chore: bump out-of-workspace consumers to the published v9.1.0 wave - #857
Merged
Merged
Conversation
acap-multimux, transmux-py and dvb-si-py sit outside the cargo workspace and resolve their dependencies from crates.io by version rather than by path, so they could not be bumped in the release PR — the versions did not exist yet and their CI was unsatisfiable by construction. Now that the wave is live: - acap-multimux: transmux 0.20 -> 0.21 - transmux-py: transmux 0.20 -> 0.21, crate 0.1.0 -> 0.2.0 - dvb-si-py: crate 0.1.0 -> 0.2.0 (tracks lockstep 9.1.0) This PR's CI is the end-to-end verification of the publish: these are the only things in the repo that resolve against the registry rather than local paths, so green here means the published artifacts actually resolve and build.
acap-multimux keeps its own Cargo.lock and CI runs `cargo test --locked`, so bumping the transmux requirement without regenerating the lock fails before it compiles anything. The regeneration pulls the whole wave in one resolution — transmux 0.20->0.21, ll-hls-runtime 0.2->0.3, media-plane 0.1.0->0.1.1, multimux 0.5.0->0.5.1, rtmp-runtime 0.2->0.3 — with no version conflict, which is the mixed-major check from #824 verified against the registry rather than asserted in a doc. Verified: `cargo test --locked` in acap-multimux, 18 passed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the v9.1.0 release wave, as flagged in
docs/release-notes/v9.1.0.mdunder Post-publish follow-up.acap-multimux,transmux-pyanddvb-si-pysit outside the cargo workspace and resolve their dependencies from crates.io by version, not by path. They could not be bumped in the release PR itself — the versions did not exist yet, socargo metadatacould not resolve and their jobs failed by construction (six red checks on #854 before the bumps were pulled out).Now that the wave is live:
acap-multimuxtransmux0.20 → 0.21bindings/transmux-pytransmux0.20 → 0.21, crate 0.1.0 → 0.2.0bindings/python(dvb-si-py)Why this PR is the real publish verification
These are the only things in the repo that resolve against the registry rather than local paths. Every other gate builds from the workspace, which is exactly why the
transmux-v0.21.0publish failure (a dev-dep cycle, fixed in #856) got through CI untouched.Green here means the published artifacts actually resolve and build for a consumer.