docs: update published Mina artifact versions - #1223
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
e7bbac8 to
cb7ef9f
Compare
|
|
||
| **Repository:** `packages.o1test.net` | ||
| **Channel:** `mesa-trail` | ||
| **Channel:** `alpha` |
There was a problem hiding this comment.
should this be alpha or still be mesa-trail?
| ## Current Build Version | ||
|
|
||
| **Version (install this):** `4.0.0-rc2-3418329` | ||
| **Version (install this):** `4.0.0-6965b50` |
There was a problem hiding this comment.
Check all versions on this page, they all change and they should not
| # Step 2: Add the repository with the mesa-trail channel. | ||
| # packages.o1test.net is unsigned, hence [trusted=yes]. | ||
| echo "deb [trusted=yes] http://packages.o1test.net $(lsb_release -cs) mesa-trail" | \ | ||
| echo "deb [trusted=yes] http://packages.o1test.net $(lsb_release -cs) alpha" | \ |
cb7ef9f to
37e5e84
Compare
glyh
left a comment
glyh
left a comment
There was a problem hiding this comment.
Verified every version and image tag this PR introduces against Docker Hub and packages.o1test.net. All of them are real: the 7 Docker tags return 200, mina-mainnet / mina-archive-mainnet / mina-rosetta-mainnet / mina-archive =4.0.0-6850301 are in stable, and mina-devnet=4.0.0-6965b50 is in alpha. The substitution itself looks correct.
Four things before merge, two of them inline below.
1. The branch conflicts with main and needs a rebase. Main has since landed the devnet half of the docker-compose changes (same 4.0.0-6965b50 pins), so those hunks are now duplicate work, and static/llms-full.txt was regenerated on main in f29dd98. Please rebase and regenerate llms-full.txt afterwards rather than merging the stale copy.
2. One gcr.io reference was missed. docs/network-upgrades/mesa/archive-upgrade.mdx line 104 still extracts the SQL script from gcr.io/o1labs-192920/mina-archive:<MESA_VERSION>-bookworm-mainnet, while verify-the-release.mdx moved to minaprotocol/ in this same PR. minaprotocol/mina-archive:4.0.0-6850301-bookworm-mainnet exists on Docker Hub, so this one should move too for consistency.
Items 3 and 4 are inline.
| # Devnet: mina-devnet=4.0.0-6965b50 | ||
| sudo apt-get install mina-<network>=<mesa-version> | ||
|
|
||
| # The pre-fork genesis generator, used to build the reference ledgers |
There was a problem hiding this comment.
Now that the install line above is network-generic, this block mixes networks: the pre-fork ledger is still pinned to the devnet build. A mainnet operator following the <network> pattern installs the wrong artifact.
The mainnet version in stable is different:
# Mainnet
sudo apt-get install mina-create-mainnet-prefork-genesis-ledger=3.5.0-mainnet-stop-slot-8110ede
# Devnet
sudo apt-get install mina-create-devnet-prefork-genesis-ledger=3.5.0-devnet-stop-slot-7a60364Worth giving this line the same two-comment treatment you gave the daemon install above.
| image: 'minaprotocol/mina-archive:3.3.0-8c0c2e6-bullseye-mainnet' | ||
| # image: 'gcr.io/o1labs-192920/mina-daemon:3.3.0-alpha1-6929a7e-bullseye-devnet' # Use this image for Devnet | ||
| image: 'minaprotocol/mina-archive:4.0.0-6850301-bullseye-mainnet' | ||
| # image: 'minaprotocol/mina-daemon:4.0.0-6965b50-bullseye-devnet' # Use this image for Devnet |
There was a problem hiding this comment.
Pre-existing copy-paste error being carried forward: this service (and missing_blocks_guardian on line 55) runs mina-archive, but the commented devnet alternative names mina-daemon. Anyone uncommenting it gets a daemon image where an archive image belongs.
The correct counterpart exists on Docker Hub:
# image: 'minaprotocol/mina-archive:4.0.0-6965b50-bullseye-devnet' # Use this image for DevnetThe same comment on mina_node (line 85) is correct as-is, since that one really is a daemon. Main has the same mistake, so fixing it here also clears part of the conflict.
| | Pre-fork (stop-slot) release | [`3.5.0-mainnet-stop-slot`](https://github.com/MinaProtocol/mina/releases/tag/3.5.0-mainnet-stop-slot) — `mina-mainnet=3.5.0-mainnet-stop-slot-5e100ee` | | ||
| | Automode release | [`4.0.0-mainnet`](https://github.com/MinaProtocol/mina/releases/tag/4.0.0-mainnet) — `mina-mainnet-automode=4.0.0-mainnet-893c877` | | ||
| | Mesa release (manual mode only) | _Published after the stop-network-slot_ | | ||
| | Mesa release (manual mode only) | `mina-mainnet=4.0.0-6850301` | |
There was a problem hiding this comment.
Judgment call rather than a defect: filling in the version dropped the link to the GitHub release, which the other two rows still carry. Keeping both would preserve what readers were using this cell for, e.g. [`4.0.0`](https://github.com/MinaProtocol/mina/releases/tag/4.0.0) — `mina-mainnet=4.0.0-6850301` .
3 participants
Summary
4.0.0-6850301.4.0.0-6965b50.Validation
npm run validate-docker-imagespasses all 13 discovered Docker references.npm run buildsucceeds.git diff --checkpasses.The repository's existing
npm run typecheckremains blocked by its pre-existing TypeScript configuration error:moduleResolution: Node16requiresmodule: Node16.