@@ -100,11 +100,11 @@ stay unpublished. There are three channels:
100100- ** Stable** (` latest ` ): a repository admin publishes a GitHub release with a new ` vX.Y.Z ` tag
101101 targeting ` main ` . Use the version ` main ` builds towards (its ` X.Y.Z-dev ` ), or a later one, and
102102 write the notes or generate them in the release form. The tag starts a ** Release** run. It waits
103- up to 20 minutes for that commit's CI to pass and for approval in the ` release ` environment, then
104- publishes the packages, attaches the iOS runner and Android helper assets to the release,
105- publishes the MCP Registry entry, and commits ` main ` 's next ` -dev ` version. If you reject the run,
106- delete the release and its tag. Pushing the tag instead (` git push origin main:refs/tags/vX.Y.Z ` )
107- starts the same run, which then drafts the release itself.
103+ up to 20 minutes for that commit's CI to pass, then waits for approval in the ` release `
104+ environment. Once approved, it publishes the packages, attaches the iOS runner and Android helper
105+ assets to the release, publishes the MCP Registry entry, and commits ` main ` 's next ` -dev ` version.
106+ If you reject the run, delete the release and its tag. Pushing the tag instead (`git push origin
107+ main : refs /tags/vX.Y.Z`) starts the same run, which then drafts the release itself.
108108- ** Dry run** : a pull request that changes release tooling builds and verifies every package with a
109109 nightly version, and publishes nothing.
110110
0 commit comments