Skip to content

Pin the labspace-infra images to v0.32.0 by digest - #22

Merged
mathieu-benoit merged 1 commit into
mainfrom
pin-labspace-infra-v0.32.0
Nov 18, 2026
Merged

mathieu-benoit merged 1 commit into
mainfrom
pin-labspace-infra-v0.32.0

Conversation

@mathieu-benoit

Copy link
Copy Markdown
Owner

The Labspace kit took dockersamples/labspace-interface:latest and dockersamples/labspace-support-vscode-extension:latest, so which interface a kit version shipped depended on when it was built. This pins both to the labspace-infra v0.32.0 release, by tag and multi-arch index digest:

  • dockersamples/labspace-interface:v0.32.0@sha256:7d9848ad2da9bb8bc51b279a4439bf8ba21bc8ddfb99175ac5b9d65264db8227
  • dockersamples/labspace-support-vscode-extension:v0.32.0@sha256:a6685edeb1de044d92a8def430295c05e5aac821fefb882db0105717932e1333

Today these are also the latest digests, so the content of the kit doesn't change. v0.32.0 brings Run and Save buttons on code blocks inside blockquotes and alerts (labspace-infra#234).

  • kit/labspace.dockerfile: the two ARGs, plus a comment with the command to get the digest for the next release.
  • README.md: the "Pin by digest" open point is removed, and the interface row says which release is pinned.

Checked: the kit builds locally with docker buildx build --builder kit-builder kit -f kit/labspace.yaml. CI builds both platforms and runs kit-tck on this PR.

Moving to a later labspace-infra release is now an explicit change to these two lines, for example as part of a version bump.

🤖 Generated with Claude Code

The interface and the VS Code support extension came from :latest, so the
same kit version could ship a different interface depending on when it was
built. Pin both to the v0.32.0 release by tag and index digest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mathieu-benoit
mathieu-benoit merged commit 53bd0cd into main Nov 18, 2026
4 checks passed
@mathieu-benoit
mathieu-benoit deleted the pin-labspace-infra-v0.32.0 branch November 18, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant