-
Notifications
You must be signed in to change notification settings - Fork 567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade:Cim-schema to version 2.54.1 #11486
base: 3.0-dev
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we please rebase with 3.0-dev
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we please address github checks
Sorry falak I didn't got any notification mail for this pr working on it.
…________________________________
From: Muhammad Falak R Wani ***@***.***>
Sent: Monday, February 3, 2025 11:34 AM
To: microsoft/azurelinux ***@***.***>
Cc: Akarsh Chaudhary (HCL Technologies Ltd) ***@***.***>; Author ***@***.***>
Subject: Re: [microsoft/azurelinux] Upgrade:Cim-schema to version 2.54.1 (PR #11486)
@mfrw requested changes on this pull request.
can we please address github checks
—
Reply to this email directly, view it on GitHub<#11486 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMLIZPD6HUMA36AHRRSKIYD2N4BIVAVCNFSM6AAAAABTXUDWQ6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKOBYHE4DCMRWGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
7a010c9
to
a1d0f07
Compare
Requested changes done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we please investigate the failing buddy build
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./LICENSES-AND-NOTICES/SPECS/data/licenses.json
,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md
,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
What does the PR accomplish, why was it needed?
Change Log
Does this affect the toolchain?
NO
Associated issues
Links to CVEs
Test Methodology