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

chore(deps): update dependency tree-sitter-ruby to v0.23.1 #183

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tree-sitter-ruby 0.19.0 -> 0.23.1 age adoption passing confidence

Release Notes

tree-sitter/tree-sitter-ruby (tree-sitter-ruby)

v0.23.1

Compare Source

NOTE: Download tree-sitter-ruby.tar.xz for the complete source code.

v0.23.0

Compare Source

v0.21.0

Compare Source

v0.20.1

Compare Source

What's Changed

New Contributors

Full Changelog: tree-sitter/tree-sitter-ruby@v0.19.0...v0.20.1


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 Feb 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-ruby-0.x branch 7 times, most recently from 7ed7a4e to 9338249 Compare February 19, 2024 21:18
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch 6 times, most recently from 5549e30 to 671cccb Compare February 27, 2024 00:03
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch 8 times, most recently from b261bda to 2fe46f1 Compare March 5, 2024 12:10
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch 7 times, most recently from e5953c8 to 570275b Compare March 13, 2024 19:31
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch from 570275b to 9363367 Compare March 14, 2024 19:36
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch from d4826b1 to c94096f Compare April 20, 2024 20:29
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch from c94096f to 81fc42c Compare May 6, 2024 00:43
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter-ruby to v0.20.1 chore(deps): update dependency tree-sitter-ruby to v0.21.0 May 6, 2024
Copy link
Contributor Author

renovate bot commented May 6, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @cucumber/[email protected]
npm error Found: [email protected]
npm error node_modules/tree-sitter
npm error   optional tree-sitter@"0.20.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peer tree-sitter@"^0.21.0" from [email protected]
npm error node_modules/tree-sitter-ruby
npm error   optional tree-sitter-ruby@"0.21.0" 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 /tmp/renovate/cache/others/npm/_logs/2024-05-06T00_43_15_155Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T00_43_15_155Z-debug-0.log

@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch from 81fc42c to 59531cd Compare May 9, 2024 09:44
Copy link
Contributor Author

renovate bot commented May 9, 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: 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.20.6" from the root project
npm error   tree-sitter@"^0.20.6" from [email protected]
npm error   node_modules/tree-sitter-typescript
npm error     optional tree-sitter-typescript@"0.20.5" 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-ruby
npm error   optional tree-sitter-ruby@"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-ruby
npm error     optional tree-sitter-ruby@"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 /tmp/renovate/cache/others/npm/_logs/2024-11-11T07_10_16_225Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-11T07_10_16_225Z-debug-0.log

@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch 8 times, most recently from 0e9a784 to 5769990 Compare May 12, 2024 20:21
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch 2 times, most recently from d5a5212 to 1db5435 Compare May 19, 2024 22:09
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch 3 times, most recently from c42d8f3 to c2dec5f Compare June 6, 2024 20:54
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch from c2dec5f to 12cc765 Compare July 4, 2024 22:07
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch 5 times, most recently from 17cad12 to e2ecb16 Compare July 20, 2024 15:21
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch from e2ecb16 to 033ad4a Compare September 2, 2024 07:57
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter-ruby to v0.21.0 chore(deps): update dependency tree-sitter-ruby to v0.23.0 Sep 2, 2024
@renovate renovate bot force-pushed the renovate/tree-sitter-ruby-0.x branch from 033ad4a to be46f00 Compare November 11, 2024 07:10
@renovate renovate bot changed the title chore(deps): update dependency tree-sitter-ruby to v0.23.0 chore(deps): update dependency tree-sitter-ruby to v0.23.1 Nov 11, 2024
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.

1 participant