Skip to content

release: v0.3.0-beta.2 #161

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.

Sign up for GitHub

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

Merged
gnanirahulnutakki merged 2 commits into from
Jul 14, 2026
Merged

release: v0.3.0-beta.2 #161

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6d2d127
fix(e9): publish beta drafts by release ID
Jul 14, 2026
ad0a819
Merge pull request #160 from ArdurAI/gnanirahulnutakki/fix/e9-beta-dr…
gnanirahulnutakki Jul 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ jobs:
run: |
set -euo pipefail
if [[ "$RELEASE_KIND" == "beta" ]]; then
release_id="$(gh api "repos/${GITHUB_REPOSITORY}/releases/tags/${GITHUB_REF_NAME}" --jq '.id')"
release_id="$(gh release view "$GITHUB_REF_NAME" --json databaseId --jq '.databaseId')"
gh api --method PATCH "repos/${GITHUB_REPOSITORY}/releases/${release_id}" \
-F draft=false \
-F prerelease=true \
Expand Down
41 changes: 41 additions & 0 deletions sessions/2026-07-14-e9-beta-draft-publish.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# E9 beta draft publication repair — 2026-07-14

Issue: #159
Branch: `gnanirahulnutakki/fix/e9-beta-draft-publish`
Base: `origin/dev` at `ff07b60ff934508dd694f338ffa017d3503da171`

## [G] Goal

Repair the beta publication step so a workflow-created draft release is resolved by its database ID
and can be published as a prerelease without replacing the latest stable release.

## [S] Incident boundary

- Signed `v0.3.0-beta.1` passed GitHub tag verification and the release workflow built, signed, and
attested the draft artifacts.
- The final publication step used `GET /releases/tags/{tag}` and received 404 for the draft,
leaving the draft unpublished. Stable `v0.2.1` remained latest.
- The failed tag and draft are preserved. No deletion, force-push, retagging, or manual publication
is permitted. The corrected workflow will publish a new immutable `v0.3.0-beta.2` tag.

## [A] Evidence in progress

- The workflow now resolves `gh release view <tag> --json databaseId`, whose draft-aware view is
already proven by the existing beta.1 draft.
- The policy test requires that lookup, rejects the draft-invisible tags endpoint, and keeps the
raw-string `make_latest=false` assertion.
- Pending: focused and full gates, red-team review, hosted PR/post-merge CI, release promotion, and
beta.2 artifact verification.

## [T] Test plan

1. Run policy scripts, `make ci`, and `make release-check` on the final diff.
2. Confirm stable publication remains unchanged and beta mutation still requires
`draft=false`, `prerelease=true`, and raw string `make_latest=false`.
3. Land through `dev` and a reviewed release PR, then create a new signed beta.2 tag and verify its
release state and macOS-arm64 archive.

## [C] Completion criteria

The issue closes only when beta.2 is published as a prerelease, `v0.2.1` remains latest, and the
macOS-arm64 release archive passes checksum, provenance, and local launch verification.
6 changes: 6 additions & 0 deletions tests/scripts/release_tag_policy_test.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,12 @@ done

grep -Fq 'hack/release-tag-classify.sh "$GITHUB_REF_NAME"' "${workflow}"
printf '[release-tag-policy] PASS: workflow invokes the tested classifier\n'
grep -Fq 'gh release view "$GITHUB_REF_NAME" --json databaseId' "${workflow}"

@coderabbitai coderabbitai Bot Jul 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Assert scalar database ID extraction.

Line 53 checks only --json databaseId; it would still pass if --jq '.databaseId' were removed and the full JSON object were passed to the PATCH URL. Match the complete lookup or separately assert the --jq expression.

🧰 Tools
🪛 Shellcheck (0.11.0)

[info] 53-53: Expressions don't expand in single quotes, use double quotes for that.

(SC2016)

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/scripts/release_tag_policy_test.sh` at line 53, Strengthen the
assertion in the release workflow validation around the grep for `gh release
view` so it verifies scalar extraction via `--jq '.databaseId'`, not just the
`--json databaseId` field. Match the complete command or add a separate
assertion covering the jq expression.

if grep -Fq 'releases/tags/${GITHUB_REF_NAME}' "${workflow}"; then
printf '[release-tag-policy] FAIL: beta publication uses draft-invisible tag lookup\n' >&2
exit 1
fi
printf '[release-tag-policy] PASS: beta publication resolves the draft release by database ID\n'
grep -Fq -- '-f make_latest=false' "${workflow}"
printf '[release-tag-policy] PASS: beta publication cannot replace latest stable\n'
grep -Fq 'vMAJOR.MINOR.PATCH-beta.N' "${guide}"
Expand Down