[jason810496]

Why

A Go Dag definition that generates its Dags at run time, for example from a YAML file in the Dag bundle, registers nothing when airflow-go-pack runs it in a temp build dir, so packing failed with bundle exposes no dags: nothing to pack.

What

• airflow-go-pack now prints a warning and still writes the bundle when no Dags or task handlers are registered at pack time.

$ go tool airflow-go-pack --output bin/dynamic_dags ./example/dynamic
warning: no Dags or task handlers were registered at pack time; this is expected only if the bundle generates its Dags at run time, and those Dags show the entrypoint source in the Code view
Wrote bundle bin/dynamic_dags (sdk=go/..., task_handler_dags=0, native_dags=0)

• The bundle metadata schema and spec no longer require dags to be non-empty. It only lists Python Dags with stub TaskHandler, so a bundle of Dag definitions already wrote dags: {}.

---

Was generative AI tooling used to co-author this PR?

• Yes, with help of Claude Code (Claude Opus 5.5) following the guidelines

[guan404ming]

Looks nice!

[github-actions]

Backport successfully created: v3-4-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-4-test