chore: prepare release 2024-04-22 #3037
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
soon yes waiting for joni's go! |
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
Fluf22
previously approved these changes
Apr 23, 2024
shortcuts
force-pushed
the
chore/prepare-release-2024-04-22
branch
from
dca2d93 to
902d38f
Compare
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.
Summary
This PR has been created using the
yarn releasescript. Once merged, the clients will try to release their new version if their version has changed.Version Changes
prerelease(e.g. 7.0.0-beta.1)minor(e.g. 1.9.0)prerelease(e.g. 4.0.0-beta.13)prerelease(e.g. 4.0.0-beta.31)prerelease(e.g. 5.0.0-beta.1)prerelease(e.g. 3.0.0-beta.26)prerelease(e.g. 4.0.0-beta.1)minor(e.g. 4.0.0b16)minor(e.g. 3.0.0.beta.1)prerelease(e.g. 2.0.0-beta.1)prerelease(e.g. 9.0.0-beta.1)Skipped Commits
It doesn't mean these commits are being excluded from the release. It means they're not taken into account when the release process figured out the next version number, and updated the changelog.
Commits without language scope:
Commits with unknown language scope: