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

astronomer / astro-cli / 39360245809
61%
main: 45%

Build:
Build:
LAST BUILD BRANCH: v2-ship-warning-style
DEFAULT BRANCH: main
Ran 20 Oct 2026 02:45AM UTC
Jobs 1
Files 345
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

20 Oct 2026 02:41AM UTC coverage: 60.381% (+0.003%) from 60.378%
39360245809

push

github

web-flow
Read --deployment and --workspace, with the 1.x spellings as aliases (#2378)

* Read --deployment and --workspace, with the 1.x spellings as aliases

Commands read the v2 flags now. --deployment-id, --deployment-name and
--workspace-id are hidden aliases, keeping 1.x's -d, -n and team add's -w,
that utils.ApplyAliases hands to the flag they stand for, refusing a
disagreement as before. --deployment knows the command's id and name and
splits once (deploymentFlag.resolve, routeDeployment's rule); an alias
keeps the kind it was typed as, so a non-CUID --deployment-id is still an
id and -d with -n is still both. followProject, create --clone and setup
read the v2 flags. The env link commands keep their own --deployment-id,
which still shadows the noun's scope flag.

An archlint test fails on a 1.x spelling named outside the alias helpers.
Nothing user-visible changes.

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

* Check 1.x spellings by constant value, and drop setup's dead dev branch

The archlint guard now type-checks cmd/ and internal/ and fails on any
expression whose constant value is a 1.x spelling, so a named constant
or a concatenation is caught where it is used. Allowed: arguments to
utils.AddAlias, and named functions and tables rather than whole files.
AddAlias returns its flag, so addDeploymentFlag looks nothing up by name.

Setup's astro dev branch is unreachable: a removed command's stub never
reaches the platform pre-run. It and workspaceOrDeploymentIDFlagSet go.

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

* Keep the 1.x spelling guard a plain literal scan

Revert the type-checked version: the guard catches an honest copy of the
old pattern, not deliberate evasion, so a scan of string literals under
cmd/ with a short file allowlist is enough. golang.org/x/tools goes back
to indirect.

The context cmd case of TestSetup relied on the deleted dev cases leaving
the login stubbed; it stubs it itself now.

Co-Authored-By: Claude <noreply... (continued)

192 of 203 new or added lines in 18 files covered. (94.58%)

5 existing lines in 1 file now uncovered.

41111 of 68086 relevant lines covered (60.38%)

394.08 hits per line

Uncovered Changes

Lines Coverage ∆ File
8
74.24
-16.38% cmd/utils/preferred_flags.go
3
96.91
-3.09% cmd/astro/preferred_flags.go

Coverage Regressions

Lines Coverage ∆ File
5
74.24
-16.38% cmd/utils/preferred_flags.go
Jobs
ID Job ID Ran Files Coverage
1 39360245809.1 20 Oct 2026 02:45AM UTC 345
60.38
GitHub Action Run
Source Files on build 39360245809
  • Tree
  • List 345
  • Changed 19
  • Source Changed 19
  • Coverage Changed 19
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #39360245809
  • fef34088 on github
  • Prev Build on v2 (#39360152563)
  • Next Build on v2 (#39447145560)
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