Repository navigation
Remove the archived policyengine-data repo from the inventory - #99
Merged
Merged
Conversation
policyengine-data has been archived (retired rather than moved to PyPI trusted publishing). Remove it from scripts/policyengine_repos.json, from REPO_KIND_OVERRIDES in scripts/build_manifest.py, and from the generated dashboard manifest. The policyengine-data skill is unrelated to the archived repo and is kept. Co-Authored-By: Claude Opus 5.5 <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
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.
What and why
The
policyengine-datarepo has been archived. It was retired instead of being moved to PyPI trusted publishing, the same way asreweight(#97): nothing in PolicyEngine imports the package, and itsdevextras pinpolicyengine-us==1.667.1, which is no longer on PyPI.scripts/policyengine_repos.jsonis meant to list only active repos, so this removes the repo from:scripts/policyengine_repos.jsonREPO_KIND_OVERRIDESinscripts/build_manifest.pydashboard/src/data/manifest.json: itsknown_reposandrepo_coverageentries, andpolicyengine-datafrom thetarget_reposof thepolicyengine-dataandpolicyengine-calibration-diagnosticsskillsThe
policyengine-dataskill is kept. It documents the Microcosm data stack and doesn't depend on the archived repo. The twotarget_reposmatches only existed becausebuild_manifest.pymatches repo names against skill text, and the skill's own name matched the repo's.As in #97, the manifest was edited directly rather than fully regenerated, to avoid unrelated rewrites. To check the edit, I ran
scripts/build_manifest.pybefore and after removing the repo from the inventory and compared the two outputs. The only differences were the four listed above (plus the order ofedges, which isn't stable between runs). Those four are exactly what this PR changes.Test plan
uv run pytest --ignore=tests/test_skill_examples.py: 178 passedpython3 scripts/build_claude_wrapper.py --source-root . --output-root <tmp>: succeeds🤖 Generated with Claude Code