Skip to content

Pin manifest-builder to exactly 0.7.14 - #107

Merged
ps-pufferfish merged 1 commit into
mainfrom
pin-manifest-builder
Sep 25, 2026
Merged

ps-pufferfish merged 1 commit into
mainfrom
pin-manifest-builder

Conversation

@ps-pufferfish

Copy link
Copy Markdown
Contributor

manifest-builder>=0.7.13 would accept 0.8.0 on any relock (uv lock --upgrade, Renovate, a dependency sweep). 0.8.0 (PortSwigger/manifest-builder#149) drops GenerationResult.deploy_id, so relcoord main would then fail every change with deployment detection on. It needs the code in #106 to go with that version.

Pinning exactly also means builder upgrades, which change the generated manifests, only happen in a PR meant for them.

Lock unchanged apart from the specifier; still resolves 0.7.14. All 469 tests pass with uv sync --locked.

A relock would otherwise take any newer release, and 0.8.0 will drop the deploy-id relcoord still depends on. The generated manifests depend on the builder version too, so moving it should be a deliberate change of its own.
@ps-pufferfish
ps-pufferfish merged commit e850810 into main Sep 25, 2026
4 checks passed
@ps-pufferfish
ps-pufferfish deleted the pin-manifest-builder branch September 25, 2026 13:56
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