chore: merge v2026-04-17 version bumps back to master#5266
Merged
Conversation
paolino
force-pushed
the
release-candidate/v2026-04-17
branch
from
725fcb3 to
7e2ce97
Compare
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 21, 2026
…erge the release-candidate branch back to master after the v2026-04-17 release. The release pipeline's cabal-version-drift guard fired on the next nightly because master still has cabal version \`2026.4.3\` while the last release tagged \`v2026-04-17\` (cabal \`2026.4.17\`). This PR brings the 4 version-bump commits back into master so the next release/nightly can proceed. - swagger.yaml wallet version - *.cabal cardano-wallet version - README.md wallet/node tags - run/common/docker/run.sh RELEASE_WALLET_TAG ## Test plan - [ ] Nightly release workflow runs past \`Prepare Release Candidate\` without cabal drift error. Source commit: 426f023
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.
Merge the release-candidate branch back to master after the v2026-04-17 release.
The release pipeline's cabal-version-drift guard fired on the next nightly because master still has cabal version `2026.4.3` while the last release tagged `v2026-04-17` (cabal `2026.4.17`). This PR brings the 4 version-bump commits back into master so the next release/nightly can proceed.
Test plan