• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

astronomer / astro-cli / 38581372048
58%
main: 45%

Build:
Build:
LAST BUILD BRANCH: init-skip-non-runtime-dockerfile
DEFAULT BRANCH: main
Ran 14 Oct 2026 02:36PM UTC
Jobs 1
Files 334
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Oct 2026 02:32PM UTC coverage: 57.851% (+0.002%) from 57.849%
38581372048

push

github

web-flow
Guard removed 1.x commands in CI, and give bundle create/update/delete -o json (#2291)

* Guard every removed 1.x command in CI, and say "removed in Astro CLI v2" everywhere

cmd/testdata/v1_commands.tsv is the inventory of every visible 1.x command,
in the trees v1_flags.tsv names (astro, astro-hosted, apc). Only the tests
read it. TestEveryV1CommandStillRunsOrSaysWhatReplacedIt resolves each path
against its v2 trees (APC at both ends of its version gates) and fails on
one that stops at a command with words left over: a command dropped without
a stub, or renamed without its 1.x name as an alias. Every stub a path
reaches is run with the other hooks disarmed, in text and under -o json:
a usage error, "was removed in Astro CLI v2" and a replacement (or none),
no pre-run, and the error object on stdout.

What it found, now fixed:
- `astro dev` failed with exit 1, not 2, and its json payload lacked the
  error object's code and kind. It is a usage error now, and its payload
  leads with error, code and kind before the mapping.
- `astro env ... create|update` ran the env group's pre-run (project and
  login) before the guidance; they skip it, as the deployment stubs do.
- The deployment and env stubs said "removed in v2"; they say "removed in
  Astro CLI v2", as dev, run and the removed flags do. `deployment pool`
  says there is no replacement in the CLI yet.

The assembled root's local commands publish to the root's out (os.Stdout in
production), so a test of the root reads what they print.

Co-Authored-By: Claude <noreply@anthropic.com>

* Give astro deployment bundle create, update and delete -o json, and unhide them

They were hidden only because they printed prose and every visible command
offers --output json. Now, under -o json:

- create and update publish the bundle as the change left it, in the shape
  bundle list gives each one (deployment-bundle.json);
- delete publishes what it deleted: id, deployment_id and action "deleted",
  as the deplo... (continued)

187 of 232 new or added lines in 15 files covered. (80.6%)

1 existing line in 1 file now uncovered.

40350 of 69748 relevant lines covered (57.85%)

245.2 hits per line

Uncovered Changes

Lines Coverage ∆ File
23
0.0
cmd/cliout/removed.go
12
85.32
1.45% internal/platform/astro/deployment/bundle.go
7
50.0
-1.08% internal/telemetry/telemetry.go
3
84.0
0.33% cmd/astro/project_scope.go

Coverage Regressions

Lines Coverage ∆ File
1
84.0
0.33% cmd/astro/project_scope.go
Jobs
ID Job ID Ran Files Coverage
1 38581372048.1 14 Oct 2026 02:36PM UTC 334
57.85
GitHub Action Run
Source Files on build 38581372048
  • Tree
  • List 334
  • Changed 15
  • Source Changed 15
  • Coverage Changed 14
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #38581372048
  • 67a8d757 on github
  • Prev Build on v2 (#38580256031)
  • Next Build on v2 (#38582239282)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc