feat(scripts): adds scripts for managing releases #81
Conversation
|
👋 MStreet3, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
MStreet3
force-pushed
the
street_addsReleaseScripts
branch
from
4f4cf6a to
5ffe60f
Compare
| Once the release is ready to be tagged execute the publish flow: | ||
|
|
||
| ```bash | ||
| $ make publish_release |
There was a problem hiding this comment.
It's unlikely we'll always keep the capabilities in sync with the base SDK.
| - capabilities/scheduler/cron | ||
| - capabilities/networking/http | ||
| - capabilities/blockchain/evm |
There was a problem hiding this comment.
Can we discover capabilities by walking the folders?
| # Create a new branch from the release branch | ||
| describe "Creating fix branch..." | ||
| git checkout -B $fix_branch origin/$release_branch |
There was a problem hiding this comment.
Is this what we want? It seems wrong to make releases from the non-main branch.
| fi | ||
|
|
||
| # Ask for the stage of release | ||
| read -p "Version Stage [beta/stable]: " versionStage |
There was a problem hiding this comment.
I would add alpha and rc as optional, maybe confirm with @wentzeld and @ejacquier what tags we potentially want.
| "capabilities/scheduler/cron/" | ||
| "capabilities/networking/http/" | ||
| "capabilities/blockchain/evm/" |
There was a problem hiding this comment.
use find to get them so we can't miss new ones. Ideally you specify which one you want and we have a helper to do it for all of them. The odds we update everything at once after GA are low.
MStreet3
force-pushed
the
street_addsReleaseScripts
branch
from
5ffe60f to
7ce8192
Compare
2 participants
No description provided.