Automated release with Semantic Release #32
Merged
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
tyrann0us
reviewed
Sep 29, 2023
There was a problem hiding this comment.
We are getting very close. Thanks for incorporating all the changes!
But:
> Packages based on yarn will not be released using this automation.
Wait, I was not aware of this! 🤯 Looks like we definitely need to decide on a package manager, and should we decide on yarn, switch to https://github.com/hongaar/semantic-release-yarn.
Edit: This is not correct.
old review, already addressed everything
luislard
approved these changes
Oct 9, 2023
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
With this PR I would like to add a new workflow that uses Semantic Release.
It is lightly based on the workflow my team has used for years.
Semantic release requires a
release.config.jsfile in order to configure the plugins that are needed during the release process. This file is created by the workflow, so there is no more need for that file inside the caller repository, unless you are releasing a custom package and you want to provide that file.The release.config.js file is generated from a template with basic setups. Refer to the documentation page for more specifications.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: