ci: Publish packages after the release flow #3064
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
Signed-off-by: utam0k <[email protected]>
utam0k
added
the
kind/cleanup
YJDoc2
reviewed
Feb 1, 2025
| needs: build | ||
| environment: | ||
| name: release | ||
| needs: release |
There was a problem hiding this comment.
We should still keep the env as release right? That way the maintainers can approve the env and only the publish the package. Or are we removing that functionality, and going directly to release if the test and builds pass?
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.
Description
Type of Change
Testing
N/A
Related Issues
None
Additional Context