disable DRY_RUN on releasable branches #589
Merged
Conversation
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
szwarckonrad
approved these changes
Feb 3, 2025
ashokaditya
approved these changes
Feb 3, 2025
pzl
added a commit
that referenced
this pull request
Feb 3, 2025
pzl
added a commit
that referenced
this pull request
Feb 3, 2025
pzl
added a commit
that referenced
this pull request
May 5, 2025
pzl
added a commit
that referenced
this pull request
May 5, 2025
This was referenced May 5, 2025
pzl
added a commit
that referenced
this pull request
May 5, 2025
pzl
added a commit
that referenced
this pull request
May 5, 2025
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.
on branches like
8.x, package release would happen in a dry run modeSo the on-merge step on the
8.xbranch right now did not publish the8.18.0package, epr still reflects8.17.0as current.Making sure these specific branches allow live deployments may fix. This change will be backported to
8.xbranch