fix: repoint civiccore wheel dependency to townlight/core (post org-transfer) - #107
Closed
scottconverse wants to merge 1 commit into
Closed
scottconverse wants to merge 1 commit into
scottconverse wants to merge 1 commit into
Conversation
…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 repeatedly
hit "too many 503 error responses" pulling the wheel during Docker builds
in the umbrella townlight/townlight repo's installer-cleanroom and
desktop-windows-msi CI, e.g.:
Collecting civiccore@ https://github.com/CivicSuite/civiccore/releases/download/v1.2.0/civiccore-1.2.0-py3-none-any.whl#sha256=... (from civicrecords-ai==1.7.3)
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>
Collaborator
Author
|
Superseded by #110 (full sweep, tests updated in lockstep). |
scottconverse
deleted the
fix/civiccore-release-url-post-org-transfer
branch
September 8, 2026 17:39
scottconverse
added a commit
that referenced
this pull request
Sep 8, 2026
…r) (#110) * 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 #107. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * chore(frontend): npm audit fix plus tiptap lockstep bump to 3.31.3 The frontend audit gate fails on browserslist (GHSA-c83g-rgw3-j3cx, GHSA-73wf-gq98-2v4g), @tiptap/core (GHSA-cp6q-959q-f8rh), and postcss-selector-parser (GHSA-w9m9-85wc-3x92). npm audit fix alone bumps @tiptap/core to 3.31.3 while @tiptap/react stays at 3.22.x, and the Vite build then fails on a missing schedulePositionCheck export. Bump the four declared @tiptap packages to ^3.31.3 so every tiptap package resolves to 3.31.3. npm audit: 0 vulnerabilities; vite build succeeds; vitest 42/42. 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
townlightorg on 2026-08-12 ~17:45 UTC, withCivicSuiteretained as an empty redirect tombstone.civiccoreitself was also independently renamedCivicSuite/civiccore->townlight/coreat an earlier point.backend/pyproject.toml's pinnedciviccorewheel dependency still points at the oldCivicSuite/civiccorelocation, so resolving it requires riding an org-rename + repo-rename redirect chain. In the hours following the transfer this repeatedly failed with"too many 503 error responses"when pulled during Docker builds in the umbrellatownlight/townlightrepo'sinstaller-cleanroomCI (this repo checked out at the exact commit this PR is based on):Fix
Repoints the URL at the canonical
townlight/corerelease directly -- same tag (v1.2.0), same asset, samesha256, verified reachable viacurlbefore 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 (e2208827b660faa7d3fc1eab2271a8eae18526ee), so merging changes what that pin resolves to; whoever owns the pin bump intownlight/townlightshould coordinate that alongside merging this.Co-Authored-By: Claude Fable 5 noreply@anthropic.com