-
Notifications
You must be signed in to change notification settings - Fork 536
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
[server 0.1036.5000] Bump server version and update deps to address CVEs - fix #19959
[server 0.1036.5000] Bump server version and update deps to address CVEs - fix #19959
Conversation
This reverts commit 09c80ef.
…osoft#17389) (Cherry pick of a0368d6) Update the recommended versions of Node.js for developers to use, as well as the version used by CI, from version 14 to 18. This change made some scenarios in some e2e tests hang, so a fix for skipping them had to be included. Details: 0.58.x doesn't have the fix to routerlicious-driver in this PR: microsoft#8913 (also see related issue for more context on the problem: microsoft#9163) This causes this test to hang while loading container2, as the snapshot is over 16KB.
…osoft#19338) ## Description Updates pr-labeler and pr-validation to include a permissions block. See github permissions doc [here](https://docs.github.com/en/enterprise-cloud@latest/actions/using-workflows/workflow-syntax-for-github-actions#permissions). Co-authored-by: Abram Sanderson <[email protected]>
…on (microsoft#17389)" (Keep changes to server) This reverts commit 232921a.
…ion (microsoft#17389)" (Keep changes to server) This reverts commit 4b47802.
…on (microsoft#17389)". Keep server changes This reverts commit 232921a.
This reverts commit 1c7a3e8.
@tylerbutler @alexvy86 It looks like the PR is running into some build issues for |
You probably need this change: #19338 |
I believe this specific PR has already been cherry picked such that the |
The only thing the labeler does is assign labels to this PR. It should not block merge. |
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.
The dependency updates to address CVEs seem correct to me. The cherry-picked changes to get the pipelines to run also seem fine but if anyone else wants to give extra eyes on those, it'd be great.
Tyler's is right that the merge is not blocked right now by the pr-labeler failing, but because lack of approval :)
d94975c
into
microsoft:release/server/0.1036.5000
…s CVEs - fix (#20544) ## Description - Update dependencies in server npm packages to address [CVE-2023-45857](GHSA-wf5p-g6vw-rhxx) and [CVE-2024-21484](GHSA-rh63-9qcf-83gf). - Consume new server version 0.1036.5002 from this PR #19959 - Updated axios and jsrsasign deps versions Followup: A similar process will be repeated for updating the azure 1.1 release. Azure packages should be updated with: - server 0.1036.5002 - client 1.4.0 - updated versions for axios and jsrsasign
… CVEs - fix (#20566) ## Description - Update dependencies in azure npm packages to address [CVE-2023-45857](GHSA-wf5p-g6vw-rhxx) and [CVE-2024-21484](GHSA-rh63-9qcf-83gf). - Consume new server version 0.1036.5002 from this PR #19959 - Consume new client version 1.4.0 from this PR #20544 - Updated axios and jsrsasign deps versions
Testing changes from @alexvy86 PR: #19772
Reverted changes from cherry pick of 232921a
except for changes to server. Ideally, this will only trigger pipeline build for server which was passing previously.