Skip to content
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

Merged

Conversation

zhenmichael
Copy link
Contributor

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.

alexvy86 and others added 9 commits February 23, 2024 12:55
…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]>
@zhenmichael zhenmichael requested review from msfluid-bot and a team as code owners March 5, 2024 16:31
@zhenmichael zhenmichael requested review from a team as code owners March 5, 2024 17:03
lerna-package-lock.json Outdated Show resolved Hide resolved
@zhenmichael
Copy link
Contributor Author

@tylerbutler @alexvy86 It looks like the PR is running into some build issues for
pr-labeler
. I'm not too sure about how the labeler works, so I was wondering if I should update
pr-labeler.yml
to match its state in the main branch. Also, are there any other relevant changes related to the github workflow that I may need to include?

@Abe27342
Copy link
Contributor

Abe27342 commented Mar 6, 2024

@tylerbutler @alexvy86 It looks like the PR is running into some build issues for pr-labeler . I'm not too sure about how the labeler works, so I was wondering if I should update pr-labeler.yml to match its state in the main branch. Also, are there any other relevant changes related to the github workflow that I may need to include?

You probably need this change: #19338

@zhenmichael
Copy link
Contributor Author

@tylerbutler @alexvy86 It looks like the PR is running into some build issues for pr-labeler . I'm not too sure about how the labeler works, so I was wondering if I should update pr-labeler.yml to match its state in the main branch. Also, are there any other relevant changes related to the github workflow that I may need to include?

You probably need this change: #19338

I believe this specific PR has already been cherry picked such that the permissions field is added to pr-labeler.yml and pr-validation.yml. However, it seems like there are still some differences between the pr-labeler.yml in main and the one in this server branch.

@tylerbutler
Copy link
Member

The only thing the labeler does is assign labels to this PR. It should not block merge.

Copy link
Contributor

@alexvy86 alexvy86 left a 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 :)

@zhenmichael zhenmichael merged commit d94975c into microsoft:release/server/0.1036.5000 Mar 7, 2024
18 of 19 checks passed
zhenmichael added a commit that referenced this pull request Apr 9, 2024
…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
zhenmichael added a commit that referenced this pull request Apr 11, 2024
… 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
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.

5 participants