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

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

Build:
Build:
LAST BUILD BRANCH: init-skip-non-runtime-dockerfile
DEFAULT BRANCH: main
Ran 14 Oct 2026 04:02PM UTC
Jobs 1
Files 335
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 03:57PM UTC coverage: 57.898% (-0.2%) from 58.075%
38593917777

push

github

web-flow
Deploy only pyproject.toml projects in v2 (#2295)

* Deploy only pyproject.toml projects in v2

v2 deploys only projects with a pyproject.toml, on Astro and on Astro
Private Cloud. Astro CLI 1.x keeps deploying the projects it made, so v2
drops the 1.x deploy rather than carrying it.

Astro: astro deploy in a 1.x-layout project (a Dockerfile beside .astro,
or a .astro/config.yaml) fails with no_project, saying to convert it with
astro init or deploy it with Astro CLI 1.x. Outside any project it gives
the no-project advice, now also no_project. --non-dags runs first, from
anywhere: it deploys a separate directory, and from a pyproject.toml
project it no longer runs a whole project deploy instead.

APC: v2 builds no project. A deploy without --image-name is refused as a
usage error saying to use Astro CLI 1.x (and, from a pyproject.toml
project, that support is coming). --image-name (and --remote) deploy
from anywhere but a 1.x project; --dags uploads a pyproject.toml
project's dags/. Any deploy from a 1.x project is refused.

The 1.x deploy is deleted with its tests: deploy.Deploy and its build,
pytest and parse steps, the named DAG bundle create, APC's Dockerfile
build, airflow's DAGChecker and ImageHandler.Pytest, and what deadcode
found behind them. The flags only it read are removed and tombstoned in
the removed-flags registry: --save, --pytest, --env, --test, --parse,
--deployment-name, --dags-path and --dag-bundle-name on Astro, --save and
--no-cache on APC.

From #2290: config.IsHomeDir in IsProjectDir, the home-directory advice,
and the bound-value --image-name check.

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

* Deploy an image from anywhere, and one rule for what a project is

From review of the first commit:

- astro deploy --image-name runs from any directory again, a 1.x project's
  included: it reads nothing from the project. Outside a pyproject.toml
  project it ships the image alone (no dags/), to an id named by the
  argument or -... (continued)

400 of 443 new or added lines in 14 files covered. (90.29%)

18 existing lines in 5 files now uncovered.

40180 of 69398 relevant lines covered (57.9%)

255.49 hits per line

Uncovered Changes

Lines Coverage ∆ File
27
84.99
0.16% cmd/astro/deploy.go
10
94.39
-2.32% internal/deploy/deploy.go
3
76.75
-1.98% internal/platform/astro/deploy/bundle.go
2
96.3
-3.7% cmd/utils/utils.go
1
97.3
1.14% cmd/astro/dbt_render.go

Coverage Regressions

Lines Coverage ∆ File
10
84.94
3.01% internal/platform/astro/deploy/deploy.go
3
79.76
-1.32% airflow/docker_image.go
3
76.75
-1.98% internal/platform/astro/deploy/bundle.go
1
84.99
0.16% cmd/astro/deploy.go
1
96.3
-3.7% cmd/utils/utils.go
Jobs
ID Job ID Ran Files Coverage
1 38593917777.1 14 Oct 2026 04:02PM UTC 335
57.9
GitHub Action Run
Source Files on build 38593917777
  • Tree
  • List 335
  • Changed 24
  • Source Changed 24
  • Coverage Changed 23
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #38593917777
  • 4070d4ec on github
  • Prev Build on v2 (#38582239282)
  • Next Build on v2 (#38599781424)
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