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

Migrate to changesets #607

Merged
merged 14 commits into from
Jan 8, 2025
Merged

Migrate to changesets #607

merged 14 commits into from
Jan 8, 2025

Conversation

enisdenjo
Copy link
Owner

@enisdenjo enisdenjo commented Jan 8, 2025

We're now using changesets (instead of semantic-release). Main reasons are snapshot releases, clear overview of the upcoming release and not using commits for messages (commits cant change if you make a mistake).

From now on, if a PR contains releasable changes, they should be documented with:

yarn changeset

@theguild-bot
Copy link
Collaborator

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
graphql-ws 5.16.1-alpha-103ff293fd6f223310e605efd6d3875fd82fd07c npm ↗︎ unpkg ↗︎

@enisdenjo enisdenjo merged commit a629ec7 into master Jan 8, 2025
8 checks passed
@enisdenjo enisdenjo deleted the changesets branch January 8, 2025 15:13
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.

None yet

2 participants