Skip to content

chore(deps): update dependency tree-sitter to v0.22.4 #188

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tree-sitter 0.21.1 -> 0.22.4 age adoption passing confidence

Release Notes

tree-sitter/node-tree-sitter (tree-sitter)

v0.22.4

Compare Source

Full Changelog: tree-sitter/node-tree-sitter@v0.22.3...v0.22.4

v0.22.3

Compare Source

v0.22.2

Compare Source

v0.22.1

Compare Source

v0.22.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Mar 11, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch 9 times, most recently from f43b76f to d533711 Compare March 18, 2024 18:05
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch 11 times, most recently from d033783 to 2267029 Compare March 25, 2024 19:36
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch 8 times, most recently from 0e2a4ba to 980c181 Compare March 29, 2024 00:07
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter to v0.21.0 chore(deps): update dependency tree-sitter to v0.21.1 Mar 29, 2024
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch 3 times, most recently from b3235c5 to ea9739c Compare July 20, 2024 15:20
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch from ea9739c to 038ae54 Compare October 26, 2024 07:37
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter to v0.21.1 chore(deps): update dependency tree-sitter to v0.22.0 Oct 26, 2024
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch from 038ae54 to c947991 Compare November 10, 2024 04:50
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter to v0.22.0 chore(deps): update dependency tree-sitter to v0.22.1 Nov 10, 2024
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch 12 times, most recently from d2995cc to 33ce938 Compare December 30, 2024 01:54
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter to v0.22.1 chore(deps): update dependency tree-sitter to v0.22.3 Dec 30, 2024
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch from 33ce938 to 6cc45ca Compare December 30, 2024 03:31
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter to v0.22.3 chore(deps): update dependency tree-sitter to v0.22.4 Dec 30, 2024
@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch from 6cc45ca to 09ede9f Compare March 4, 2025 19:15
Copy link
Contributor Author

renovate bot commented Mar 4, 2025

⚠️ 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/tree-sitter
npm error   optional tree-sitter@"0.22.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional tree-sitter@"^0.21.1" from [email protected]
npm error node_modules/tree-sitter-c-sharp
npm error   optional tree-sitter-c-sharp@"0.23.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/tree-sitter
npm error   peerOptional tree-sitter@"^0.21.1" from [email protected]
npm error   node_modules/tree-sitter-c-sharp
npm error     optional tree-sitter-c-sharp@"0.23.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-03-04T19_20_01_384Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-04T19_20_01_384Z-debug-0.log

@renovate renovate bot force-pushed the renovate/tree-sitter-0.x branch from 09ede9f to f59e900 Compare March 4, 2025 19:20
@luke-hill luke-hill closed this Mar 4, 2025
@luke-hill luke-hill deleted the renovate/tree-sitter-0.x branch March 4, 2025 19:20
Copy link
Contributor Author

renovate bot commented Mar 4, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (0.22.4). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants