feat: adding the option to add bundle version parameter on dag run trigger endpoint

[itayweb]

A new feature in the dag run REST API, adding the option to add bundle version parameter to trigger specific version.
Wasn't sure how can I add to this a unit test due to need a git repo/s3 bucket, let me know if needed

• closes: Support bundle version param in trigger dag run endpoint #60484

---

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

• Yes (please specify the tool below)

Generated-by: [Cursor] following the guidelines

[pierrejeambrun]

Overall this looks good to me.

Can you add unit tests to verify that behavior when we actually pass a 'bundle_version'.

I'd love a second look from versioning experts.

[jason810496]

Thanks for the improvement!

Please add the corresponding tests when you are convenient, thanks.

[pierrejeambrun]

Can you add the requested unit tests please so we can merge this.

[itayweb]

I've added the unit test, let me know what do you think 😄 sorry for the delay

[potiuk]

You need to rebase.

[pierrejeambrun]

Good feature. The core trickiness (TIs must be built from the resolved older dag, not the live one) is handled correctly and tested. Some concerns below, mostly around deduplication of the DagVersion lookup and the branching logic in _create_orm_dagrun.

CI need fixing.

[potiuk]

@itayweb Converting to draft — this PR doesn't yet meet our Pull Request quality criteria.

• ❌ Merge conflicts: this branch has conflicts with main and cannot be merged as-is. Rebase: git fetch upstream main && git rebase upstream/main, resolve, force-push.
• ❌ Failing CI: Special tests / Pendulum2 test: core / All-core:Pendulum2-Postgres:14:3.10:API...CLI, Special tests / Latest SQLAlchemy test: core / DB-core:LatestSQLAlchemy-Postgres:14:3.10:API...CLI, Special tests / Latest Boto test: core / All-core:LatestBoto-Postgres:14:3.10:API...CLI (+5 more). Please investigate and fix.
• ❌ Unresolved review comments (8 threads (from maintainers)): please walk through each unresolved review thread. Even if a suggestion looks incorrect or irrelevant — and some of them will be, especially any comments left by automated reviewers like GitHub Copilot — it is still the author's responsibility to respond: apply the fix, reply in-thread with a brief explanation of why the suggestion does not apply, or resolve the thread if the feedback is no longer relevant. Once you believe a thread is resolved — whether by pushing a fix or by explaining why the suggestion doesn't apply — please mark it as resolved yourself by clicking the 'Resolve conversation' button at the bottom of each thread. Reviewers don't auto-close their own threads, so an addressed-but-unresolved thread reads as 'still waiting on the author' and keeps the PR from moving forward.

See the linked criteria for how to fix each item, then mark the PR "Ready for review". This is not a rejection — just an invitation to bring the PR up to standard. No rush.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.