chore: add script to make versioning and publishing prereleases easier

[massao]

Purpose of PR

Add script to make the handling of prereleases packages easier.

The script will handle:

• bumping the version according to the selected prerelease (alpha, beta)
• adding to the ignore field on changeset configuration
• publish to npm

PS: kept with the --dry-run flag for now for testing, will remove it before merging into main

[changeset-bot]

⚠️ No Changeset found

Latest commit: c7abb32

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

[vercel]

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

Name	Status	Preview	Updated
forma-36	✅ Ready (Inspect)	Visit Preview	Sep 13, 2022 at 1:36PM (UTC)

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
CommonJS	120.59 KB (0%)	2.5 s (0%)	459 ms (+19.78% 🔺)	2.9 s
Module	118.39 KB (0%)	2.4 s (0%)	332 ms (+7.18% 🔺)	2.7 s

[Lelith]

thank you so much for taking care of this!

[denkristoffer]

How, if at all, does this handle having both a stable and a prerelease version of a component? Is that even possible?

[massao]

How, if at all, does this handle having both a stable and a prerelease version of a component? Is that even possible?

It doesn't, it could be possible with a bit more tweaking, because we would need to know if it is a new prerelease our going back to a previous one have to store the information of the prerelease somehow, so there is no version conflict, e.g:

alpha -> stable fix -> back to alpha = `alpha.x`
or
alpha -> merge alpha -> new alpha = `4.x.x-alpha.0`

~~For that we could have a json file that store the prerelease versions that weren't merged into stable yet, but we would need to also add a command to mark that we will merge a prerelease package into stable. 🤔 ~~
But the code of the component would be all messed up with that.

Nevermind that, since need the prerelease code on the main branch so it shows up on the website, once a package enter a prerelease state, it will only receive a new stable version if that prerelease is completed.
Otherwise we would have a new stable release but with prerelease code

[denkristoffer]

I think that's okay, but we should add documentation specifying that prerelease is only for new components. Or something like that. What do you think?