Skip to content

Conversation

@jedcunningham
Copy link
Member

Turns out the VERSION_SUFFIX env var is used as the default for the --version-suffix flag, and we do not want it set when we are preparing the package.

More permanent fix coming soon, but this unblocks PMC verification for 1.19.0rc2.

Related: #61303

Turns out the VERSION_SUFFIX env var is used as the default for the
--version-suffix flag, and we do not want it set when we are preparing
the package.

More permanent fix coming soon, but this unblocks PMC verification for
1.19.0rc2.

Related: apache#61303
@jedcunningham jedcunningham merged commit 27ea947 into apache:main Feb 1, 2026
66 checks passed
@jedcunningham jedcunningham deleted the fix_helm_release_round_2 branch February 1, 2026 08:20
@github-actions
Copy link

github-actions bot commented Feb 1, 2026

Backport failed to create: v3-1-test. View the failure log Run details

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 27ea947 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

morelgeorge pushed a commit to morelgeorge/airflow that referenced this pull request Feb 1, 2026
Turns out the VERSION_SUFFIX env var is used as the default for the
--version-suffix flag, and we do not want it set when we are preparing
the package.

More permanent fix coming soon, but this unblocks PMC verification for
1.19.0rc2.

Related: apache#61303
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants