ci(release): set release-please release-as for now#4835
Merged
erikgb merged 1 commit intoweaveworks:mainfrom Mar 16, 2025
Merged
ci(release): set release-please release-as for now#4835erikgb merged 1 commit intoweaveworks:mainfrom
erikgb merged 1 commit intoweaveworks:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes
What changed?
Instruct release-please of the next release as the prerelease strategy in release-please does not seem to support our use case, ref. #4834
Why was this change made?
We want to cut new release candidates until we know that things are working.
How was this change implemented?
How did you validate the change?
Release notes
Documentation Changes