Align pipeline runtime with data-model release #40
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.
Summary
build.ymljob keeps producing runnablemain/latestimages[email protected]and lean on its dependency stack instead of duplicatingxarray/zarrversion rangesmainimage tag, making the staging overlay patch unnecessaryuv.lockunder the new constraintsTesting
uv run -q pytest -q(suite currently reports "no tests ran"; coverage emits standard warning)Follow-up
Build Docker Imageafter merge to refreshghcr.io/eopf-explorer/data-pipeline:{main,latest}data-model#65(fix: sync v0.3.0 metadata data-model#65) to aligneopf-geozarrpackaging metadata with tagv0.3.0(or adopt SCM-based versioning)