Repository navigation
ci(dependabot): hold CI-breaking major bumps (setup-swift v3, rand 0.10) - #526
Merged
Seth Juarez (sethjuarez) merged 2 commits intoSep 9, 2026
Merged
Conversation
The regenerated actions-version group (PR #525) bumps swift-actions/setup-swift v2 -> v3, which fails the Swift CI job on Linux: gpg: Can't check signature: No public key The process '/usr/bin/gpg' failed with exit code 2 This is an open upstream bug in the action's Swiftly-based installer: swift-actions/setup-swift#798 Ignore major (v3) bumps for swift-actions/setup-swift so the group keeps the working v2 SHA pin while still taking the passing setup-java/gradle bumps. Remove once upstream v3 installs cleanly. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The cargo-version group (PR #504) bumps rand 0.9 -> 0.10, a breaking API change that removes the Rng::random()/random_range() methods our code uses: error[E0599]: no method named \ andom\ found for struct \ThreadRng\ error[E0599]: no method named \ andom_range\ found for struct \ThreadRng\ These are used in prompty (parsers/prompty.rs, renderers/common.rs, pipeline/live_turn.rs) and prompty-foundry (oauth.rs). Hold rand on 0.9 until the source is migrated to the 0.10 API so the grouped cargo updates stay green. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Seth Juarez (sethjuarez)
changed the title
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
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.
What
Adds Dependabot
ignorerules for two major version bumps that break CI, so their grouped PRs regenerate green while still taking every other update in the group:swift-actions/setup-swift— hold at v2 (github-actionsecosystem)rand— hold at 0.9 (cargoecosystem)Why
setup-swift v3 (breaks #525)
The regenerated actions-version group (#525) bumps
swift-actions/setup-swiftv2→v3, which fails the Swift CI job on Linux:Open upstream bug in the action's Swiftly-based installer: swift-actions/setup-swift#798. v2 works fine (Swift check is green on
main). The group'sactions/setup-javav6 andgradle/actions/setup-gradlev6 bumps pass and are unaffected.rand 0.10 (breaks #504)
The cargo-version group (#504) bumps
rand0.9→0.10, a breaking API change that removes theRng::random()/random_range()methods our code uses, so the workspace no longer compiles across all 4 Rust matrix jobs:Used in
prompty(parsers/prompty.rs,renderers/common.rs,pipeline/live_turn.rs) andprompty-foundry(oauth.rs).main(rand 0.9) is green. Holding rand at 0.9 keeps the other 7 cargo bumps flowing.Effect
After merge,
@dependabot recreateon #525 and #504 → both regenerate without the breaking major and go green.Follow-up
rand0.9→0.10 source migration. Worth a tracking issue.