chore(deps): upgrade go.lsp.dev dependencies to v1
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- build-system
Research direction
Start with go.mod and identify the go.lsp.dev modules listed in the issue, including protocol, uri, and jsonrpc2. Check their v1 releases and update the dependency versions, then run the relevant Go module and test checks. Done means the listed dependencies use v1 versions and the project builds and tests successfully.
Written by the indexing model from the issue text.
Description
Currently, buf depends on pre-v1 releases of go.lsp.dev/* modules in go.mod (such as go.lsp.dev/protocol, go.lsp.dev/uri, and go.lsp.dev/jsonrpc2).
Since go.lsp.dev has stable v1 releases available, please upgrade these dependencies to their v1 versions to incorporate upstream improvements, bug fixes, and ensure consistency across Go module imports.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 372
- Avg merge
- 18h 42m
- Merged PRs (30d)
- 31
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bufbuild/buf
-
Feature
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
Feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
bufbuild/buf#4722 · 2 comments ·
Maintainers usually reply within 1 day
-
Add a merge-base option to the buf-breaking checkMay be free again A pull request for this issue was closed without being merged. OpenFeature
Difficulty 3/5 1-2 days Newbie friendliness 58/100
bufbuild/buf#4495 · 4 comments ·
Maintainers usually reply within 1 day
-
Feature
Difficulty 3/5 1-2 days Newbie friendliness 38/100
bufbuild/buf#4425 · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
GitHub webhook is not subscribed to release events, so `event: release` never triggersPossibly taken @qsun claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
woodpecker-ci/woodpecker#7542 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zilliztech/milvus-backup#1386 ·
Maintainers usually reply within 1 day
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil varsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oracle/go-oracledb#168 ·
Maintainers usually reply within 2 days