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]

@itayweb — There are 1 unresolved review thread(s) on this PR, and you have engaged with each one (post-review commits and/or in-thread replies). Could you confirm whether you believe the feedback is fully addressed and the PR is ready for maintainer review confirmation?

If yes, reply here (a short "yes / ready" is fine) and an Apache Airflow maintainer will pick the PR up from the review queue on the next sweep.

If you are still working on a thread, please reply with what is outstanding so the threads stay unresolved on purpose.

---

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.

---

Drafted-by: Claude Code (Opus 4.7); reviewed by @potiuk before posting

[itayweb]

@itayweb — There are 1 unresolved review thread(s) on this PR, and you have engaged with each one (post-review commits and/or in-thread replies). Could you confirm whether you believe the feedback is fully addressed and the PR is ready for maintainer review confirmation?

If yes, reply here (a short "yes / ready" is fine) and an Apache Airflow maintainer will pick the PR up from the review queue on the next sweep.

If you are still working on a thread, please reply with what is outstanding so the threads stay unresolved on purpose.

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.

Drafted-by: Claude Code (Opus 4.7); reviewed by @potiuk before posting

yes

[eladkal]

There are conflicts to resolve

[itayweb]

There are conflicts to resolve

Fixed, CI errors I am pretty sure not caused by my changes

[eladkal]

@itayweb can you handle the open comments?

[itayweb]

@itayweb can you handle the open comments?

Yes, I've already handled them locally but I have some issues with the pre-commit hook when trying to rebase my branch

[ashb]

Please follow the commit guidelines, particularly the commit/PR subject should not contain conventional commits.

[itayweb]

Please follow the commit guidelines, particularly the commit/PR subject should not contain conventional commits.

Oh didn't noticed you've changed your guidelines, do you prefer I'll squash all the existing commits to single commit to not include conventional commits?

[github-actions]

uv.lock on main just moved via #68400 ("Bump clickhouse-connect>=1.3.0"), commit 844a892 and this PR currently conflicts.

Quickest fix:

git fetch upstream main && git rebase upstream/main
rm uv.lock && uv lock
git add uv.lock && git rebase --continue
git push --force-with-lease

Automated nudge — ignore if you're not ready to rebase. This comment is updated in place on future uv.lock bumps.

[guan404ming]

Overall looks great. @itayweb could you help resolve the conflict, thanks!

[itayweb]

Overall looks great. @itayweb could you help resolve the conflict, thanks!

Done 👍