Document release automation #2163
Open
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
This was referenced Nov 22, 2024
marcustyphoon
force-pushed
the
document-release
branch
from
ed5a806 to
e0755f3
Compare
|
Might make sense to add to .env.example with a comment link to |
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.
Adds documentation about the (convoluted... but fewer steps than previously?) XKit version release process automation.
I think the worst thing about this is currently the xkit_patches version bump, which I managed to screw up earlier today. If anyone can think of a way to refactorRemoved as of #2165 and #2166!run_orderso this doesn't have to be done or can be simpler, I'm all ears (just make sure your idea works with mismatched xkit_patches and xkit versions).