chore: prep release workflow for @next
release
#125
Merged
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.
This PR adds the
next
branch to therelease.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 intomain
.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 forbits-ui,
form snap,
andpaneforge
, and changesets make it stupidly simple!