-
Notifications
You must be signed in to change notification settings - Fork 80
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
Stable Release for NV23 #1569
Comments
We've already shipped this to calibrationnet. Are we going to run a separate build on mainnet? |
We have only shipped the v14.0.0-rc1 - so it will be the same bundle/commit, but tagged as stable (i.e v14.0.0). Also I am writing up this issue mostly for capturing it as an item that needs to be done before a Mainnet upgrade for the (publicly viewable) nv23 upgrade tracking master doc. |
Ah, awesome. I just wanted to make sure we didn't re-build... |
So just for sanity, it should be fine to create the v14.0.0 tag based on the release/v14 branch, as its the same commit as https://github.com/filecoin-project/builtin-actors/releases/tag/v14.0.0-rc.1, or will this trigger a re-build? Or how has this been handled before? |
Closing as the final v14.0.0 release has been published here: https://github.com/filecoin-project/builtin-actors/releases/tag/v14.0.0 |
Tracking issue for cutting the stable v14.0.0 builtin-actors release.
The v14.0.0-rc1 bundle, has gone through testing in devnets/butterfly/calibration without any issues arising (Check: (publicly viewable) nv23 upgrade tracking master doc..
So no backports seems needed to the
release/v14
branch, and we would just need to re-tag the rc1 as stable, but if there are any, they should be flagged in this ticket.The text was updated successfully, but these errors were encountered: