Skip to content

fix: ensure version-cal-output artifact is always created for version-output job#10038

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-version-output-job
Draft

fix: ensure version-cal-output artifact is always created for version-output job#10038
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-version-output-job

Conversation

Copilot AI commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

When a labeled/unlabeled event fires for the release-version-block label, both version-cal and skip-version-cal were skipped — leaving no artifact for version-output to download, causing it to fail.

Change

.github/workflows/VersionCalPRComment.yml

  • Extended skip-version-cal's if condition to also trigger when the event is labeled or unlabeled for release-version-block, so a default artifact is always uploaded for version-output to consume:
# Before
if: ${{ contains(github.event.pull_request.labels.*.name, 'skip-cal-version') }}

# After
if: ${{ contains(github.event.pull_request.labels.*.name, 'skip-cal-version') || (contains(fromJSON('["labeled", "unlabeled"]'), github.event.action) && github.event.label.name == 'release-version-block') }}

The two upstream jobs (version-cal / skip-version-cal) remain mutually exclusive across all event types.


This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

N/A — workflow-only change

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • Have you run python scripts/ci/test_index.py -q locally? (azdev required; see .azure-pipelines/templates/azdev_setup.yml for the install command until azdev==0.2.11b1 is on PyPI)
  • My extension version conforms to the Extension version schema

For new extensions:

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

@azure-client-tools-bot-prd

azure-client-tools-bot-prd Bot commented Jun 24, 2026

Copy link
Copy Markdown
️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes

@azure-client-tools-bot-prd

Copy link
Copy Markdown

Hi @copilot,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

Copilot AI changed the title [WIP] Fix failing GitHub Actions job for version calculation fix: ensure version-cal-output artifact is always created for version-output job Jun 24, 2026
Copilot AI requested a review from jsntcy June 24, 2026 04:49
@yonzhan

yonzhan commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator

fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants