mirror of
https://github.com/Kaelio/ktx.git
synced 2026-06-07 07:55:13 +02:00
fix(release): point repository URLs at renamed GitHub repo (#250)
* fix(release): point repository URLs at renamed GitHub repo The GitHub repo was renamed from Kaelio/ktx to Kaelio/ktx-ai-data-agents-context. semantic-release reads repositoryUrl from package.json's repository field and the @semantic-release/github plugin failed verifyConditions with EMISMATCHGITHUBURL because it no longer matched the live clone URL. Update every Kaelio/ktx reference to the renamed repo: package metadata (root + CLI repository/bugs/homepage), the codecov upload slugs and star-history slug in CI, the issue-template and security-advisory links, the release runbook, and all docs/install commands. * fix(release): derive semantic-release repositoryUrl from the CI repo @semantic-release/github exact-matches repositoryUrl against the live GitHub clone_url (no redirect following), so any repo rename re-breaks the release when repositoryUrl is the static package.json value. Derive repositoryUrl from the runner's GITHUB_REPOSITORY/GITHUB_SERVER_URL so it always tracks the current repo name. A future rename (including back to Kaelio/ktx) now resolves with no code change. Outside CI the option is omitted, so semantic-release falls back to package.json as documented. The package.json repository field stays ktx-ai-data-agents-context as npm-display metadata, decoupled from the release-time match.
This commit is contained in:
parent
9133d243e8
commit
41f52797de
17 changed files with 94 additions and 33 deletions
|
|
@ -26,7 +26,7 @@ The workflow rejects releases from any branch other than `main`.
|
|||
Before you publish, confirm these requirements:
|
||||
|
||||
- npm Trusted Publishing is configured for `@kaelio/ktx`.
|
||||
- The trusted publisher points at the `Kaelio/ktx` repository and the
|
||||
- The trusted publisher points at the `Kaelio/ktx-ai-data-agents-context` repository and the
|
||||
`.github/workflows/release.yml` workflow.
|
||||
- The workflow keeps `id-token: write` permission so npm can verify the
|
||||
GitHub Actions run through OpenID Connect.
|
||||
|
|
@ -35,6 +35,15 @@ Before you publish, confirm these requirements:
|
|||
- The repository has a stable baseline tag when you need semantic-release to
|
||||
publish the first stable version as `0.1.0`.
|
||||
|
||||
If you rename the GitHub repository, the semantic-release run adapts on its
|
||||
own: `scripts/semantic-release-config.cjs` derives `repositoryUrl` from the
|
||||
runner's `GITHUB_REPOSITORY`, so `@semantic-release/github` always matches the
|
||||
current clone URL. The one thing that does **not** auto-update is the npm
|
||||
Trusted Publishing config — re-point it at the new repository name (plus
|
||||
`release.yml`) on npm, or `npm publish --provenance` will fail OIDC
|
||||
verification. The `repository` field in `package.json` is npm-display metadata
|
||||
only and can stay whatever public name you prefer.
|
||||
|
||||
semantic-release doesn't support choosing an arbitrary first `0.x` stable
|
||||
release. If KTX has no stable tag yet and you need the first stable release to
|
||||
be `0.1.0`, create and push the baseline tag once before running the live
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue