Skip to content

chore(bridge): repin to pyMzLib v0.1.0.dev4 - #10

Merged
trishorts merged 1 commit into
mainfrom
bridge/pymzlib-0.1.0.dev4
Aug 9, 2026
Merged

chore(bridge): repin to pyMzLib v0.1.0.dev4#10
trishorts merged 1 commit into
mainfrom
bridge/pymzlib-0.1.0.dev4

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

pyMzLib published v0.1.0.dev4. This repins R/install-bridge.R from
0.1.0.dev1 to 0.1.0.dev4, with all four SHA-256 digests regenerated by
scripts/regen-bridge-pins.R from that release's SHA256SUMS asset.

What to check before merging

The digests come from the release manifest, so they are right by construction if
the manifest is. What CI cannot tell you is whether the new bridge changes any
value mzLib reports — the live canaries exercise the wire contract, not the
numbers crossing it. If the pyMzLib release notes mention a reader or a unit
changing, look for a caveat in this package that has become wrong.

Under BRIDGE-MAINTAIN-PARITY, a bridge bump that retires a caveat retires it
in pyMzLib, mzLibRust and mzLibR as one unit of work.


Opened by .github/workflows/bridge-watch.yml.

Regenerated from the SHA256SUMS asset by scripts/regen-bridge-pins.R.
Opened by bridge-watch.yml.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant