Repository navigation
Record the go-sdk read and the knowledge-graph skip markers - #1080
Merged
Merged
Conversation
Every go-sdk issue and pull request the register links was read again. go-sdk has cut no release since v1.8.0, so every merge recorded here is still unreleased, and the maintainer's own estimate of the next release, about two months after v1.8.0, is cited. Row 11: a maintainer updated our pull request from main on 2026-09-29 and every check passed; main gained two commits after it, and I updated it again the same day, keeping the maintainer's merge commit, with every check passing. It has had no review since 2026-09-15. Rows 8 and 12: I updated both pull requests from main the same day and their checks passed; row 8's has had no review and row 12's one review thread still waits on the reviewer. Row 68: the issue was triaged P2, the pull request another contributor opened now conflicts with main and its checks have never run, and the dates of our comment, review and the author's follow-up are corrected to UTC. Row 48: the case is named as a known limitation of a pull request another contributor opened, merged on 2026-09-18, which the summary row and the entry now record, with the maintainer's position on that pull request. Its discussion also showed the entry's transport claim too wide: v1.8.0's stateful HTTP handler refuses every 2026-07-28 request but server/discover, so only stdio reaches the case, and the entry now says so. Rows 75 and 76: both knowledge-graph merge requests now carry the [skip pinned-version-check] marker in their descriptions, which the check asks for when a change does not affect the shape, so the merged-results pipeline will not refuse them for want of a query_dsl bump. Each also offers the bump instead: row 75's a patch bump, so clients that cache the schema by version fetch the new text, and row 76's should the maintainers read its changed declared default as part of the contract.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
Warning Review limit reachedNext included review available in 17 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository: jmrplens/gitlab-mcp-server/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
the
documentation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I read every go-sdk issue and pull request
docs/development/upstream-bugs.mdlinks, and this records what moved. Nothing there asks anything of us, and go-sdk has cut no release since v1.8.0, so every merge recorded is still unreleased; the maintainer's estimate of the next one, about two months after v1.8.0, is now cited.mainon 2026-09-29 and all nine checks passed;maingained two commits after it, and I updated it again the same day with GitHub's Update branch, which kept the maintainer's merge commit, and the checks passed again. It has had no review since 2026-09-15.main; I updated them frommainon 2026-09-29 and their checks passed. modelcontextprotocol/go-sdk#1293 has had no review, and the one review thread on modelcontextprotocol/go-sdk#1267 still waits on the reviewer.mainand its checks have never run. The dates of my comment and review, and of the author's follow-up, are corrected to UTC.server/discover, so only stdio reaches the case.knowledge-graph
[skip pinned-version-check], which the project's check asks for when a change does not affect the shape, so the merged-results pipeline a maintainer runs will not refuse either for want of aquery_dslbump. The marker sits at the top of each description's collapsed details block, where the project's description lint does not count it and the 2700 characters a pipeline reads still hold it. Each merge request also offers the bump instead: row 75's a patch bump, so clients that cache the schema by version fetch the new text, and row 76's should the maintainers read the declared default that branch changes as part of the contract. Both Files lists now name the test pins.Checks
npx markdownlint-cli2 docs/development/upstream-bugs.mdpasses.go run ./cmd/format_md_tables/ --checkpasses.