Skip to content

🌱 images: bump pi 1.4.0 -> 1.5.0 - #16392

Merged
hivecommons-hive[bot] merged 3 commits into
v5from
cli-pin-bump/pi
Nov 3, 2026
Merged

hivecommons-hive[bot] merged 3 commits into
v5from
cli-pin-bump/pi

Conversation

@clubanderson

Copy link
Copy Markdown
Member

Part of #8419

Automated pin bump: pi 1.4.0 -> 1.5.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/41583688567; 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.5.0

Smoke (before this PR was opened)

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

$ pi --version
1.5.0

Model lists (not automated)

::warning::claudePinnedCLIModels has no 'version pinned in src/Dockerfile (X' comment to check
::warning::codex static list comment says 0.165.0 but src/Dockerfile pins 0.166.0
2 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.5.0

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 Nov 3, 2026
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Nov 3, 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 kellyaa 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

@kubestellar-prow kubestellar-prow Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 3, 2026
@github-actions

github-actions Bot commented Nov 3, 2026

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.

@github-actions

github-actions Bot commented Nov 3, 2026 •

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
2fea59d

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

Hive flagged this PR (author @clubanderson, head 2fea59d12384) 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.

Looks correct to me. npm view @earendil-works/pi-coding-agent@1.5.0 resolves (version 1.5.0 published), and the diff against merge-base moves all three places that must agree together: ARG PI_VERSION (src/Dockerfile:457), ARG PI_CODING_AGENT_VERSION (src/Dockerfile.contributor:489) and the expectation string in src/pkg/config/dockerfile_contributor_test.go:20. The CANCELLED rollup entries are superseded concurrency runs, not failures.

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

@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.

Looks correct to me. Verified against head 9cbc2a3:

  • @earendil-works/pi-coding-agent@1.5.0 exists on the npm registry (dist-tags.latest = 1.5.0, published 2026-11-02), so the pin resolves and --ignore-scripts install path is unchanged.
  • All three places that hard-code the version move together: src/Dockerfile:457 (PI_VERSION), src/Dockerfile.contributor:489 (PI_CODING_AGENT_VERSION), and the guard in src/pkg/config/dockerfile_contributor_test.go:20. src/deploy/test_supply_chain_pins.sh:90 only asserts the ARG is non-latest, so it stays green.
  • Both image builds (amd64/arm64, hive + contributor) and the pin-bump self-test passed on this head.

One low docs note, not a blocker for this automated PR: src/docs/contributor-relay.md:224 says "The contributor image pins Pi 1.4.0", which becomes stale on merge. The 1.4.0+ minimums elsewhere (docs/backend-setup.md:15, contribute_landing.go:1623) remain true and need no change.

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

@hivecommons-hive

hivecommons-hive Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

Review findings from adjudicator-5 (folded here because this head already carries its hive review):

docs-currency (delta re-review, head 9cbc2a3) — the delta since 2fea59d is only Merge branch 'v5' (already-landed base commits); the PR's own diff vs v5 is unchanged (pi 1.4.0 → 1.5.0 in both Dockerfiles + test pin). No prior findings to re-check.

One operator-facing doc goes stale with this bump:

  • src/docs/contributor-relay.md:224 — "The contributor image pins Pi 1.4.0" becomes false once PI_CODING_AGENT_VERSION=1.5.0 lands (src/Dockerfile.contributor:489). The matching host-install snippet at src/docs/contributor-relay.md:256 also pins @1.4.0. src/docs/cli-pins.md:10 is fine (names the ARGs, no version literal).
  The contributor image pins Pi 1.5.0; this route requires **Pi 1.4.0+** for its

and at line 256:

npm install -g @earendil-works/pi-coding-agent@1.5.0

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

Why:

  • the review swarm requested changes

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.

Review findings from reviewer (folded here because this head already carries its hive review):

Looks correct to me. Read the three changed sites against v5: src/Dockerfile:457, src/Dockerfile.contributor:489 and the literal assertion in src/pkg/config/dockerfile_contributor_test.go:20 all move together, which is exactly the set src/scripts/cli-pin-bump.sh:440-447 owns, and src/deploy/test_supply_chain_pins.sh:90 still sees a non-latest pin. No other code path reads the pi version.

One low-severity docs drift this bump script does not cover (and no prior pi bump has had to, since the 1.4.0 pin and this prose landed together in 66cb92b / #15969):

  • src/docs/contributor-relay.md:224 states as fact "The contributor image pins Pi 1.4.0" — after this merges that sentence is wrong. The @1.4.0 host-install commands at contributor-relay.md:256 and src/pkg/dashboard/contribute_landing.go:1623,1805 are minimum-version instructions ("Pi 1.4.0+") and remain valid, so I'd only touch the one sentence.

Not blocking: fine to land as-is and fix the sentence in a follow-up, or have cli-pin-bump.sh rewrite that line alongside the Go test assertion so future pi bumps don't drift it again.

Evidence bundle `#16392d434487` sha256:e458ec41fb256d12aca9d8168e0059f1dd525ce976a621929f4de2342611ec01 — download from the dashboard or `hivectl review evidence #16392`.

@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.

docs-currency (delta re-review at d434487; delta is a v5 rebase with no pi-related doc changes)

Still present from the previous review: src/docs/contributor-relay.md still describes the contributor image as pinning Pi 1.4.0 while src/Dockerfile.contributor now sets ARG PI_CODING_AGENT_VERSION=1.5.0 (and src/Dockerfile ARG PI_VERSION=1.5.0).

src/docs/contributor-relay.md:224

  The contributor image pins Pi 1.5.0; this route requires **Pi 1.4.0+** for its

src/docs/contributor-relay.md:256 (the native-Mac install command for the same route should match the image pin)

npm install -g @earendil-works/pi-coding-agent@1.5.0

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

@hivecommons-hive
hivecommons-hive Bot merged commit 50197bb into v5 Nov 3, 2026
86 of 87 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the cli-pin-bump/pi branch November 3, 2026 07:47
@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 d434487.

@github-actions

github-actions Bot commented Nov 3, 2026

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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant