Skip to content

Move azure-http-specs to lockstep chronus version policy#4913

Open
timotheeguerin with Copilot wants to merge 1 commit into
mainfrom
copilot/move-azure-http-specs-to-lock-step-chronus-policy
Open

Move azure-http-specs to lockstep chronus version policy#4913
timotheeguerin with Copilot wants to merge 1 commit into
mainfrom
copilot/move-azure-http-specs-to-lock-step-chronus-policy

Conversation

Copilot AI commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

@azure-tools/azure-http-specs was not part of the typespec-azure lockstep version policy, meaning it versioned independently from the rest of the Azure TypeSpec packages.

Changes

  • Added @azure-tools/azure-http-specs to the typespec-azure lockstep policy in .chronus/config.yaml

Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@timotheeguerin
timotheeguerin marked this pull request as ready for review July 16, 2026 15:25
@azure-sdk-automation

Copy link
Copy Markdown
Contributor

No changes needing a change description found.

@azure-sdk-automation

Copy link
Copy Markdown
Contributor

You can try these changes here

🛝 Playground 🌐 Website

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.

2 participants