Repository navigation
fix(deps): bump eclass-docker-fork to 1.4.0 - #2
Merged
Merged
Conversation
eclass-docker-fork 1.3.1 sent the registry credentials in the push request body, which Docker Engine >= 28.3.3 no longer reads. On the ubuntu-26.04 runners (Docker 29.4.2) every image push went out anonymously and failed with "Error tag docker push.", so v1.1.1 and v1.1.2 have no image on GHCR. 1.4.0 sends the credentials as the X-Registry-Auth header and logs Docker's error when a login, tag or push fails (0-vortex/eclass-docker-fork#2). The action image installs it from package.json, so repos that push images through the action get the fix with the next image.
1 of 11 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
Nov 12, 2026
## [1.1.3](v1.1.2...v1.1.3) (2026-11-12) ### 🐛 Bug Fixes * **deps:** bump eclass-docker-fork to 1.4.0 ([#2](#2)) ([303b512](303b512))
4 of 20 tasks
|
🎉 This PR is included in version 1.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 of 11 tasks
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
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.
Summary
Bumps eclass-docker-fork from 1.3.1 to 1.4.0. This fixes the image push that failed the v1.1.1 and v1.1.2 releases with "Error tag docker push." (run 43123015313).
1.3.1 passed the registry credentials to dockerode as plain push options, so they went into the request body and no
X-Registry-Authheader was sent. Docker Engine stopped reading credentials from the body in 28.3.3 (moby/moby@e4b1f89996).ubuntu-latestis now ubuntu-26.04 with Docker 29.4.2, so every push went out anonymously and GHCR refused it.1.4.0 (0-vortex/eclass-docker-fork#2) sends the
X-Registry-Authheader, logs Docker's own error when a login, tag or push fails, and uses dockerode 5.0.1. The lockfile diff only touches eclass-docker-fork's dependency tree.The action image installs its dependencies from
package.json, so repos that push images throughHyperCubeSphere/release@v1get the fix with the next image.Related: 0-vortex/eclass-docker-fork#1
Type
Checklist
npm ciaccepts the lockfile on npm 10, 11 and 12; this repo has no test or lint scriptsAI-assistance
An agent prepared the dependency bump and lockfile update.
Screenshots / recordings
None.
Post-deployment
Merging releases 1.1.3: semantic-release publishes
@hypercubesphere/release@1.1.3, pushesghcr.io/hypercubesphere/release:1.1.3and:latest, andsemantic-release-major-tagmovesv1to v1.1.3. After the run, check that the1.1.3image exists and thatv1points at v1.1.3.