also looking at this
fix: validate native SDK release prerequisites before tagging
#364
7 files
+153
-15
| @@ -11,7 +11,9 @@ They also read addressed native state from the main, child, and adopted windows. | ||
| 11 | 11 | Each installed-app smoke also checks creator teardown and adoption of a |
| 12 | 12 | surviving, unparented grandchild. The PKG case explicitly destroys the retained |
| 13 | 13 | macOS creator after close; DEB and MSI close already releases it. |
| 14 | The release hook generates the next changelog section before that commit, | |
| 14 | The release command registers the workspace and Zig release manifests with | |
| 15 | Bumpx so their versions update and roll back together. The release hook | |
| 16 | generates the next changelog section before that commit, | |
| 15 | 17 | deduplicates repeated issue references, and links the previous and new tags. |
| 16 | 18 | Do not run the hook again after it has written the section. |
| 17 | 19 | |
| @@ -61,3 +63,18 @@ registry publication can still fail after the native archives become public, so | ||
| 61 | 63 | the final workflow status remains the release signal. If a post-release registry |
| 62 | 64 | publication fails, the GitHub release still contains the full verified archive |
| 63 | 65 | set; inspect and rerun the failed job rather than republishing the draft. |
| 66 | ||
| 67 | ## Release prerequisites and failed tags | |
| 68 | ||
| 69 | Install the locked release tools with `bun install --frozen-lockfile` first. | |
| 70 | Preflight now checks the Bumpx and Logsmith CLIs, a clean `main`, and the current | |
| 71 | `origin/main` before changing versions. Use a separate release clone if `main` | |
| 72 | is in use by another worktree. Required release commands fail before committing, | |
| 73 | tagging or pushing; Bumpx restores the version files when they fail. | |
| 74 | ||
| 75 | Retain a tag that failed publication. Choose a new unused version with | |
| 76 | `bun run release:version <version>` and set `CRAFT_CHANGELOG_FROM` to the last | |
| 77 | successfully published tag. The standard version and patch commands run the | |
| 78 | same manifest synchronization, changelog generator and publication gates. | |
| 79 | Confirm the final Releaser result and actual registry artifacts before apps | |
| 80 | adopt the new version. | |