Skip to content

chore(deps): bump alpine from 3.24.1 to 3.24.2 - #1056

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/alpine-3.24.2
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/alpine-3.24.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 28, 2026

Copy link
Copy Markdown
Contributor

Bumps alpine from 3.24.1 to 3.24.2.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps alpine from 3.24.1 to 3.24.2.

---
updated-dependencies:
- dependency-name: alpine
  dependency-version: 3.24.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Dependabot: a container image update labels Sep 28, 2026
@dependabot
dependabot Bot requested a review from jmrplens as a code owner September 28, 2026 17:14
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Dependabot: a container image update labels Sep 28, 2026
@github-actions github-actions Bot added the distribution Release artifacts, packaging, and install channels label Sep 28, 2026
jmrplens added a commit that referenced this pull request Sep 28, 2026
The runtime stage of the image, pinned by tag and digest. Taken from
Dependabot's pull request #1056.
jmrplens added a commit that referenced this pull request Sep 28, 2026
…he dependencies up to date (#1058)

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

- **Row 73, gobco**: files excluded by build constraints are
type-checked anyway, so `cmd/server` and `internal/toolutil` panic and
the e2e harness is never instrumented. Reported as
[rillig/gobco#40](rillig/gobco#40), fixed in
[rillig/gobco#41](rillig/gobco#41). The
workaround is issue #1017.
- **Row 74, gitlab-org/gitlab**: the Orbit API page's five query
examples predate version 12 of the DSL. The fix is in review in
[gitlab-org/gitlab!258241](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/258241).
- **Rows 75 and 76, gitlab-org/orbit/knowledge-graph**: the DSL schema
says a path query may omit `rel_types`, and that the default neighbors
direction is `both`. Each is an issue
([knowledge-graph#1329](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/work_items/1329),
[knowledge-graph#1330](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/work_items/1330))
with a merge request that closes it
([knowledge-graph!2650](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2650),
[knowledge-graph!2651](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2651)).
These go in a new Orbit section.

## 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 #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](https://gitlab.com/gitlab-org/api/client-go/-/merge_requests/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](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/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:

- #1059: the six `actions-all` updates. These are SonarQube scan, the
three Docker setup and build actions on new commits of the same major,
and CodeQL 4.38.0 to 4.38.1.
- #1056: Alpine 3.24.1 to 3.24.2 for the runtime image.
- #1057: the five `npm-minor-patch` updates of the site. These are
Starlight 0.42.2, Astro 7.3.3, typescript-eslint 8.70.1 and Prettier
3.9.8.

**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](https://github.com/jmrplens/gitlab-mcp-server/actions/runs/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 #1046 added,
which 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.
@jmrplens

Copy link
Copy Markdown
Owner

Applied unchanged in #1058, which merged as 85e44fb together with the rest of this week's dependency updates.

@jmrplens jmrplens closed this Sep 28, 2026
@jmrplens
jmrplens deleted the dependabot/docker/alpine-3.24.2 branch September 28, 2026 18:53
@dependabot @github

dependabot Bot commented on behalf of github Sep 28, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file distribution Release artifacts, packaging, and install channels docker Dependabot: a container image update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant