sanity-io / contentful-to-sanity

Migrate from Contentful to Sanity
MIT License
34 stars 7 forks source link

chore(deps): update dependency ls-engines to ^0.9.1 #161

Closed renovate[bot] closed 5 months ago

renovate[bot] commented 5 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ls-engines ^0.9.0 -> ^0.9.1 age adoption passing confidence

Release Notes

ljharb/ls-engines (ls-engines) ### [`v0.9.1`](https://togithub.com/ljharb/ls-engines/blob/HEAD/CHANGELOG.md#v091---2023-11-15) [Compare Source](https://togithub.com/ljharb/ls-engines/compare/v0.9.0...v0.9.1) ##### Commits - \[Refactor] extract `getGraphEntries` [`a2d6348`](https://togithub.com/ljharb/ls-engines/commit/a2d6348990070675021010dda09a458dfc679fc0) - \[Refactor] `getGraphEntries`: sort output by package name and node version, for determinism [`74690d8`](https://togithub.com/ljharb/ls-engines/commit/74690d8d2916f4109cfb29095b8a21e72001f986) - \[Refactor] extract `getGraphValids`, `validVersionsForEngines` [`f6d807e`](https://togithub.com/ljharb/ls-engines/commit/f6d807e1e1460548873586e9fa18caa27a53002a) - \[Refactor] extract `getAllVersions` [`0d0d327`](https://togithub.com/ljharb/ls-engines/commit/0d0d3277201ce64a3a1277b6a07249b9f82ee78c) - \[Refactor] some code cleanup [`ac05eaf`](https://togithub.com/ljharb/ls-engines/commit/ac05eafa9d19a9a2dff9a83d9e940a1e33b48741) - \[Robustness] `getGraphEntries`: avoid builtin prototype methods [`24f4201`](https://togithub.com/ljharb/ls-engines/commit/24f42017655811f9096294f826f795cd00e2ff21) - \[Refactor] use arborist querySelectorAll instead of filtering inventory [`dc77370`](https://togithub.com/ljharb/ls-engines/commit/dc77370b2e7875a3457db4eb58b32fced226e5bc) - \[Tests] update fixtures; `depd` was removed in [https://github.com/node-modules/agentkeepalive/pull/114](https://togithub.com/node-modules/agentkeepalive/pull/114) [`e5c1783`](https://togithub.com/ljharb/ls-engines/commit/e5c1783fcf81b1a7f5c4a1668403490239f89542) - \[Deps] update `@npmcli/arborist`, `object.fromentries`, `object.values`, `pacote`, `promise.allsettled`, `semver`, `yargs` [`baf84ac`](https://togithub.com/ljharb/ls-engines/commit/baf84ac31371e6043f01f338f80feaf83f0ed5b4) - \[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape` [`71295f2`](https://togithub.com/ljharb/ls-engines/commit/71295f25192eb03571754ab27fba31df5938566f) - \[Refactor] remove unneccesary promise creation when the graph is empty [`dbc0dde`](https://togithub.com/ljharb/ls-engines/commit/dbc0dde2d6922704c606d2374fc471dead161903)

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

socket-security[bot] commented 5 months ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSource
Potential typo squat npm/array.prototype.some@1.1.6
  • orphan: npm/array.prototype.some@1.1.6

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/array.prototype.some@1.1.6