Development record
the org rename breaks the plugin bootstrap's tag resolution, so a fresh install refuses with a message blaming the network. hooks/bootstrap.sh pins repo_url and api_url to the old organisation. It resolves the latest release by reading (not following) the redirect from $releases_url/latest and parsing a tag out of it with sed 's|.*/releases/tag/...|'. After the rename that URL returns 301 to https://github.com/<new-org>/abcd/releases/latest — the org hop, NOT a tag URL — so the sed matches nothing and resolved_tag is empty. Verified live 2026-08-24: old org gives redirect_url=.../abcd/releases/latest (301), new org gives .../releases/tag/v0.6.3 (302). Consequences: with a cached binary the script takes use_cache=yes with cache_trust=offline and provisions from an unauthenticated cache while claiming offline, which is wrong about the cause but degrades loudly; with NO cache the download path hits its guard '[ -n "$resolved_tag" ] || refuse the latest release tag could not be resolved ... there may be no network' and refuses, so every fresh plugin install fails and the message misdirects to the network. bootstrap.sh ships from the repository tree rather than a release asset, so merging the corrected URLs to the default branch fixes installs without waiting for a release cut.
the org rename breaks the plugin bootstrap's tag resolution, so a fresh install refuses with a message blaming the network. hooks/bootstrap.sh pins repo_url and api_url to the old organisation. It resolves the latest release by reading (not following) the redirect from $releases_url/latest and parsing a tag out of it with sed 's|.*/releases/tag/...|'. After the rename that URL returns 301 to https://github.com/<new-org>/abcd/releases/latest — the org hop, NOT a tag URL — so the sed matches nothing and resolved_tag is empty. Verified live 2026-08-24: old org gives redirect_url=.../abcd/releases/latest (301), new org gives .../releases/tag/v0.6.3 (302). Consequences: with a cached binary the script takes use_cache=yes with cache_trust=offline and provisions from an unauthenticated cache while claiming offline, which is wrong about the cause but degrades loudly; with NO cache the download path hits its guard '[ -n "$resolved_tag" ] || refuse the latest release tag could not be resolved ... there may be no network' and refuses, so every fresh plugin install fails and the message misdirects to the network. bootstrap.sh ships from the repository tree rather than a release asset, so merging the corrected URLs to the default branch fixes installs without waiting for a release cut.
Frontmatter
| id | iss-2608241659573856 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | critical |
.abcd/work/issues/resolved/iss-2608241659573856-the-org-rename-breaks-the-plugin.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608241959573830the repository moved organisations and the module path, install commands and support links still name the old one. github.com/<old-org>/abcd appears 468 times across 40+ files: go.mod's module path and the 404 import lines in 226 Go files that follow it, README.md's two badge URLs and its marketplace-add and install one-liner, docs/how-to/install.md, CITATION.cff's repository-code, SECURITY.md's advisory link, and the Makefile ldflags that stamp the version symbol. The runtime surface is already corrected (iss-2608241659573856) because it was breaking fresh installs; this is the rest. TestInstallGuideDocumentsTheInstallAndUpdatePath derives the documented marketplace slug from go.mod's module path, so go.mod, README.md and docs/how-to/install.md must move in one change or the gate fails - which is the detector working. Renaming the module path is a breaking change for any Go importer, judged near-zero cost because abcd is a CLI rather than a library and is pre-1.0. Deliberately out of scope: CHANGELOG.md's entry for the EARLIER transfer to the old organisation, and the historical records under .abcd/, which state facts about the past that rewriting would falsify.