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

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

Build:
Build:
LAST BUILD BRANCH: fix/within-project-dir-cwd
DEFAULT BRANCH: main
Ran 20 Oct 2026 12:23AM UTC
Jobs 1
Files 344
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 12:19AM UTC coverage: 60.353% (+0.04%) from 60.312%
39346980441

push

github

web-flow
Tell a converted 1.x script what replaced each astro dev flag (#2382)

* Say what astro init carries from a 1.x project in its help

The help still said a requirements.txt was listed at the end, to move
across by hand, but init has migrated it into pyproject.toml's
dependencies since the conversion landed, with packages.txt,
airflow_settings.yaml and a Dockerfile that does more than pick a base
image. It now says so, that a 1.x file goes once everything it said is
in pyproject.toml, and that what is listed at the end is what could not
be carried, such as a requirements.txt line that is not a plain
requirement.

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

* Tell a converted 1.x script what replaced each astro dev flag

astro dev is a stub, so its flags were never tombstoned, and a script
converted by renaming the command (astro dev init to astro init, astro
dev start to astro local start) was told only "unknown flag" for
--runtime-version, --no-browser, --wait and the rest. The same went for
the flags 1.x kept hidden as deprecated, which v1_flags.tsv did not
record.

A v2 command that replaced a 1.x one under another name now answers for
the flags its predecessor had (v1Predecessors): astro init for astro dev
init, astro local start, restart, stop, status, logs, shell, check and
reset, astro package, and the root's start, stop and logs. The map
follows scaffold.DevReplacements, which a test holds it to; dev run
(which parsed no flags), pytest (uv run pytest) and object (no flag of
astro local env does what theirs did) are left out. A shorthand 1.x gave
a flag the command still has under its long name alone, as astro init
-n and astro local start -p, says to use the long name.

v1_flags.tsv records the deprecated flags 1.x still accepted: deploy's
--force-upgrade-to-af3, deployment create's --cluster-type, create and
update's --enforce-cicd, and APC deployment delete's --hard. --strict
needs nothing: in 1.x it was on env ... update, whose stub alrea... (continued)

82 of 83 new or added lines in 2 files covered. (98.8%)

41034 of 67990 relevant lines covered (60.35%)

368.06 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
94.83
1.7% cmd/removed_flags.go
Jobs
ID Job ID Ran Files Coverage
1 39346980441.1 20 Oct 2026 12:23AM UTC 344
60.35
GitHub Action Run
Source Files on build 39346980441
  • Tree
  • List 344
  • Changed 2
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #39346980441
  • 067597af on github
  • Prev Build on v2 (#39334836546)
  • Next Build on v2 (#39350257591)
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