Repository navigation
chore(models): deploy the new PV image - #63
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PV now echoes empty gemeente_code/gemeente_name in the run selection and versions production profiles as 1.1.0+<hash>. 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.
Updates the pv-map-api release identity pins (compose image and env,
layer-manifest.json, tests) from 357d7a9 to 0d40dbf (PV-MAP#30). Model 0.3.0 and metadata contract 2.1.0 are unchanged.Changes visible in the API: production profiles use generation method 1.1.0 (profile versions
1.1.0+<hash>),pv_capacitygains amunicipality_codeattribute, agemeenteselection type was added, and run echoes include emptygemeente_code/gemeente_namefields.orchestration.pynow accepts the last two.Checked in a throwaway network with a copy of the PV volume: production-profile runs succeed, the layer-publisher's fetch code accepts the new API (66 records), and the orchestrator's PV steps pass. PV, transformer-profile and publisher tests pass.
🤖 Generated with Claude Code