This is an automated email from the ASF dual-hosted git repository. vatsrahul1001 pushed a commit to branch fix-constraints-push-ambiguous-refspec in repository https://gitbox.apache.org/repos/asf/airflow.git
commit cfad896bde39f7377e7245b7a27a833992f77694 Author: Rahul Vats <[email protected]> AuthorDate: Wed Aug 5 19:21:44 2026 +0530 Fix ambiguous git refspec when pushing release-candidate constraints For a release candidate the constraints branch and tag are both named constraints-<VERSION>, so pushing them by bare name fails with "src refspec ... matches more than one" whenever both a local branch and tag of that name exist (e.g. on a re-run after the tag was already created). Qualify the refspecs so the branch and tag pushes are unambiguous. --- .github/workflows/release-constraints.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release-constraints.yml b/.github/workflows/release-constraints.yml index 4eb2f3042ca..94506af6f01 100644 --- a/.github/workflows/release-constraints.yml +++ b/.github/workflows/release-constraints.yml @@ -237,13 +237,15 @@ jobs: - name: "Push ${{ needs.build-info.outputs.target-branch }}" working-directory: "constraints" shell: bash - run: git push origin "${TARGET_BRANCH}" + # Qualify as refs/heads/ -- for a release candidate the branch and the tag share a name + # (both constraints-<VERSION>), so a bare refspec is ambiguous ("matches more than one"). + run: git push origin "refs/heads/${TARGET_BRANCH}" - name: "Tag constraints-${{ inputs.version }}" working-directory: "constraints" shell: bash run: | git tag -a "constraints-${VERSION}" -m "Constraints for Apache Airflow ${VERSION}" - git push origin "constraints-${VERSION}" + git push origin "refs/tags/constraints-${VERSION}" - name: "Summary" shell: bash run: |
