You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Releases after `v0.16.0` include a `checksums.txt` asset containing the SHA-256 digest of every executable. These releases are immutable, so their tags, executables, and checksum manifests cannot be replaced after publication. CLI releases through `v0.16.0` predate this integrity contract.
Copy file name to clipboardExpand all lines: RELEASING.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ This document describes how to create a new release of `linear-release`.
7
7
- You must be on the `main` branch with a clean working tree, up to date with `origin/main`
8
8
- The [GitHub CLI](https://cli.github.com) (`gh`) must be installed and authenticated
9
9
-`pnpm` must be installed
10
+
- Immutable releases must be enabled in the repository settings
10
11
11
12
## Creating a release
12
13
@@ -57,9 +58,13 @@ When a PR from a `release/*` branch is merged into `main`, the **Auto-tag releas
57
58
58
59
The **Release** workflow (`.github/workflows/release.yml`) is triggered by the new tag and:
59
60
60
-
1. Builds platform-specific executables (linux-x64, darwin-x64, darwin-arm64) using Bun
61
+
1. Builds platform-specific executables (linux-x64, linux-arm64, darwin-x64, darwin-arm64) using Bun
61
62
2. Code signs and notarizes the macOS binaries
62
-
3. Creates a GitHub Release with the built binaries attached
63
+
3. Generates and validates `checksums.txt` for the final executables
64
+
4. Creates a draft GitHub Release and attaches all executables and the checksum manifest
65
+
5. Publishes the completed draft as an immutable release
66
+
67
+
After publication, release assets cannot be changed or deleted and the associated tag cannot be moved. If a published artifact is incorrect, fix the issue and publish a new patch version instead of replacing the existing asset.
0 commit comments