Skip to content

Promote dev to main — adagio-cli 0.1.3 - #73

Merged
johnchase merged 19 commits into
mainfrom
dev
Oct 18, 2026
Merged

johnchase merged 19 commits into
mainfrom
dev

Conversation

@johnchase

Copy link
Copy Markdown
Contributor

Promote dev to main for the adagio-cli 0.1.3 release, preserving existing main history. Per RELEASING.md, v0.1.3 is tagged on the resulting main commit; publication rejects tags not contained in origin/main.

Contents since 0.1.2: #66 saved values as the lowest argument layer, #67 URL inputs with polymorphic types, #71 batch (#68 cleanup, #69 saved environments under --config, #70 output paths ending in / are directories), #72 version 0.1.3 and changelog.

Validation: CI on this PR; locally on dev, 281 tests pass and the 0.1.3 wheel and sdist pass twine check.

John Chase and others added 19 commits October 14, 2026 15:16
…ment layer

The .adg carries its values in configs[0], in the arguments-file shape.
adagio run reads it under --arguments and flags, --no-bundled-config
ignores it, adagio pipeline config prints it, and the adapter-facing
runtime command applies it under the job's arguments. Signatures no longer
carry defaults; older files that do are read the same way.
Apply the configuration bundled in a pipeline file as the lowest argument layer
Fix polymorphic URL artifact input validation
The bundled configuration stays the lowest argument layer and --help still
shows its values as defaults. Printing it as a separate command and ignoring
it wholesale added surface few users need: the arguments file can be
downloaded from the app, and any value can be overridden with --arguments or
a flag.
configs[0].execution in the .adg carries the environments and resources
the app would use, in the shape of a --config file. The CLI applies it as
the lowest environment layer; a --config file overrides it for every
field it sets. The run header lists each plugin's environment and its
source.
The output is written into it under its own name: --output-table
/data/run1/ writes /data/run1/table.qza. The same rule applies to publish
destinations and to output paths in a pipeline file's config or an
arguments file. Only the text decides, never the disk, so a shared
pipeline means the same thing on every machine.
@johnchase
johnchase merged commit 6d579c5 into main Oct 18, 2026
8 checks passed
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