Skip to content

Record the upstream contributions of 27 and 28 September, and bring the dependencies up to date - #1058

Merged
jmrplens merged 12 commits into
mainfrom
docs/upstream-bugs-2026-09-28
Sep 28, 2026
Merged

jmrplens merged 12 commits into
mainfrom
docs/upstream-bugs-2026-09-28

Conversation

@jmrplens

@jmrplens jmrplens commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

I re-read every tracker docs/development/upstream-bugs.md links, the latest release of each dependency, and everything my GitLab and GitHub accounts touched outside this repository on 27 and 28 September, and brought the register up to date with it. Nothing done upstream in those two days is missing from it now.

New entries

Rows that moved

  • Row 17 (Codex): rmcp 3.5.0 was released on the 28th and carries the fix, and the comment owed on the Codex issue was posted. Codex's main still pins rmcp 3.2.0, so the workaround stays. The section also records the openai-mcp measurement from Capture the clientInfo a ChatGPT connector session reports, and decide whether the Codex profile should match it #1044.
  • Row 72: after the maintainer's review, the saved view fix clears the dirty state (clear_attribute_changes) instead of restoring it. The section now describes the fix as it stands in review.
  • Rows 11, 34, 39, 46, 53 and 68: each records its latest step.
    • Row 11's pull request now also carries the two sites it had left out, plus the promised comment rewrite.
    • Row 68's pull request took our review change as a commit.
    • Row 53 had its first backend review and our first round of changes.
    • Row 46 is approved and waits on routes master does not have yet.
  • The client-go umbrella and the go-sdk index: both were rewritten on the evening of the 27th. The paragraphs that said they had fallen behind now say that.

Two of those rows were waiting on me, and both were answered the same evening:

  • gitlab-org/api/client-go!3048: the maintainer review left one suggestion, and "otherwise LGTM". The suggestion is applied, and a second commit updates the test it broke.
  • gitlab-org/gitlab!254699: the new pipeline failed the same way as on the 22nd. It ran on the branch head, whose base predates the upstream fix, not on the merged result. My reply in the thread explains this and offers either a merged-result pipeline or a rebase. The second commit of this PR corrects row 39, which I had first written as a different clash coming from master.

The audit declaration

The new entries quote Orbit's schema file, graph_query.schema.json. audit_doc_tool_names reads graph_query.schema in that name as an action ID, because schema is also an Orbit action. So I declared it beside mcp.schema, which is the same case for the Agent Plugins schema.

Numbering: the second-wave lanes add rows of their own, and two of them already collide on 73. They take the numbers after 76 when they are integrated.

Dependency updates

This PR also carries the week's dependency updates, so they land in one merge.

From Dependabot's three pull requests. Each is taken as Dependabot resolved it, one commit per PR:

Pins Dependabot does not manage. All of these are past the seven-day cooldown dependabot.yml sets:

  • golangci-lint v2.13.1 to v2.13.2.
    • make install-tools installed golangci-lint@latest, which today is a release CI does not run. It now installs the pinned version.
    • It also installed govulncheck and gotestsum at @latest, although go.mod pins both as tools. It now installs the versions go.mod names.
  • Builder image: the golang:1.27.1-alpine3.24 digest, rebuilt upstream on 21 September on the same Go release.
  • Release workflow tools:
    • GoReleaser v2.18.0 to v2.18.2.
    • syft v1.51.1 to v1.52.0. Its tarball SHA256 changes in both jobs, and the workflow still checks it against the cosign-signed checksum file.
    • npm 11.5.1 to 11.19.1.
  • .NET SDK 10.0.400 to 10.0.401.
    • It moves in the release job and in the image make validate-nuget pins, now spelled sdk:10.0.401@sha256:….
    • I checked the three dnx behaviours the docs rely on against that image, using the package published on nuget.org. Without a terminal it installs without asking. It accepts --yes. Without --, it reads --version as its own option.
    • The pages that named 10.0.400 as the verified SDK now name both.
  • Site toolchain: Node 24.18.0 to 24.21.0 and pnpm 12.4.1 to 12.4.2.
    • CONTRIBUTING.md and the development guide named pnpm 11.x, and CONTRIBUTING.md still asked for Node 22. Both now match the pin.
  • OpenTelemetry collector image the telemetry e2e runs: 0.159.0 to 0.161.0. Neither release changes the OTLP receiver or the file and debug exporters the test uses.

Held back, and why.

  • Still inside the cooldown:
    • gqlparser v2.5.58, released 23 September; its only functional change is a stricter overlapping-fields comparison.
    • golangci-lint v2.14.0.
    • npm 11.20.0.
    • pnpm 12.5.
  • New majors, each a change of its own:
    • Node 24 in the release job;
    • npm 12;
    • Bitbucket 10 in the e2e fixture;
    • a newer haproxy branch in the balancer test.

The other Go modules have no update, or are indirect and follow their parents. Go 1.27.1 is still the newest Go release.

Checks

  • go run ./cmd/audit_doc_tool_names/ --check passes, and so does go test ./cmd/audit_doc_tool_names/.
  • go run ./cmd/format_md_tables/ --check passes.
  • markdownlint-cli2 and make check-em-dash pass.
  • make gen-stats accounts for the one line the declaration adds.
  • A rehearsal of the release workflow on this branch (run 36461778198) succeeded. It covers what CI does not run:
    • the image build on both Docker pins;
    • GoReleaser with syft's SBOMs;
    • npm's dry publish on 11.19.1;
    • the NuGet validation on 10.0.401;
    • the race gate, which runs the collector module on 0.161.0.
  • CI's Windows job first failed on the listing-limit test feat(tenancy): bound tools/list across the process (RTC-007) #1046 added, which judges a later budget than the one that stopped it (The rate-limit-off arm of TestLimit_ProcessBoundsListingAcrossCredentials judges a later budget than the one that stopped it #1060, unrelated to these updates), and passed on the rerun.
  • The site lockfile needed pnpm 12.4.2 recorded in it, since pnpm 12 writes its own version there and a frozen install refuses a mismatch.

Add rows 73 to 76, the contributions made upstream on 2026-09-28: the
gobco build-constraint fix (rillig/gobco#40 and #41), the Orbit API
query examples rewritten for version 12 of the DSL (gitlab-org/gitlab
!258241), and the two Orbit schema defects, each an issue and a merge
request that closes it (knowledge-graph #1329 with !2650, #1330 with
!2651).

Re-verify every tracker the file links and every change the maintainer's
accounts made on the 27th and 28th, and bring the rows that moved up to
date: rmcp 3.5.0 carries the Codex fix (row 17), the saved view fix now
clears the dirty state instead of restoring it (row 72), and rows 11, 34,
39, 46, 53 and 68 each record their latest step, two of them one that now
waits on us. The client-go umbrella and the go-sdk index were rewritten
on the 27th, so the paragraphs saying they had fallen behind now say so.

Declare graph_query.schema in the documentation tool-name audit: it is
the middle of Orbit's schema file name, graph_query.schema.json, which
the new entries quote, as mcp.schema already is for the Agent Plugins
schema.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @jmrplens, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 5 hours and 55 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

@coderabbitai

coderabbitai Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: jmrplens/gitlab-mcp-server/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 532bed2c-5f31-4af1-8a91-34a337db1768

📥 Commits

Reviewing files that changed from the base of the PR and between 0bf10e9 and 53f4c7a.

📒 Files selected for processing (3)
  • README.md
  • cmd/audit_doc_tool_names/ids.go
  • docs/development/upstream-bugs.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Summary

Summary by CodeRabbit

  • Documentation
    • Updated the upstream issue register with current tracker and release information, including newly documented issues and progress on existing contributions.
    • Corrected the README’s source-line and total-line counts.

Walkthrough

The pull request updates the upstream-bug register with new issue records and revised status details. It also adjusts the documentation-name audit allowlist and updates the README line-count totals.

Changes

Upstream issue register refresh

Layer / File(s) Summary
Register summary and verification snapshot
README.md, docs/development/upstream-bugs.md
The README line totals change. The register summary and verification log record new issue categories, tracker checks, release details, and status updates.
Client and Go SDK status records
docs/development/upstream-bugs.md
Client-go and Go SDK entries record review progress, pull request status, protocol-version details, and an adopted review change.
Existing issue progress updates
docs/development/upstream-bugs.md
Existing entries update review and pipeline status, release compatibility observations, and the saved-view fix description.
New issue records and audit exception
docs/development/upstream-bugs.md, cmd/audit_doc_tool_names/ids.go
The register adds Orbit API, Orbit schema, and gobco entries. The audit allowlist accepts graph_query.schema as part of a filename.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 53f4c

This change updates documentation and its audit exception; no actionable merge-blocking regression is established, so it is mergeable subject to normal checks.

Architecture Summary

Architecture risk: 🔵 Low · up to 53f4c

The change affects 3 systems.

Changed systems: cmd, docs, README.md

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — cmd (service) was modified; 1 changed file maps to changed impact.
  • observed — docs (service) was modified; 1 changed file maps to changed impact.
  • observed — README.md (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in README.md: The file-count table increases the source line total from 316,127 to 316,128 and the overall line total from 1,050,552 to 1,050,553; category file counts and other line totals remain unchanged.
  • observed — Modified behavior in cmd/audit_doc_tool_names/ids.go: allowedIDs adds an exception for graph_query.schema, identified as a segment of the graph_query.schema.json file name.
  • observed — Modified behavior in docs/development/upstream-bugs.md: The summary table now records the Codex priority fix as merged in rmcp 3.5.0, while noting Codex still pins 3.2.0 and the workaround remains until fixed builds are widely deployed.
  • observed — Modified behavior in docs/development/upstream-bugs.md: Four entries were added to the summary table: gobco’s package-wide type checking, outdated Orbit API query examples, and two Orbit DSL schema defects.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly identifies the recorded upstream contributions and dependency updates, which are the main changes in the pull request.
Description check ✅ Passed The description provides a detailed summary, linked upstream issues, dependency changes, testing evidence, and rationale for held-back updates. It does not follow the template headings or checklist fo…
✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jmrplens jmrplens added documentation Improvements or additions to documentation v3.1.0 Targeted at the 3.1.0 release labels Sep 28, 2026
@jmrplens jmrplens added this to the 3.1.0 milestone Sep 28, 2026
@jmrplens jmrplens changed the title docs(upstream-bugs): record the contributions of 27 and 28 September Record the upstream contributions of 27 and 28 September, and re-verify the register Sep 28, 2026
@github-actions github-actions Bot added the tooling The audit and generator commands under cmd/, and the Makefile targets that run them label Sep 28, 2026
Row 39 said the pipeline of 2026-09-28 failed on a different clash from
master. It was the same clash as on 2026-09-22, for a different reason:
the pipeline ran on the branch head, whose base predates the fix, not on
the merged result. Record that and the reply that sets it out.

Row 34 now records the maintainer's suggestion as applied, with the test
update it needed, and the dated paragraph says both actions that waited
on us were taken.
sourcery-ai[bot]
sourcery-ai Bot previously approved these changes Sep 28, 2026

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sourcery assessment

Approved.

SonarSource/sonarqube-scan-action, docker/setup-qemu-action,
docker/setup-buildx-action and docker/build-push-action move to new
commits of the same major, and github/codeql-action init and analyze
from v4.38.0 to v4.38.1. Taken from Dependabot's pull request #1059.
The runtime stage of the image, pinned by tag and digest. Taken from
Dependabot's pull request #1056.
@astrojs/starlight 0.42.0 to 0.42.2, astro 7.3.2 to 7.3.3, the two
@typescript-eslint packages 8.70.0 to 8.70.1 and prettier 3.9.6 to
3.9.8, with the lockfile Dependabot resolved. Taken from Dependabot's
pull request #1057.
GOLANGCI_LINT_VERSION moves from v2.13.1 to v2.13.2, which CI reads from
the Makefile. v2.14.0 is left for when it clears the seven-day cooldown.

make install-tools installed golangci-lint@latest, which is v2.14.0
today, so a developer who followed it linted with a release CI does not
run. It now installs GOLANGCI_LINT_VERSION. govulncheck and gotestsum
were @latest as well, although go.mod pins both as tool directives; run
inside the module, `go install <pkg>` without a version builds the one
go.mod names, which is what CI runs. ensure-gotestsum does the same.
The tag was rebuilt on 2026-09-21 on the same Go release, which puts it
past the seven-day cooldown the other Docker pins follow. Dependabot
would have proposed this digest next week.
GoReleaser v2.18.0 to v2.18.2 and syft v1.51.1 to v1.52.0, with the
SHA256 of the syft linux/amd64 tarball updated in both jobs that install
it; the workflow still checks that tarball against syft's cosign-signed
checksum file before running it. The npm the publish step upgrades to
moves from 11.5.1 to 11.19.1, still above the 11.5.1 floor trusted
publishing needs. npm 11.20.0 and 12.x are left for later: the first is
inside the seven-day cooldown and the second is a major.
… 10.0.401

The release job's setup-dotnet version and the image `make
validate-nuget` pins move together, as their comment asks: 10.0.400 to
10.0.401, and the image is now spelled with its exact tag beside the
digest, sdk:10.0.401@sha256:35d40304..., so the two cannot disagree.

The three dnx facts the documentation relies on were checked against
that image, on the package published on nuget.org: with stdin not a
terminal and no --yes it installs without asking; it accepts --yes; and
without `--`, `--version` is read as dnx's own option. The pages that
named 10.0.400 as the verified SDK now name both.
site/.node-version, which every job that builds the site reads, moves
from 24.18.0 to 24.21.0, and the packageManager pin from pnpm 12.4.1 to
12.4.2, with the sha512 corepack checks. pnpm 12.5 is a minor still
inside the fourteen-day cooldown the npm ecosystem follows here.

The contributor pages named pnpm 11.8.0 and 11.25.0, two versions the
site had long left, and CONTRIBUTING.md still asked for Node 22. Both
now name the pin and the floor site/package.json's engines field states.
…to 0.161.0

otel/opentelemetry-collector-contrib 0.159.0 to 0.161.0, published on
2026-09-16. Neither 0.160.0 nor 0.161.0 lists a breaking change in the
OTLP receiver or the file and debug exporters, which are all the test's
pipeline uses. The module runs in race.yml, weekly and as a release gate.
@github-actions github-actions Bot added security Security-related issue ci Build pipeline, workflows, or lint configuration distribution Release artifacts, packaging, and install channels dependencies Pull requests that update a dependency file site The documentation site's build, components and scripts, not its content e2e The end-to-end suite and its Docker fixtures labels Sep 28, 2026
@sourcery-ai
sourcery-ai Bot dismissed their stale review September 28, 2026 17:57

Sourcery withdrew this approval because the latest commits introduced blocking findings.

@jmrplens jmrplens changed the title Record the upstream contributions of 27 and 28 September, and re-verify the register Record the upstream contributions of 27 and 28 September, and bring the dependencies up to date Sep 28, 2026
pnpm 12 writes its own version into pnpm-lock.yaml as a package manager
dependency, and `pnpm install --frozen-lockfile` refuses a lockfile
whose recorded pnpm differs from the packageManager field. Regenerated
with pnpm 12.4.2 in lockfile-only mode; only the pnpm entries change.
@sonarqubecloud

Copy link
Copy Markdown

@jmrplens
jmrplens merged commit 85e44fb into main Sep 28, 2026
6 checks passed
@jmrplens
jmrplens deleted the docs/upstream-bugs-2026-09-28 branch September 28, 2026 18:53
jmrplens added a commit that referenced this pull request Sep 30, 2026
…ve advisories published on 29 September (#1085)

I went through every dependency this repository pins, against the latest release of each upstream, and updated everything the cooldown in `dependabot.yml` admits: seven days for a patch, fourteen for a minor, counted from the release. I applied the same rule to the pins Dependabot does not manage. There were no open Dependabot pull requests, so every change here is by hand.

## Security fixes in the site's dependency tree

- **brace-expansion** (first commit): GHSA-6j4f-fj2g-mc7p and GHSA-qhr7-859c-m2p7, both high, reach the 1.1.18 and 5.0.9 the overrides pinned, through pa11y-ci, htmlhint and eslint, and they failed the site dependency audit on every pull request. Both pins move to the last release of their line, 1.1.21 and 5.0.12, published on 2026-09-14. Those two releases are also the first to fix GHSA-q2hr-2g5m-vwhr (moderate), published on 29 September with the other two, which is why the pins are 1.1.21 and 5.0.12 rather than 1.1.20 and 5.0.11; the comment beside them in `site/pnpm-workspace.yaml` now records all three.
- **ip-address** 10.5.1 to 10.7.2: GHSA-j6r3-76f7-8jcv (isInSubnet compares addresses of different families as one address space) and GHSA-h3mg-xc3c-68pw (an Address6 parse diagnostic with no length bound), both moderate and published on 29 September, reach the 10.5.1 the override pinned, through pa11y-ci, puppeteer, @puppeteer/browsers, proxy-agent and socks-proxy-agent to socks. Both are fixed in 10.7.1. 10.7.2 is the last 10.x release and stays inside the ^10.1.1 socks asks for.

With both, `pnpm audit --audit-level=high` reports nothing but the two recorded extract-zip exceptions.

## What moved

Go modules, all indirect:

- github.com/ebitengine/purego v0.11.0 to v0.11.1
- github.com/power-devops/perfstat to its 2026-09-16 commit
- golang.org/x/telemetry to its 2026-09-22 commit, the newest one at least seven days old
- google.golang.org/genproto/googleapis/api and /rpc to their 2026-09-21 commit, the newest one at least seven days old

The site:

- @astrojs/starlight 0.42.2 to 0.42.3
- astro 7.3.3 to 7.3.4, which itself moves obug to 3.0.0, tinyclip to 1.0.3 and its own @astrojs/markdown-satteri to 0.4.2 (Starlight keeps 0.4.1)
- prettier 3.9.8 to 3.9.9
- html-validate 11.15.0 to 11.16.0
- The esbuild override 0.28.1 to 0.28.2, the last 0.28.x release, with the reason it is still needed now written beside it: GHSA-g7r4-m6w7-qqqr reaches 0.27.3 to 0.28.0, and astro's ^0.28.0 admits 0.28.0. The high advisory published beside it, GHSA-gv7w-rqvm-qjhr, was withdrawn on 2026-06-17.

I resolved the site lockfile with a seven-day minimum release age, so no transitive package younger than the cooldown came in with these.

## Overrides no longer needed

I checked each override in `site/pnpm-workspace.yaml` against the range its consumers ask for. Two are no longer needed:

- **lodash**: its one consumer, pa11y-ci, asks for ~4.18.1, which is past both advisories, so the tree holds the same 4.18.1 without the override.
- **yaml** and **yaml-language-server@1.20.0>yaml**: the scoped entry named a release the tree no longer holds (it has 1.23.0), and every consumer now asks for a release past GHSA-48c2-rrv3-qjmp. Without the global pin, yaml-language-server gets the 2.8.3 it pins exactly, the first patched release, and the rest stay on 2.9.0.

lodash-es stays, because chevrotain 11.1.2 still asks for exactly 4.17.23, and I wrote that beside it. The others were already at the last patched release of their line: fast-uri 3.1.8, js-yaml 4.3.2 and undici 6.28.1 and 8.10.2, whose next releases (6.29.0, 8.11.x) are minors inside the cooldown.

## Already current

Go 1.27.1 is still the newest Go release, go-sdk v1.8.0 and every other direct Go requirement are at their newest version, and Node 24.21.0 is the newest Node 24. Every GitHub Actions pin but one is on the newest release of its action. GoReleaser v2.18.2, syft v1.52.0, oras 1.3.4, cosign v3.1.3, the .NET SDK 10.0.401 (the image digest `make validate-nuget` pins is unchanged), mcp-publisher v1.8.1, the mcpb CLI 2.1.2, the LobeHub CLI 0.0.41, gremlins v0.6.0, gobco v1.3.4, twine 7.0.0 and release-cli v0.24.0 are all the newest releases. The builder, runtime and Dockerfile frontend digests in the `Dockerfile` are the ones their tags pointed to on 2026-09-30.

## Held, and why

Inside the cooldown, with the date each becomes eligible:

- github.com/vektah/gqlparser/v2 v2.5.58, a patch released 2026-09-23 at 18:03 UTC, eligible 2026-09-30 at 18:03 UTC. Its one functional change compares composite argument values when judging overlapping fields. I tried it anyway: with it, the full unit suite and `make check-graphql-documents` pass, so it can go in as soon as it clears.
- gitlab.com/gitlab-org/api/client-go/v3 v3.15.0, a minor released 2026-09-28, eligible 2026-10-12.
- google.golang.org/grpc v1.84.0 (minor, eligible 2026-10-01) and github.com/grpc-ecosystem/grpc-gateway/v2 v2.31.0 (minor, eligible 2026-10-09), both indirect.
- The genproto commit of 2026-09-28 and the x/telemetry commits of 2026-09-23 and 2026-09-24.
- github/codeql-action v4.38.2, released 2026-09-24, eligible 2026-10-01.
- golangci-lint v2.14.0, a minor released 2026-09-24, eligible 2026-10-08.
- The OpenTelemetry collector image 0.162.0, released 2026-09-29 and not yet on Docker Hub on the morning of 2026-09-30, eligible 2026-10-13, since 0.161 to 0.162 is a minor.
- npm 11.20.0 in the release job, a minor released 2026-09-22, eligible 2026-10-06.
- pnpm: every minor after 12.4 is younger than fourteen days. 12.5.1 is eligible 2026-10-02 and 12.8.1 on 2026-10-12.
- The site: astro 7.3.5 and Starlight 0.42.4 (2026-10-01), eslint-plugin-astro 3.2.0 and 3.2.1 (2026-09-30 and 2026-10-01), eslint 10.11.0 (2026-10-02), sharp 0.35.5 and html-validate 11.16.1 (2026-10-04), typescript-eslint 8.71.0 (2026-10-12).

Majors, each a change of its own, as in #1058: npm 12 in the release job, whose trusted publishing exchange only a real publish exercises; Node 24 in the release job; Bitbucket 10 in the e2e fixture; the HAProxy 3.4 LTS branch in the balancer test; and TypeScript 7, which `astro check` refuses for the reason `pnpm-workspace.yaml` records. The server's major tracks client-go's, so a client-go v4 would be held regardless.

## Checks

- `go build ./...`, `go vet ./...` and `go vet -tags e2e ./test/e2e/...` pass.
- The full unit suite, `go test ./cmd/... ./internal/... -count=1 -shuffle=on`, passes: 276 packages.
- `make golangci-lint` at v2.13.2 passes.
- The e2e suites compile: `./test/e2e/gitlab/...` and the harness under `e2e`, and the `httpe2e`, `stdioe2e` and `collectore2e` modules.
- `make test-e2e-http` passes, 566 tests with 7 skipped: the nginx and HAProxy layers need Docker, which the machine that ran it lacks, and CI runs them. `make test-e2e-stdio` passes, 90 tests.
- `govulncheck` reports no vulnerability our code reaches. The one module-level entry is GO-2026-5932 in golang.org/x/crypto, which has no fix and is documented in `scripts/govulncheck.sh`.
- `make check-supply-chain`, `make check-server-json` and `go run ./cmd/gen_testing_docs/ --check` pass.
- `make gen-stats` changes nothing, and `make check-stats` and `make check-em-dash` pass.
- The site: `pnpm install --frozen-lockfile`, `pnpm audit --audit-level=high` (only the two extract-zip exceptions), `pnpm run build` (105 pages, internal links valid, Mermaid rendered through Playwright's Chromium) and `pnpm run lint` all pass.
- The release rehearsal on this branch, [run 36688038543](https://github.com/jmrplens/gitlab-mcp-server/actions/runs/36688038543) (`gh workflow run release.yml --ref deps-2026-09-30 -f tag=v3.1.0`), passed. It covers what CI does not: the E2E gate against an ephemeral GitLab, the image build, GoReleaser with syft's SBOMs, npm's dry publish, the NuGet validation and the race gate with the collector module.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Build pipeline, workflows, or lint configuration dependencies Pull requests that update a dependency file distribution Release artifacts, packaging, and install channels documentation Improvements or additions to documentation e2e The end-to-end suite and its Docker fixtures security Security-related issue site The documentation site's build, components and scripts, not its content tooling The audit and generator commands under cmd/, and the Makefile targets that run them v3.1.0 Targeted at the 3.1.0 release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant