Skip to content

🌱 images: bump goose 1.56.0 -> 1.57.0 - #15317

Merged
hivecommons-hive[bot] merged 2 commits into
v5from
cli-pin-bump/goose
Oct 29, 2026
Merged

hivecommons-hive[bot] merged 2 commits into
v5from
cli-pin-bump/goose

Conversation

@clubanderson

Copy link
Copy Markdown
Member

Part of #8419

Automated pin bump: goose 1.56.0 -> 1.57.0 in src/Dockerfile and src/Dockerfile.contributor.

Provenance

Every value below was resolved by src/scripts/cli-pin-bump.sh in run https://github.com/hivecommons/hive/actions/runs/40823383821; digests are computed from the downloaded artifacts and cross-checked against the vendor-published digest where one exists (never copied from a page).

VERSION=1.57.0
SHA256_AMD64=10eb96cb6a159b6e1d38eeedbef6ab64cd28168aad91948f1fa5c34eefdf98e3
SHA256_ARM64=c32605acfd560aeb2adbf17ec359cc0217e28022a7e647b35a6af5dcfca91749

Smoke (before this PR was opened)

src/Dockerfile built for linux/amd64 with the new pin; inside the image:

$ goose --version
 1.57.0

Model lists (not automated)

::warning::claudePinnedCLIModels has no 'version pinned in src/Dockerfile (X' comment to check
1 model-list drift finding(s) against the CLI pins; also review static/index.html and src/pkg/tokens/pricing.go by hand.
  • Allowlists and static fallbacks in src/pkg/dashboard/cli_models*.go match the new pin's model set, and their "matches CLI version" comments name it
  • static/index.html model options updated
  • src/pkg/tokens/pricing.go has prices for any new model

The docker workflow on this PR builds both images for linux/amd64 and linux/arm64 (every hash-verified layer runs sha256sum -c / sha512sum -c), and the backend smoke's pinned lane picks the new CLI up on its next run. See src/docs/cli-pins.md.

Opened by .github/workflows/cli-pin-bump.yml.

Automated pin bump (#8419). Digests recomputed from the downloaded
release artifacts by src/scripts/cli-pin-bump.sh:

  VERSION=1.57.0
  SHA256_AMD64=10eb96cb6a159b6e1d38eeedbef6ab64cd28168aad91948f1fa5c34eefdf98e3
  SHA256_ARM64=c32605acfd560aeb2adbf17ec359cc0217e28022a7e647b35a6af5dcfca91749

Signed-off-by: hive-release[bot] <hive-release@hive.kubestellar.io>
Signed-off-by: clubanderson <407614+clubanderson@users.noreply.github.com>
@clubanderson clubanderson added dependencies Pull requests that update a dependency file security no-changelog No changelog fragment required labels Oct 29, 2026
@clubanderson
clubanderson requested a review from hanthor as a code owner October 29, 2026 05:31
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Oct 29, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign hanthor for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions

Copy link
Copy Markdown
Contributor

Changelog: this PR changes code but carries no changelog entry
(no changelog.d/ fragment and no CHANGELOG.md edit).

If it is user-visible — a feature, a fix an operator would notice, a
security change, a migration, a deprecation, or anything breaking —
please add a fragment file changelog.d/<category>-<pr-or-slug>.md
containing exactly your entry (see changelog.d/README.md; the
category is one of added/changed/deprecated/fixed/security). Please
do not append to CHANGELOG.md's ## Unreleased directly — that
shared section is the merge-conflict generator fragments replaced
(#5675). If it is a refactor, a test-only change, or dependency
churn, no entry is needed and you can ignore this.

This is a reminder, not a gate; it never blocks a merge.

@kubestellar-prow kubestellar-prow Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 29, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

No conflicting open PRs or same-file overlaps were found.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@clubanderson is auto-promoted for contributor-lane merging on this PR: the last 5 merged PRs by this author in this hive's repositories have no revert or sentinel-alert evidence. CI, reviewer verdict, diff fences, soak, holds and branch protection still apply.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@clubanderson this PR is held at stage/071-needs-author and the hive will not merge it yet.

Failing checks:

  • build-and-test

Next: the hive does not push to your branch. Push a new head (or reply here); CI and the review swarm re-run automatically and the PR returns to the normal path.

@hivecommons-hive

Copy link
Copy Markdown
Contributor
ef2b2ca

ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blocked

Hive flagged this PR (author @clubanderson, head ef2b2ca2e5d9) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 2 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • src/Dockerfile
    • src/Dockerfile.contributor

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The red checks on this PR are not this PR's fault; the pin bump itself looks fine to me.

What I verified at ef2b2ca:

  • Diff is strictly the three ARG GOOSE_* values in src/Dockerfile:345-347 and src/Dockerfile.contributor:366-368; the install step is untouched and still hard-fails on a digest mismatch via sha256sum -c (src/Dockerfile:355), so a wrong hash cannot produce an image — it produces a build failure.
  • The failing test (dashboard …), coverage, build-and-test shards: this branch's merge-base with v5 is 15207d3eb, which still has the one-argument stageTrackerResolveLinkedPRs(items) at stage_tracker_linked_progress_test.go:95. That compile error was fixed on v5 by #15301 (2f05d8e18), merged after this PR was opened. A rebase/update-branch onto current v5 should turn those green; nothing in the Dockerfiles can affect them.
  • Digests come from src/scripts/cli-pin-bump.sh (computed from downloaded artifacts, digest() at L115) rather than copied by hand; the build (linux/arm64 …) job that actually exercises the checksum is still running. I have not independently re-fetched the upstream tarballs, so that job is the real verification of the hash values.

Suggested next step for whoever is tending the queue: update the branch from v5 and let the Docker build finish. No decision needed beyond that.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Deferred to shared-CI incident #15322: the failing checks here (test (dashboard N/4), test (dashboard shuffle N/3), test, coverage) are red on v5 HEAD itself (stageTrackerResolveLinkedPRs arity mismatch in a test file), not caused by this Dockerfile-only pin bump. #15321 fixes the baseline; this PR re-runs once it lands.


🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Shared-CI incident #15322 is now resolved on v5 (2f05d8e). The red checks here ran against the pre-fix base; rebasing/updating this branch onto current v5 should turn them green — nothing in this diff needs to change.


🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

hive/awaiting-ci: the red run (05:31Z) compiled against v5 between #15236 and its follow-up #15301 (stage_tracker_linked_progress_test.go: not enough arguments in call to stageTrackerResolveLinkedPRs) — not this diff. Merged origin/v5 into the branch for a fresh run. CI pending — sweep will merge when green.


🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive
hivecommons-hive Bot merged commit 80008ac into v5 Oct 29, 2026
81 of 82 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the cli-pin-bump/goose branch October 29, 2026 06:54
@hivecommons-hive

Copy link
Copy Markdown
Contributor
Evidence bundle `#15317e082268` sha256:281bddf3b62a67f5e01414dd800251098da857512243f4b2e5fbb83ba70e9dfe — download from the dashboard or `hivectl review evidence #15317`.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

merged by Hive trusted-author auto-merge: author @clubanderson holds role owner and GitHub permission admin on repo; CI green at e082268.

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback

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

Labels

dco-signoff: yes Indicates the PR's author has signed the DCO. dependencies Pull requests that update a dependency file no-changelog No changelog fragment required security size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant