Bump docker/setup-buildx-action from 4.3.0 to 4.4.1 in the github-actions-minor-patch group by dependabot[bot] · Pull Request #502 · orionrobots/orionrobots.github.io

dependabot · 2026-09-19T19:45:12Z

Bumps the github-actions-minor-patch group with 1 update: docker/setup-buildx-action.

Updates docker/setup-buildx-action from 4.3.0 to 4.4.1

Release notes

Sourced from docker/setup-buildx-action's releases.

v4.4.1

Skip BuildKit image pre-pulls for explicit endpoints by @crazy-max in docker/setup-buildx-action#624

Full Changelog: docker/setup-buildx-action@v4.4.0...v4.4.1

v4.4.0

Use official Buildx releases for cloud driver by @crazy-max in docker/setup-buildx-action#606

Pull BuildKit image before builder creation by @crazy-max in docker/setup-buildx-action#609

Use shared error helpers for Buildx and Docker commands by @crazy-max in docker/setup-buildx-action#620

Bump @docker/actions-toolkit from 0.95.0 to 0.100.0 in docker/setup-buildx-action#610 docker/setup-buildx-action#618 docker/setup-buildx-action#619

Bump @humanfs/node from 0.16.7 to 0.16.8 in docker/setup-buildx-action#614

Bump js-yaml from 5.3.0 to 5.4.2 in docker/setup-buildx-action#608 docker/setup-buildx-action#617

Bump postcss-selector-parser from 7.1.1 to 7.1.5 in docker/setup-buildx-action#611

Full Changelog: docker/setup-buildx-action@v4.3.0...v4.4.0

Commits

f87e599 Merge pull request #624 from crazy-max/skip-pull-with-endpoint
e700274 chore: update generated content
3061c91 skip BuildKit image pre-pulls for explicit endpoints
594f3bf Merge pull request #609 from crazy-max/pull-buildkit-image-before-create
bd6e702 chore: update generated content
6268c9d pull BuildKit image before builder creation
e823525 Merge pull request #621 from docker/dependabot/github_actions/codeql-actions-...
533ed8e build(deps): bump the codeql-actions group with 2 updates
bedaf13 Merge pull request #620 from crazy-max/shared-error-helpers
d5079fb chore: update generated content
Additional commits viewable in compare view

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 <dependency name> major version will 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 version will 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

Bumps the github-actions-minor-patch group with 1 update: [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action). Updates `docker/setup-buildx-action` from 4.3.0 to 4.4.1 - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@v4.3.0...v4.4.1) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-version: 4.4.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>

github-actions · 2026-09-19T19:48:32Z

✅⚠️MegaLinter analysis: Success with warnings

Descriptor	Linter	Files	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	7	0	0	0.15s
⚠️ ACTION	zizmor	7	1	0	0.56s
✅ BASH	bash-exec	2	0	0	0.02s
✅ BASH	shellcheck	2	0	0	0.22s
⚠️ BASH	shfmt	2	1	0	0.01s
⚠️ C	cppcheck	8	8	0	0.09s
⚠️ CPP	cppcheck	8	8	0	0.11s
✅ JSON	npm-package-json-lint	yes	no	no	0.84s
✅ JSON	v8r	17	0	0	9.82s
✅ REPOSITORY	betterleaks	yes	no	no	1.69s
✅ REPOSITORY	git_diff	yes	no	no	1.0s
✅ REPOSITORY	grype	yes	no	no	77.52s
✅ REPOSITORY	osv-scanner	yes	no	no	1.49s
✅ REPOSITORY	secretlint	yes	no	no	16.19s
✅ REPOSITORY	syft	yes	no	no	3.77s
✅ REPOSITORY	trivy-sbom	yes	no	no	2.15s
✅ REPOSITORY	trufflehog	yes	no	no	8.41s
✅ TYPESCRIPT	ts-standard	3	0	0	7.17s
✅ XML	xmllint	1	0	0	9.4s
✅ YAML	v8r	15	0	0	11.01s

Detailed Issues

⚠️ C / cppcheck - 8 errors

Checking assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h ...
assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
1/8 files checked 12% done
Checking assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h ...
assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
2/8 files checked 19% done
Checking assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h ...
assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
3/8 files checked 31% done
Checking assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h ...
assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
4/8 files checked 49% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
5/8 files checked 62% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
6/8 files checked 69% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
7/8 files checked 81% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
8/8 files checked 100% done

⚠️ CPP / cppcheck - 8 errors

Checking assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h ...
assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
1/8 files checked 12% done
Checking assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h ...
assets/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
2/8 files checked 19% done
Checking assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h ...
assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
3/8 files checked 31% done
Checking assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h ...
assets/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
4/8 files checked 49% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
5/8 files checked 62% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/alternative_demo/Motors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
6/8 files checked 69% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/DistanceSensor.h:3:1: error: Code 'classSR04{' is invalid C code. [syntaxError]
class SR04 {
^
7/8 files checked 81% done
Checking galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h ...
galleries/2013-11-14-explorer-wall-avoider-kit/demo_sketch/TurtleMotors.h:3:1: error: Code 'classMotor{' is invalid C code. [syntaxError]
class Motor {
^
8/8 files checked 100% done

⚠️ BASH / shfmt - 1 error

diff .github/scripts/validate-local-build.sh.orig .github/scripts/validate-local-build.sh
--- .github/scripts/validate-local-build.sh.orig
+++ .github/scripts/validate-local-build.sh
@@ -30,9 +30,9 @@
 echo ""
 echo "=== Step 1: Checking http_serve is running ==="
 if ! docker ps --format '{{.Names}}' | grep -q "^${HTTP_SERVE_CONTAINER}$"; then
-  echo "ERROR: ${HTTP_SERVE_CONTAINER} is not running."
-  echo "Start it with: docker compose --profile manual up -d http_serve"
-  exit 1
+    echo "ERROR: ${HTTP_SERVE_CONTAINER} is not running."
+    echo "Start it with: docker compose --profile manual up -d http_serve"
+    exit 1
 fi
 
 # ─── Step 2: Quick HTTP smoke check from host ─────────────────────────────────
@@ -39,17 +39,17 @@
 echo ""
 echo "=== Step 2: HTTP smoke checks (host -> port ${HOST_PORT}) ==="
 for path in "/" "/construction_guide.html" "/tags/arduino/"; do
-  status=$(curl -s -o /dev/null -w "%{http_code}" "http://localhost:${HOST_PORT}${path}")
-  if [[ "$status" == "200" ]]; then
-    echo "  OK  ${path} -> ${status}"
-  else
-    echo "  FAIL ${path} -> ${status}"
-    SMOKE_FAILED=1
-  fi
+    status=$(curl -s -o /dev/null -w "%{http_code}" "http://localhost:${HOST_PORT}${path}")
+    if [[ "$status" == "200" ]]; then
+        echo "  OK  ${path} -> ${status}"
+    else
+        echo "  FAIL ${path} -> ${status}"
+        SMOKE_FAILED=1
+    fi
 done
 if [[ -n "${SMOKE_FAILED:-}" ]]; then
-  echo "ERROR: Smoke checks failed."
-  exit 1
+    echo "ERROR: Smoke checks failed."
+    exit 1
 fi
 
 # ─── Step 3: Verify AVIF images are generated ────────────────────────────────
@@ -62,8 +62,8 @@
 echo "  Post body WebP: ${webp_count}"
 echo "  Thumbnail AVIF: ${thumb_avif}"
 if [[ "$avif_count" -eq 0 ]]; then
-  echo "ERROR: No AVIF images found in _site/assets/images. Was the build run?"
-  exit 1
+    echo "ERROR: No AVIF images found in _site/assets/images. Was the build run?"
+    exit 1
 fi
 
 # ─── Step 4: BDD tests ─────────────────────────────────────────────────────
@@ -71,14 +71,14 @@
 echo "=== Step 4: BDD tests (via Docker, network: ${DOCKER_NETWORK}) ==="
 
 docker run --rm \
-  --network "${DOCKER_NETWORK}" \
-  -e BASE_URL="${BASE_URL}" \
-  -v "${PROJECT_ROOT}/tests:/app/src/tests" \
-  -v "${PROJECT_ROOT}/package.json:/app/src/package.json" \
-  -v "${PROJECT_ROOT}/package-lock.json:/app/src/package-lock.json" \
-  -v "${PROJECT_ROOT}/cucumber.js:/app/src/cucumber.js" \
-  "${TEST_IMAGE}" \
-  npm run test:bdd
+    --network "${DOCKER_NETWORK}" \
+    -e BASE_URL="${BASE_URL}" \
+    -v "${PROJECT_ROOT}/tests:/app/src/tests" \
+    -v "${PROJECT_ROOT}/package.json:/app/src/package.json" \
+    -v "${PROJECT_ROOT}/package-lock.json:/app/src/package-lock.json" \
+    -v "${PROJECT_ROOT}/cucumber.js:/app/src/cucumber.js" \
+    "${TEST_IMAGE}" \
+    npm run test:bdd
 
 echo ""
 echo "=== Validation complete ==="

⚠️ ACTION / zizmor - 1 error

INFO zizmor: 🌈 zizmor v1.25.0
 WARN audit:audit{input=Workflow(file://.github/workflows/on_call_build_site.yaml)}: zizmor::audit::unpinned_uses: failed to look up commit for docker/setup-buildx-action@v4.4.1: couldn't list branches for docker/setup-buildx-action
fatal: no audit was performed
'artipacked' audit failed on file://.github/workflows/on_call_build_site.yaml

Caused by:
    0: error in 'artipacked' audit
    1: couldn't list tags for actions/checkout
    2: request error while accessing GitHub API
    3: HTTP status client error (401 Unauthorized) for url (https://github.com/actions/checkout.git/git-upload-pack)


[ACTION_ZIZMOR_ERROR_GITHUB_API_UNREACHABLE] Zizmor could not access a repository referenced by a `uses:` clause via the GitHub API (missing token, insufficient scope, or cross-repo private access).
To allow zizmor to authenticate with GITHUB_TOKEN (or a PAT with `Contents: read-only`), whitelist the variable in your .mega-linter.yml:
ACTION_ZIZMOR_UNSECURED_ENV_VARIABLES:
  - GITHUB_TOKEN
If the referenced workflow is in a private repo outside the current one, provide a PAT with cross-repo access instead of the default GITHUB_TOKEN, or run zizmor in offline mode.

Notices

⚠️ Your configuration references items that have been removed from MegaLinter and are ignored: REPOSITORY_KICS. See Removed linters to find their replacements.

See detailed reports in MegaLinter artifacts

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

oxsecurity/megalinter/flavors/dotnetweb@v10.1.0 (81 linters)

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

Documentation: Custom Flavors
Command: npx mega-linter-runner@10.1.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,ACTION_ZIZMOR,BASH_EXEC,BASH_SHELLCHECK,BASH_SHFMT,C_CPPCHECK,CPP_CPPCHECK,JSON_V8R,JSON_NPM_PACKAGE_JSON_LINT,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_GRYPE,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,TYPESCRIPT_STANDARD,XML_XMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository

github-actions · 2026-09-19T19:56:42Z

🐳 Docker Base Image Available

A new base Docker image has been built and pushed for this PR:

Image: ghcr.io/orionrobots/orionrobots-site.base:502

How to use this image:

# Pull the image
docker pull ghcr.io/orionrobots/orionrobots-site.base:502

# Run with the image
docker run -it ghcr.io/orionrobots/orionrobots-site.base:502 bash

For local development:

You can use this image as a base for testing changes without rebuilding dependencies.

This comment is automatically updated when the base image is rebuilt.

…inor-patch-b530e7f9d1

dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Sep 19, 2026

Merge branch 'master' into dependabot/github_actions/github-actions-m…

1db55b7

…inor-patch-b530e7f9d1

dannystaple merged commit ee22fa8 into master Sep 22, 2026
11 checks passed

dannystaple deleted the dependabot/github_actions/github-actions-minor-patch-b530e7f9d1 branch September 22, 2026 14:10

Navigation Menu

Bump docker/setup-buildx-action from 4.3.0 to 4.4.1 in the github-actions-minor-patch group - #502

Bump docker/setup-buildx-action from 4.3.0 to 4.4.1 in the github-actions-minor-patch group#502
dannystaple merged 2 commits into
masterfrom
dependabot/github_actions/github-actions-minor-patch-b530e7f9d1

dependabot Bot commented on behalf of github Sep 19, 2026

Uh oh!

github-actions Bot commented Sep 19, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 19, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

dependabot Bot commented on behalf of github Sep 19, 2026

v4.4.1

v4.4.0

Uh oh!

github-actions Bot commented Sep 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅⚠️MegaLinter analysis: Success with warnings

Detailed Issues

Notices

Uh oh!

github-actions Bot commented Sep 19, 2026

🐳 Docker Base Image Available

How to use this image:

For local development:

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions Bot commented Sep 19, 2026 •

edited

Loading