MILAB-6714: drop private from gpu-info software package - #6
Merged
Conversation
pl-pkg gates docker auto-push on !isPrivate, so CI built the image and
wrote the entrypoint descriptor pointing at its tag, then skipped the
push. The published block 404s pulling that image at runtime.
The flag was written by a structure refresh run against a local
block-tools build predating the fix in @platforma-sdk/block-tools
(structurer now does removeField("private") for software packages).
xnacly
force-pushed
the
MILAB-6714_software-not-private
branch
from
August 11, 2026 11:23
c9effaf to
d36a970
Compare
DenKoren
approved these changes
Aug 11, 2026
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.
Problem
The block published on 2026-07-27 references a docker image that was never uploaded.
quay.io/milaboratories/pl-containers:platforma-open.milaboratories.gpu-test.gpu-info.main.c79fc91ff0c4does not exist; the June image (...1c637624b078) does. Any run of the block fails when the backend pulls it.Cause
"private": trueonsoftware/gpu-info/package.json.pl-pkggates docker auto-push on!isPrivate, so CI built the image, wrote the entrypoint descriptor pointing at its tag, and skipped the push. The build reported success.CI logs for the merge run confirm it:
Building docker images.../Docker image is built:with zero occurrences ofPublishing docker images.... The June run has both.The flag arrived in f49dae5 via a
structure refreshrun against a local block-tools build (thefile:/Users/.../block-tools/package.tgzoverride committed in that same commit and removed in 58f0308). That build predated the structurer fix in@platforma-sdk/block-tools@2.11.6, which stopped emittingprivateon software packages and now strips it on refresh.Change
Remove the field, plus a patch changeset so the block republishes.
Not included
This block's
.structureis still{"version":1}. A fullstructure refreshwith current block-tools would stripprivatetoo, but would also migrate to v2: build script toblock-tools software build, dropprepublishOnly, swap the@platforma-sdk/package-builderdevDep. Kept separate so this stays a minimal unblock.Verification
After merge, the
mainbuild should logPublishing docker images...and the new tag should resolve in the registry.Ticket: MILAB-6714
Greptile Summary
The PR removes the
privatepackage flag that preventedpl-pkgfrom pushing the GPU information Docker image and adds a patch changeset to trigger republication.private: A package-manifest flag that suppresses publication; removed from the GPU information software package so Docker auto-push is enabled.gpu-info: The software package that detects GPUs and reports their details; its source is unchanged, but its package publication status changes.pl-pkg: The Platforma package-building tool whose Docker auto-push behavior is gated by the package's private status; this PR enables its publishing path.changeset: Release metadata describing the package and semantic-version increment; a patch entry is added so a corrected artifact is released.Confidence Score: 5/5
The PR appears safe to merge, with no concrete blocking or non-blocking defects identified in the two focused metadata changes.
The package identifier in the changeset matches the modified workspace package, and removing the publication guard directly addresses the documented skipped Docker push without exposing an existing npm publication path.
Important Files Changed
private: trueso the existing software-package tooling can publish the generated Docker image.Reviews (1): Last reviewed commit: "MILAB-6714: drop private from gpu-info s..." | Re-trigger Greptile