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

search-core: Resolve Vulnerabilities #287

Merged
merged 3 commits into from
Dec 9, 2024
Merged

search-core: Resolve Vulnerabilities #287

merged 3 commits into from
Dec 9, 2024

Conversation

mkouzel-yext
Copy link
Contributor

Regenerated package-lock.json and test-site/package-lock.json to ensure that both used updated safe dependencies.

J=VULN-39421
TEST=manual

Inspected babel dependencies in each file to confirm they used safe versions.

Regenerated package-lock.json and test-site/package-lock.json to ensure that both used updated safe dependencies.

J=VULN-39421
TEST=manual

Inspected babel dependencies in each file to confirm they used safe versions.
@mkouzel-yext mkouzel-yext requested a review from a team as a code owner November 22, 2024 21:46
@coveralls
Copy link

Pull Request Test Coverage Report for Build 11980635027

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.252%

Totals Coverage Status
Change from base Build 11940405180: 0.0%
Covered Lines: 216
Relevant Lines: 236

💛 - Coveralls

@Fondryext
Copy link
Contributor

A bit vague of an ask but could we try and see why all the .md files got reformatted? I wouldn't expect anything in this to have done it since we just updated package-lock. If it's from an earlier package change and only just got triggered, that's fine. Don't spend much time on this, just a quick glance at previous package changes to see if any seem related

@mkouzel-yext
Copy link
Contributor Author

I don't see anything obvious that caused the docs to get reformatted. I checked my local commit, and I did not include anything in the docs directory locally so it was done automatically.

Copy link
Contributor

@Fondryext Fondryext left a comment

Choose a reason for hiding this comment

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

no worries, then. Here's hoping they stay formatted for a while lol I feel like it happens every couple package upgrades

@mkouzel-yext mkouzel-yext merged commit d56085d into master Dec 9, 2024
14 checks passed
Fondryext pushed a commit that referenced this pull request Dec 9, 2024
search-core: Resolve Vulnerabilities

Regenerated package-lock.json and test-site/package-lock.json to ensure that both used updated safe dependencies.

J=VULN-39421
TEST=manual

Inspected babel dependencies in each file to confirm they used safe versions.

* Automated update to THIRD-PARTY-NOTICES from github action's 3rd party notices check

* Automated update to repo's documentation from github action

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
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