Repository navigation
chore(ci): bump docker/setup-buildx-action from 4.2.0 to 4.3.0 in the docker-actions group - #867
Conversation
Bumps the docker-actions group with 1 update: [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action). Updates `docker/setup-buildx-action` from 4.2.0 to 4.3.0 - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@bb05f3f...37fe631) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-version: 4.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: docker-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Benchmark delta (vs
|
| size | recall@k (head Δ vs base) | MRR (head Δ vs base) | p99 (ms) |
|---|---|---|---|
| 50 | ✅ 0.5649 (+0.0000) | ✅ 0.4978 (+0.0000) | ✅ 0.549 (base 0.650) |
| 83 | ✅ 0.3825 (+0.0000) | ✅ 0.3242 (+0.0000) | ✅ 0.720 (base 1.205) |
| 1000 | ✅ 0.1475 (+0.0000) | ✅ 0.1456 (+0.0000) | ✅ 42.144 (base 47.855) |
Per-backend × per-size matrix
| backend | size | recall@k (Δ) | MRR (Δ) | p99 (ms) |
|---|---|---|---|---|
| bm25 | 100 | ✅ 0.3825 (+0.0000) | ✅ 0.3399 (+0.0000) | ✅ 6.579 (base 8.399) |
| bm25 | 500 | ✅ 0.2250 (+0.0000) | ✅ 0.2165 (+0.0000) | ✅ 32.411 (base 41.865) |
| bm25 | 1000 | ✅ 0.1575 (+0.0000) | ✅ 0.1525 (+0.0000) | ✅ 88.475 (base 112.387) |
| embedding_hashing | 100 | ✅ 0.5175 (+0.0000) | ✅ 0.4360 (+0.0000) | ✅ 8.039 (base 7.218) |
| embedding_hashing | 500 | ✅ 0.2700 (+0.0000) | ✅ 0.2674 (+0.0000) | ✅ 41.655 (base 43.171) |
| embedding_hashing | 1000 | ✅ 0.2000 (+0.0000) | ✅ 0.1931 (+0.0000) | ✅ 99.227 (base 102.979) |
| embedding_st | 100 | skipped (skipped: missing sentence-transformers) | — | — |
| embedding_st | 500 | skipped (skipped: missing sentence-transformers) | — | — |
| embedding_st | 1000 | skipped (skipped: missing sentence-transformers) | — | — |
| fuzzy | 100 | skipped (skipped: missing rapidfuzz) | — | — |
| fuzzy | 500 | skipped (skipped: missing rapidfuzz) | — | — |
| fuzzy | 1000 | skipped (skipped: missing rapidfuzz) | — | — |
| tfidf | 100 | ✅ 0.3825 (+0.0000) | ✅ 0.3220 (+0.0000) | ✅ 1.088 (base 1.193) |
| tfidf | 500 | ✅ 0.2325 (+0.0000) | ✅ 0.2314 (+0.0000) | ✅ 10.453 (base 10.803) |
| tfidf | 1000 | ✅ 0.1475 (+0.0000) | ✅ 0.1456 (+0.0000) | ✅ 36.100 (base 42.986) |
Context pipeline (per scenario)
| scenario | tokens | dropped | dedup |
|---|---|---|---|
| large_catalog | 1480 (base 1480, Δ+0) | 0 (base 0, Δ+0) | 0 (base 0, Δ+0) |
| long_conversation | 2500 (base 2500, Δ+0) | 0 (base 0, Δ+0) | 0 (base 0, Δ+0) |
| mixed_payload | 488 (base 488, Δ+0) | 0 (base 0, Δ+0) | 0 (base 0, Δ+0) |
| short_conversation | 487 (base 487, Δ+0) | 0 (base 0, Δ+0) | 0 (base 0, Δ+0) |
| stress_conversation | 6590 (base 6590, Δ+0) | 11 (base 11, Δ+0) | 4 (base 4, Δ+0) |
| tiny_payload | 256 (base 256, Δ+0) | 0 (base 0, Δ+0) | 0 (base 0, Δ+0) |
Numbers come from make benchmark / make benchmark-matrix.
Latency is hardware-dependent — treat the markers as a rough guide.
See benchmarks/scorecard.md for the full picture.
dgenio
left a comment
There was a problem hiding this comment.
Review — correct, but nothing here or in CI has actually run it
One line: docker/setup-buildx-action@bb05f3f → @37fe631, both commented # v4. No inputs changed. Status: confirmed from the diff.
Two things worth saying rather than rubber-stamping:
1. The version comment does not move, so it carries no information. Both SHAs are # v4. That is Dependabot doing the right thing under the SHA-pinning policy this repo adopted in #748 — the tag floats, the SHA is the pin — but it means the diff cannot tell a reviewer what changed between the two commits. For an action that configures the builder in an image-publishing job, the SHA is the whole review surface.
2. docker-publish.yml is not exercised by any check on this PR. It is not part of the PR CI graph, so the green ticks here are evidence about the rest of the repository, not about the file being changed. This is the third contextweaver PR this cycle where the only changed file is one PR CI never runs — worth a workflow_dispatch after merge rather than discovering it at the next release.
Ordering. #868 also touches docker-publish.yml, on the actions/checkout line rather than this one. The two merge cleanly and will not conflict; the only cost is that whichever lands second has CI evidence computed without the other. Merging #869 (the release-path fix) first, then #868, then this, keeps the release path exercised once with everything in place.
Recommendation: merge, then dispatch docker-publish.yml once to confirm the builder still comes up. Not approving — not mine, and it needs an approving review from someone who can act on the merge.
Generated by Claude Code
Bumps the docker-actions group with 1 update: docker/setup-buildx-action.
Updates
docker/setup-buildx-actionfrom 4.2.0 to 4.3.0Release notes
Sourced from docker/setup-buildx-action's releases.
Commits
37fe631Merge pull request #595 from docker/dependabot/npm_and_yarn/docker/actions-to...b5c4f91[dependabot skip] chore: update generated content3e93b63build(deps): bump@docker/actions-toolkitfrom 0.92.0 to 0.95.0e527031Merge pull request #600 from docker/dependabot/npm_and_yarn/brace-expansion-1...c68814b[dependabot skip] chore: update generated content3f891b0build(deps): bump brace-expansion from 1.1.13 to 1.1.18787db26Merge pull request #585 from docker/dependabot/npm_and_yarn/js-yaml-5.2.1f779368[dependabot skip] chore: update generated content7d5e604build(deps): bump js-yaml from 5.2.0 to 5.3.0292c2fbMerge pull request #590 from docker/dependabot/github_actions/actions/setup-n...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions