fix: ensure version-cal-output artifact is always created for version-output job#10038
Draft
Copilot wants to merge 2 commits into
Draft
fix: ensure version-cal-output artifact is always created for version-output job#10038Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @copilot, |
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
Collaborator
|
fix |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a
labeled/unlabeledevent fires for therelease-version-blocklabel, bothversion-calandskip-version-calwere skipped — leaving no artifact forversion-outputto download, causing it to fail.Change
.github/workflows/VersionCalPRComment.ymlskip-version-cal'sifcondition to also trigger when the event islabeledorunlabeledforrelease-version-block, so a default artifact is always uploaded forversion-outputto consume: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
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (azdevrequired; see.azure-pipelines/templates/azdev_setup.ymlfor the install command untilazdev==0.2.11b1is on PyPI)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.jsonautomatically.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.