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 #3135

Merged
merged 6 commits into from
Jan 9, 2024
Merged

Implement semantic release #3135

merged 6 commits into from
Jan 9, 2024

Conversation

cwillisf
Copy link
Contributor

Resolves

Proposed Changes

Implement semantic-release and friends.

@cwillisf cwillisf force-pushed the implement-semantic-release branch from 417f1b1 to d77da46 Compare December 21, 2023 03:46
@cwillisf cwillisf force-pushed the implement-semantic-release branch from 1fe67a5 to d05bf67 Compare December 21, 2023 03:57
@cwillisf cwillisf requested a review from delasare January 5, 2024 19:38
@cwillisf cwillisf merged commit 0ee13ca into develop Jan 9, 2024
2 checks passed
@cwillisf cwillisf deleted the implement-semantic-release branch January 9, 2024 16:39
github-actions bot pushed a commit that referenced this pull request Jan 9, 2024
…lement-semantic-release

Implement semantic release
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