Skip to content

Release policyengine 6.16.2 for the UK Autumn Budget dashboard - #747

Merged
MaxGhenis merged 2 commits into
release/uk-autumn-budget-2026from
hub/uk-autumn-budget-2026-release-6.16.2
Nov 12, 2026
Merged

MaxGhenis merged 2 commits into
release/uk-autumn-budget-2026from
hub/uk-autumn-budget-2026-release-6.16.2

Conversation

@MaxGhenis

Copy link
Copy Markdown
Contributor

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-2026 to this PR's head in one push. The branch tip then keeps the message "Update package version", so push.yaml runs 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-2026 starts at #731's head, e50a59d5, the tree that passed #731's 13 checks on 10 Nov.

What the two commits change

  1. fb02d2b edits push.yaml on 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.
  2. b542148 stamps 6.16.2 with the release job's own steps, in the job's order: bump_version, towncrier, bundle.py generate, release_lock.py --refresh on the job's uv 0.13.4, the TRO regeneration and bundle.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-tros exits 0, release_lock.py exits 0, and the tests that read the workflow files pass (333 passed, 1 skipped). The pypi environment now allows this branch beside main.

🤖 Generated with Claude Code

MaxGhenis and others added 2 commits November 11, 2026 10:25
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>
@MaxGhenis
MaxGhenis merged commit b542148 into release/uk-autumn-budget-2026 Nov 12, 2026
13 checks passed

This branch was successfully deployed

1 active deployment
pypi — b5421481 Deployed Nov 12, 2026 by MaxGhenis via Publish #344
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