Skip to content

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Nov 1, 2025

  • Add Task SDK support to start-release command

Enhance the breeze release-management start-release command to handle
Task SDK releases alongside Airflow releases, matching the functionality
of the start-rc-process command.

Changes:

  • Add optional --task-sdk-release-candidate parameter to start-release
  • Update SVN operations to handle both Airflow and Task SDK artifacts
  • Support uploading both packages to PyPI separately
  • Create and push tags for both Airflow and Task SDK releases
  • Improve documentation with environment variables for all version parameters
  • Add concrete examples for publish-docs commands

This allows release managers to release Airflow and Task SDK together
in a single workflow or release Airflow independently when Task SDK
updates are not needed.

  • Update vote email template to include Task SDK

Update the vote email template to include Task SDK release information,
based on the format used in recent releases.

Changes:

  • Add TASK_SDK_VERSION_WITHOUT_RC environment variable
  • Update subject line to include both Airflow and Task SDK versions
  • Add separate sections for Task SDK artifacts
  • Include Task SDK in PyPI installation instructions
  • Add docs preview and release notes links
  • Add simplified uv-based installation example
    (cherry picked from commit 1c845c2)

Co-authored-by: Kaxil Naik kaxilnaik@gmail.com

)

* Add Task SDK support to start-release command

Enhance the breeze release-management start-release command to handle
Task SDK releases alongside Airflow releases, matching the functionality
of the start-rc-process command.

Changes:
- Add optional --task-sdk-release-candidate parameter to start-release
- Update SVN operations to handle both Airflow and Task SDK artifacts
- Support uploading both packages to PyPI separately
- Create and push tags for both Airflow and Task SDK releases
- Improve documentation with environment variables for all version parameters
- Add concrete examples for publish-docs commands

This allows release managers to release Airflow and Task SDK together
in a single workflow or release Airflow independently when Task SDK
updates are not needed.

* Update vote email template to include Task SDK

Update the vote email template to include Task SDK release information,
based on the format used in recent releases.

Changes:
- Add TASK_SDK_VERSION_WITHOUT_RC environment variable
- Update subject line to include both Airflow and Task SDK versions
- Add separate sections for Task SDK artifacts
- Include Task SDK in PyPI installation instructions
- Add docs preview and release notes links
- Add simplified uv-based installation example
(cherry picked from commit 1c845c2)

Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Nov 1, 2025
@potiuk potiuk marked this pull request as ready for review November 1, 2025 18:15
@potiuk potiuk merged commit 6ffc740 into v3-1-test Nov 1, 2025
6 checks passed
@potiuk potiuk deleted the backport-1c845c2-v3-1-test branch November 1, 2025 18:15
ephraimbuddy pushed a commit that referenced this pull request Nov 3, 2025
) (#57666)

* Add Task SDK support to start-release command

Enhance the breeze release-management start-release command to handle
Task SDK releases alongside Airflow releases, matching the functionality
of the start-rc-process command.

Changes:
- Add optional --task-sdk-release-candidate parameter to start-release
- Update SVN operations to handle both Airflow and Task SDK artifacts
- Support uploading both packages to PyPI separately
- Create and push tags for both Airflow and Task SDK releases
- Improve documentation with environment variables for all version parameters
- Add concrete examples for publish-docs commands

This allows release managers to release Airflow and Task SDK together
in a single workflow or release Airflow independently when Task SDK
updates are not needed.

* Update vote email template to include Task SDK

Update the vote email template to include Task SDK release information,
based on the format used in recent releases.

Changes:
- Add TASK_SDK_VERSION_WITHOUT_RC environment variable
- Update subject line to include both Airflow and Task SDK versions
- Add separate sections for Task SDK artifacts
- Include Task SDK in PyPI installation instructions
- Add docs preview and release notes links
- Add simplified uv-based installation example
(cherry picked from commit 1c845c2)

Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
ephraimbuddy pushed a commit that referenced this pull request Nov 4, 2025
) (#57666)

* Add Task SDK support to start-release command

Enhance the breeze release-management start-release command to handle
Task SDK releases alongside Airflow releases, matching the functionality
of the start-rc-process command.

Changes:
- Add optional --task-sdk-release-candidate parameter to start-release
- Update SVN operations to handle both Airflow and Task SDK artifacts
- Support uploading both packages to PyPI separately
- Create and push tags for both Airflow and Task SDK releases
- Improve documentation with environment variables for all version parameters
- Add concrete examples for publish-docs commands

This allows release managers to release Airflow and Task SDK together
in a single workflow or release Airflow independently when Task SDK
updates are not needed.

* Update vote email template to include Task SDK

Update the vote email template to include Task SDK release information,
based on the format used in recent releases.

Changes:
- Add TASK_SDK_VERSION_WITHOUT_RC environment variable
- Update subject line to include both Airflow and Task SDK versions
- Add separate sections for Task SDK artifacts
- Include Task SDK in PyPI installation instructions
- Add docs preview and release notes links
- Add simplified uv-based installation example
(cherry picked from commit 1c845c2)

Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
@ephraimbuddy ephraimbuddy added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label Nov 10, 2025
@ephraimbuddy ephraimbuddy added this to the Airflow 3.1.3 milestone Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants