Repository navigation
release: promote mastering application package 2.0.0 - #17
Merged
Merged
Conversation
Import GeoJSON Polygon and URI records, share EPSG and spectral-band enums, and adapt command bindings to the existing application interface. BREAKING CHANGE: Local CWL jobs must supply Polygon AOIs and URI records instead of plain strings. Workflow EPSG values now use the 4326 enum.
Use typed YAML jobs in local CWL labs and documentation scripts, document release input compatibility, and refresh generated reference pages and diagrams.
Build processing wheels in multistage containers, preserve dependency pins and remote-read retries, and align CWL bindings with polygon masking and explicit raster options. BREAKING CHANGE: processing tools require Python 3.12 or newer and installed console commands. Rebuild local images; normalized difference and STAC use repeated raster options, and Otsu uses --raster.
Test the synthetic processing chain, build wheels and images, update mandatory Docker requirements with release digests, and preserve metadata while embedding workflow schemas.
Install processing packages in lab environments, use the new CLI options and host-user container mapping, explain polygon masking, and refresh CWL references and diagrams.
Replace embedded staging scripts with installed Python commands and dedicated multistage images while preserving CWL job inputs and legacy released examples. Fail incomplete downloads and retain destination prefixes for absolute asset paths.
Include stage-in and stage-out in package tests, wheel builds, container smoke checks, and the release image matrix.
Update the staging notebook and documentation for installed commands, separate images, bounded downloads, and catalog uploads.
Pass GeoJSON polygons to crop and separate Podman flags from image names in container help cells.
feat!: prepare 2.0.0 application packages and release pipeline
fix(kubernetes): use published release candidates for portable labs
fix(stage-out): publish complete Zarr stores for cross-module reuse
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
1 participant
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.
Promote the validated 2.0.0 release candidate source to main and publish the stable application packages and six GHCR processing images through the release workflow.
Validation: candidate 2.0.0-rc.42.1 passed all 41 CI tests and container security scans. Both chapter 5 notebooks passed, including direct Calrissian execution, Kubernetes Job execution and benchmarks. The published stage-out image uploaded the real Sentinel-2 Zarr output successfully; STAC metadata and TiTiler NDWI/water rendering were verified. Chapters 1–4 were previously validated against rc.41.1.
Includes complete Zarr v2/v3 stage-out support required by the Zarr module, CWL v1.2 application packages and typed inputs. The stable promotion retains the candidate source tree.