Repository navigation
Conversation
The UK Autumn Budget 2026 dashboard scores each Budget measure against pre-Budget law, so it needs the pair that #731 certifies on policyengine-uk 2.165.1. Main has carried policyengine-uk 2.174.1 since #744, where current law includes the Budget, and both APIs pin that line. Releasing #731 from main would move them back. On this branch only, push.yaml: - runs on pushes to release/uk-autumn-budget-2026; - keeps Docs and Versioning for main, so no push here deploys the docs or bumps the version; - creates the GitHub release without marking it latest; - notifies the Budget dashboard only, not the APIs or the scorecard. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch was successfully deployed
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.
This PR runs CI on policyengine 6.16.2 before it publishes. Please don't merge it with the button. Once CI passes, I'll fast-forward
release/uk-autumn-budget-2026to this PR's head in one push. The branch tip then keeps the message "Update package version", sopush.yamlruns Publish, and GitHub marks this PR merged.Why a branch off main. The UK Autumn Budget 2026 dashboard scores each Budget measure against pre-Budget law, so it needs the pair that #731 certifies on policyengine-uk 2.165.1. Since #744, main and both APIs pin policyengine-uk 2.174.1, where current law includes the Budget. Merging #731 into main would publish 2.165.1 as PyPI's latest and open a bump PR on policyengine-api. So
release/uk-autumn-budget-2026starts at #731's head,e50a59d5, the tree that passed #731's 13 checks on 10 Nov.What the two commits change
fb02d2beditspush.yamlon this branch only. It runs on pushes to this branch, and it leaves Docs and Versioning to main, so no push here deploys the docs or bumps the version. It creates the GitHub release without marking it latest, and it notifies only the Budget dashboard, not the APIs or the scorecard.b542148stamps 6.16.2 with the release job's own steps, in the job's order:bump_version,towncrier,bundle.py generate,release_lock.py --refreshon the job's uv 0.13.4, the TRO regeneration andbundle.py check. It also adds a CHANGELOG line that says what the release serves.6.16.2 sorts below 6.17.2, so pip keeps installing the 6.17 line by default. The dashboard pins
policyengine[uk]==6.16.2.Checked locally on the stamped tree:
bundle.py check --published-spm --include-tros --strict-trosexits 0,release_lock.pyexits 0, and the tests that read the workflow files pass (333 passed, 1 skipped). Thepypienvironment now allows this branch beside main.🤖 Generated with Claude Code