Skip to content

ci(release): build and attach the Windows bundle from the release-please run - #121

Merged
spelech merged 2 commits into
mainfrom
ci/release-build-trigger-repo
Nov 12, 2026
Merged

spelech merged 2 commits into
mainfrom
ci/release-build-trigger-repo

Conversation

@spelech

@spelech spelech commented Nov 12, 2026 •

Copy link
Copy Markdown
Owner

Summary

The Windows portable bundle was not attached to v2.23.0. Releases and tags that release-please creates with GITHUB_TOKEN do not trigger other workflows (release: published, push: tags), and the gh workflow run hand-off from #117 failed because the release-please job has no checkout:

Release created for tag: v2.23.0
failed to run git: fatal: not a git repository (or any of the parent directories): .git

(The v2.23.0 bundle was built by hand: run 43268867692.)

Change

  • build-portable-windows.yml gets a workflow_call trigger with tag_name. It checks out the release tag, uploads with gh release upload --clobber (a re-run replaces the asset), and a new step verifies that the release has contextcortex-windows-x64-portable.zip with the size of the built zip. A concurrency group allows one build per tag at a time. Manual workflow_dispatch with tag_name still works; PR builds still build and smoke-test without attaching.
  • release-please.yml exports releases_created and tag_name and calls the bundle workflow as a second job (needs: release-please). No dispatch, no extra token; a bundle failure now shows in the release run. actions: write is no longer needed.

Verification

  • Both workflows parse; the PR build runs the bundle build and smoke tests (no attach on PRs).
  • The attach and verify steps can be exercised before the next release with a manual dispatch of this branch's workflow and tag_name=v2.23.0 (rebuilds the v2.23.0 code and replaces the same asset).

🤖 Generated with Claude Code

Steve Pelech and others added 2 commits November 12, 2026 11:23
The release-please job has no checkout, so `gh workflow run` failed with
"not a git repository" and no Windows bundle was built for v2.23.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ase run

Releases and tags created with GITHUB_TOKEN do not trigger other workflows,
and the gh workflow run hand-off failed for v2.23.0 ("not a git
repository"). The Windows bundle is now a reusable workflow
(workflow_call) that release-please.yml calls as a second job when a
release is created.

- build-portable-windows.yml: workflow_call input tag_name; checks out the
  release tag; uploads with `gh release upload --clobber` (safe re-runs);
  verifies that the release has the zip with the built size; one build per
  tag at a time (concurrency). Manual dispatch with tag_name still works.
- release-please.yml: exports releases_created/tag_name and calls the bundle
  workflow; the actions: write permission is no longer needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@spelech spelech changed the title ci(release): pass --repo to gh when triggering the Windows bundle build ci(release): build and attach the Windows bundle from the release-please run Nov 12, 2026
@spelech
spelech merged commit bdf109f into main Nov 12, 2026
12 checks passed
@spelech
spelech deleted the ci/release-build-trigger-repo branch November 12, 2026 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant