Skip to content

Comments

fix(deps): update dependency unist-util-visit to v5#134

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/unist-util-visit-5.x
Closed

fix(deps): update dependency unist-util-visit to v5#134
renovate[bot] wants to merge 1 commit intomainfrom
renovate/unist-util-visit-5.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 29, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change OpenSSF
unist-util-visit dependencies major ^2.0.3 -> ^5.0.0 OpenSSF Scorecard

Release Notes

syntax-tree/unist-util-visit (unist-util-visit)

v5.0.0

Compare Source

Change
  • 4dcff31 Update @types/unist
    migrate: update too
  • befc0b3 Change to require Node.js 16
    migrate: update too
  • b5f36de Change to use export map
    migrate: don’t use private APIs
  • 89fc050 Change to remove complex-types.d.ts
    migrate: use main export
  • 12c9ee9 Change to pass undefined, not null
    migrate: change null to undefined
Fix
  • 3cb2732 Fix performance of InclusiveDescendant type

Full Changelog: syntax-tree/unist-util-visit@4.1.2...5.0.0

v4.1.2

Compare Source

Misc

Full Changelog: syntax-tree/unist-util-visit@4.1.1...4.1.2

v4.1.1

Compare Source

Full Changelog: syntax-tree/unist-util-visit@4.1.0...4.1.1

v4.1.0

Compare Source

Full Changelog: syntax-tree/unist-util-visit@4.0.0...4.1.0

v4.0.0

Compare Source

  • 050fdc3 Change types to base what visitor gets on tree
    (breaking if you use TypeScript, read commit for info)

v3.1.0

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

  • ed0bccd Add JSDoc based types
  • dfbcafb Use ESM
    note: change from const visit = require('unist-util-visit') to import {visit} from 'unist-util-visit'

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented Mar 29, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 14 projects
Progress: resolved 1, reused 0, downloaded 0, added 0
undefined
/tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace/node1:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/anotherExternal: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace/node1

anotherExternal is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

@renovate renovate bot force-pushed the renovate/unist-util-visit-5.x branch 3 times, most recently from 52899d8 to 008761c Compare March 29, 2024 15:47
@renovate renovate bot force-pushed the renovate/unist-util-visit-5.x branch from 008761c to 890a00e Compare March 29, 2024 15:55
@dgellow dgellow closed this Mar 29, 2024
@renovate
Copy link
Author

renovate bot commented Mar 29, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

1 participant