chore(release): add semantic-release#432
Draft
outslept wants to merge 1 commit intoeditorconfig:mainfrom
Draft
Conversation
- Added semantic-release workflow in GitHub Actions - Configured release.config.js with appropriate plugins - Added required dependencies for semantic-release - Updated .vscodeignore to exclude release.config.js
2561796 to
8205e04
Compare
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
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 fill in this template.
tscw/o errors (same asnpm run build).npm run lintw/o errors.Testing
I've tested the configuration with semantic-release --dry-run which completes successfully until the final push step (which is expected since pushing to main is restricted).
Also I've tested the GitHub action locally with act. Logs below:
Note
I'll keep this PR in draft status (although it's ready for merge) to avoid potentially disrupting changelogs while we can discuss if there's a more reliable way to test the semantic-release configuration.
Part of #406