Update the release script #99
Conversation
allow pre-releases to be automated, too
| # Get the release version. | ||
| echo "Enter the release version: " | ||
| read VERSION | ||
| # Check if this is a pre-release or a regular release. |
There was a problem hiding this comment.
I'm confused a bit the name of the script and the release.
I think there are two types of release: pre-release and regular release.
I also think there are two types of scripts: pre-release and post-release
If that's the case, we're good.
There was a problem hiding this comment.
Yes and yes. The scripts were named that way because there are steps to automate before a release is created and steps to automate after a release is created.
Independent of that, there are pre-releases (which is a type of release) and there are regular releases. It's hairy naming territory for sure, but if we continue using the branches/x.x for version Next releases (which I think is a good practice to ensure we don't break what's on main and can develop for specific versions while maintaining a stable version on main) then this helps that process.
There was a problem hiding this comment.
I believe there are ways that releases can be created with the gh commandline tool, but to do that, we'd also need to automate the process of pulling in the PR names to build release notes. Altis has some scripts for this, but I don't know if they're public, so for now, the actual creating a release part is manual.
commands failing and some syntax issues
This PR changes the
pre-releasescript to allow pre-releases to be automated, too.