ci: resolve pre-release commit but not release #9631
Merged
Conversation
This file contains 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
benelan
requested review from
jcfranco,
driskull,
geospatialem and
a team
as code owners
github-actions
bot
added
the
chore
jcfranco
approved these changes
Jun 18, 2024
benelan
added
the
skip visual snapshots
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.
Related Issue: #9578
Summary
The PR linked above introduced a bug in the pre-release automation script, which
abstracted the steps for use on multiple branches. The bug resulted in some
"build: update types and package-lock" commits on
devthat versionednextbut didn't actually release.I brought the state of the repo back to before those commits, and fixed the
issues. I also removed the hotfix pre-release logic, so pre-releases can only occur
on
devandnext.