-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
[wallet-ext] New wallet versioning strategy #5814
Conversation
💳 Wallet Extension has been built, you can download the packaged extension here: https://github.com/MystenLabs/sui/actions/runs/3424442057#artifacts |
529d317
to
70270e1
Compare
} | ||
|
||
const WALLET_BETA = !!process.env.WALLET_BETA; | ||
const PATCH_VERISON = Number(process.env.PATCH_VERSION) || 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this used in case we need to publish again the same day?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah exactly, just buys us the ability to do multiple releases in a day in the event something goes wrong. Or if we do want a true patch release of a dated version, we can just cherry-pick commits onto it and issue a patch vs having to issue a full version.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
e223e71
to
0ac5b22
Compare
This updates the wallet versioning strategy so that it is aligned with the new wallet release proposal. This includes support for beta builds, and better name labelling for the dev builds.
I removed the wallet version workflow as we're now accomplishing this through a different means (date-based versioning + beta builds).