Skip to content

fix: repoint civiccore wheel dependency to townlight/core (post org-transfer) - #180

Closed
scottconverse wants to merge 1 commit into
mainfrom
fix/civiccore-release-url-post-org-transfer
Closed

scottconverse wants to merge 1 commit into
mainfrom
fix/civiccore-release-url-post-org-transfer

Conversation

@scottconverse

Copy link
Copy Markdown
Contributor

Part of the 2026-08-12 CivicSuite -> townlight org-transfer maintenance, tracked from townlight/townlight PR #246.

Context

The CivicSuite org (including this repo) was transferred to the townlight org on 2026-08-12 ~17:45 UTC, with CivicSuite retained as an empty redirect tombstone. civiccore itself was also independently renamed CivicSuite/civiccore -> townlight/core at an earlier point.

pyproject.toml's pinned civiccore wheel dependency still points at the old CivicSuite/civiccore location, so resolving it requires riding an org-rename + repo-rename redirect chain. In the hours following the transfer, this class of URL (same pattern, hit from a sibling module's identical dependency) repeatedly failed with "too many 503 error responses" during Docker builds in the umbrella townlight/townlight repo's installer-cleanroom CI.

Fix

Repoints the URL at the canonical townlight/core release directly -- same tag (v1.2.0), same asset, same sha256, verified reachable via curl before opening this PR. Removes the redirect hop instead of depending on it indefinitely.

Not merged -- opened for review since this branch was cut directly from the exact commit townlight/townlight's CI workflows currently pin (fa1874edfe977bfc36ddea2939df6464b5bc16be), so merging changes what that pin resolves to; whoever owns the pin bump in townlight/townlight should coordinate that alongside merging this.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

…ransfer)

CivicSuite org (repo included) was transferred to townlight on 2026-08-12
~17:45 UTC, with CivicSuite retained as an empty redirect tombstone.
civiccore itself was independently renamed CivicSuite/civiccore ->
townlight/core at an earlier point too.

The pinned civiccore wheel dependency here still points at the old
CivicSuite/civiccore location, riding a redirect chain (org rename +
repo rename) to resolve. In the hours after the transfer this class of
URL repeatedly hit "too many 503 error responses" pulling the civiccore
wheel during Docker builds in the umbrella townlight/townlight repo's
installer-cleanroom and desktop-windows-msi CI, e.g. (from a sibling
module hitting the identical URL):

    Collecting civiccore@ https://github.com/CivicSuite/civiccore/releases/download/v1.2.0/civiccore-1.2.0-py3-none-any.whl#sha256=... (from civicnotice==0.2.0)
    ERROR: Could not install packages due to an OSError: HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded with url: /CivicSuite/civiccore/releases/download/v1.2.0/civiccore-1.2.0-py3-none-any.whl (Caused by ResponseError('too many 503 error responses'))

Repoints the URL at the canonical townlight/core release directly (same
tag, same asset, same sha256 -- verified reachable) to remove the redirect
hop. Part of the 2026-08-12 CivicSuite -> townlight org-transfer cleanup
tracked from townlight/townlight PR #246.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@scottconverse

Copy link
Copy Markdown
Contributor Author

Superseded by #181 (full sweep, tests updated in lockstep).

@scottconverse
scottconverse deleted the fix/civiccore-release-url-post-org-transfer branch September 8, 2026 17:38
scottconverse added a commit that referenced this pull request Sep 8, 2026
…r) (#181)

* fix: repoint CivicSuite org references to townlight (post org-transfer)

The repos moved from the CivicSuite org to townlight on 2026-08-12. This
sweeps live code, workflows, scripts, install docs, and the tests that
assert the civiccore wheel URL from github.com/CivicSuite/* to the
townlight/* homes (civiccore -> core, civicclerk -> meetings,
civiccode -> ordinances, civicrecords-ai -> sunshine).

Left as-is on purpose: CHANGELOG.md, docs/audits and docs/evidence,
tier1-retrofit-ledger.json, release_provenance fixtures, and every
Sigstore workflow identity or --repo used to verify attestations that
were signed under the CivicSuite identity before the transfer.

Supersedes #180.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* chore(frontend): npm audit fix for nanoid and postcss high advisories

The CI and cleanroom npm-audit gates fail on two transitive dev
dependencies: nanoid <=3.3.17 (GHSA-28wg-ghj8-5hjv, GHSA-2v37-7h3g-55p8)
and postcss <=8.5.22 (GHSA-fxqj-rqcc-2cmp, GHSA-r28c-9q8g-f849). npm audit
fix bumps nanoid 3.3.12 -> 3.3.18 and postcss 8.5.15 -> 8.5.28 in the
lockfile only; package.json is unchanged. npm audit now reports 0
vulnerabilities, the Vite build succeeds, and vitest passes 33/33.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* test: assert the townlight/core wheel URL in the release-workflow contract test

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: Scott Converse <scottconverse@users.noreply.github.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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