Skip to content

chore: prep release workflow for @next release #125

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

Merged
merged 1 commit into from
Oct 27, 2024

Conversation

huntabyte
Copy link
Collaborator

This PR adds the next branch to the release.yml workflow so that it is in place. We can soon do a prerelease @next for the Svelte 5 version testing/usage prior to a full merge/release into main.

I'll create the next branch from the existing forked branch I have in this project and move those changes into it. I currently have @next deployments going for bits-ui, form snap, and paneforge, and changesets make it stupidly simple!

Copy link

changeset-bot bot commented Oct 6, 2024

⚠️ No Changeset found

Latest commit: 0c32c4a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Oct 6, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
svelte-sonner ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 6, 2024 11:19pm

@huntabyte
Copy link
Collaborator Author

This is good to merge into main @wobsoriano. Won't have any impact but we need it in main to kick off the next release workflows when the time comes 😃

Planning to give the next branch another look and come up with some API ideas for the stuff we don't yet have a solution for (component vs function for the promise toast) and hopefully, we can get an next release rolling to catch any bugs before eventually making it the main release.

@wobsoriano
Copy link
Owner

Thanks @huntabyte! Learning a lot off changeset + versioning stuff with these updates

@wobsoriano wobsoriano merged commit 76fccd9 into wobsoriano:main Oct 27, 2024
7 checks passed
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.

2 participants