Skip to content

fix: target current repository in release notes - #89

Merged
bigsmartben merged 1 commit into
mainfrom
fix/release-install-url
Jul 31, 2026
Merged

fix: target current repository in release notes#89
bigsmartben merged 1 commit into
mainfrom
fix/release-install-url

Conversation

@bigsmartben

Copy link
Copy Markdown
Owner

Summary

  • Build the release-note install URL from ${GITHUB_REPOSITORY} instead of hard-coding github/spec-kit.
  • Add a regression test that requires the dynamic repository URL and rejects the former hard-coded URL.

Root cause

The release workflow was inherited from upstream with an installation command fixed to github/spec-kit. Releases created in a fork therefore told users to install the upstream repository instead of the repository that produced the release.

Impact

Future releases now render an install command for their own repository. For example, a bigsmartben/spec-kit release produces git+https://github.com/bigsmartben/spec-kit.git@<tag>, while the upstream workflow continues to produce its own URL.

Validation

  • .venv/Scripts/python.exe -m pytest tests/test_github_workflows.py -v — 4 passed
  • uvx ruff@0.15.0 check tests/test_github_workflows.py — passed
  • git diff --check — passed

Agent disclosure

Prepared, tested, committed, pushed, and posted on behalf of @bigsmartben by OpenAI Codex (model: GPT-5, autonomous).

Assisted-by: OpenAI Codex (model: GPT-5, autonomous)
@bigsmartben
bigsmartben marked this pull request as ready for review July 31, 2026 07:25
@bigsmartben
bigsmartben merged commit 5b89a1e into main Jul 31, 2026
17 checks passed
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