feat(release): use latest open-turo semantic release config#67
Merged
Conversation
tagoro9
force-pushed
the
f/use_latest_semantic_config
branch
from
4ce4d1b to
e4e9205
Compare
greenkiwi
approved these changes
Jan 24, 2025
|
🎉 This PR is included in version 2.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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.
Description
I just realized this pythong repos were doing some things on releases that our latest config shouldn't do (like post messages in PRs with the released version). This PR updates the pinned version of the semantic release config to use the latest.
We had originally pinned it to 1.4.0 because of a bug in 2.0.0 that broke many things. All other repos are using the latest version.
Changes
🚀 PR created with fotingo