Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement semantic release #208

Merged
merged 4 commits into from
Jan 16, 2024
Merged

Implement semantic release #208

merged 4 commits into from
Jan 16, 2024

Conversation

cwillisf
Copy link
Contributor

Proposed changes

Implement semantic-release and friends.

@cwillisf cwillisf force-pushed the implement-semantic-release branch from 0d5c4f4 to dca7446 Compare December 21, 2023 03:43
@cwillisf cwillisf requested a review from skripted-io January 5, 2024 19:37
Copy link
Contributor

@skripted-io skripted-io left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love how this cleans up the workflow. Only have a minor question re: concurrency.

.github/workflows/commitlint.yml Show resolved Hide resolved
@cwillisf cwillisf merged commit 76379e6 into develop Jan 16, 2024
2 checks passed
@cwillisf cwillisf deleted the implement-semantic-release branch January 16, 2024 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

npm-published packages should follow semver
2 participants