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

Upgrade @babel/traverse #409

Merged
merged 3 commits into from
Dec 7, 2023
Merged

Upgrade @babel/traverse #409

merged 3 commits into from
Dec 7, 2023

Conversation

nmanu1
Copy link
Contributor

@nmanu1 nmanu1 commented Dec 6, 2023

Upgrade @babel/traverse from v7.23.0 (in top-level package-lock) and v7.20.1 (in the test site's package-lock) to 7.23.5 to address a critical vulnerability in the package.

Also, add some changes from running ESLint locally, since the linting PR check doesn't currently work.

J=VULN-38476, VULN-38477
TEST=auto

@coveralls
Copy link

coveralls commented Dec 6, 2023

Coverage Status

coverage: 85.159% (+0.004%) from 85.155%
when pulling 5ca94b1 on dev/upgrade-babel-traverse
into f8fd9fe on develop.

Copy link
Contributor

github-actions bot commented Dec 6, 2023

Current unit coverage is 92.18045112781955%
Current visual coverage is 78.34757834757835%
Current combined coverage is 92.68537074148297%

@nmanu1 nmanu1 marked this pull request as ready for review December 6, 2023 22:48
@nmanu1 nmanu1 requested a review from a team as a code owner December 6, 2023 22:48
Copy link
Member

@benmcginnis benmcginnis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@nmanu1 nmanu1 merged commit 5d0160c into develop Dec 7, 2023
16 of 18 checks passed
@nmanu1 nmanu1 deleted the dev/upgrade-babel-traverse branch December 7, 2023 22:11
@nmanu1 nmanu1 mentioned this pull request Dec 8, 2023
nmanu1 added a commit that referenced this pull request Dec 8, 2023
### Changes
- Added compatibility with PagesJS v1 (#400, #402, #404)
### Fixes
- Upgraded `@babel/traverse` version to address a vulnerability in the package (#409)
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.

3 participants