github: Separate 2.3 and 2.4 release workflows #1263
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
slusarz
force-pushed
the
github_actions_2_3
branch
from
457602f to
2e8e3d1
Compare
cmouse
reviewed
Aug 8, 2025
cmouse
reviewed
Aug 8, 2025
Contributor
Author
|
I resolved the 2.3 change, but it doesn't seem like we were tagging 2.3 before? Will we change release process to add tags for 2.3 (if we ever release) going forward? |
slusarz
force-pushed
the
github_actions_2_3
branch
from
2e8e3d1 to
a0624d1
Compare
cmouse
force-pushed
the
github_actions_2_3
branch
from
a0624d1 to
03ebfb7
Compare
cmouse
approved these changes
Aug 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
2.3 release would build all of vitepress documentation even though it is never used.
Regardless, given EOL of 2.3, it should be removed from the "main" release action anyway.