chore: bump @oplabs/talos-client to 0.0.31 - #356
Draft
clement-ux wants to merge 1 commit into
Draft
clement-ux wants to merge 1 commit into
clement-ux wants to merge 1 commit into
Conversation
The published 0.0.30 does not carry the client build the Talos admin expects (contentHash eed13408dead), so this runner shows as outdated. 0.0.31 is cut from talos main with that build. Requires @oplabs/talos-client@0.0.31 to be published first (oplabs/talos tag v0.0.31); until then the runner image build cannot install it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Why
The Talos admin flags this runner as running an outdated
@talos/client(it expects contentHasheed13408dead). The published 0.0.30 was cut before later client changes and carries98e7cc59335e, so no published version matched. 0.0.31 is cut from talosmainwith the expected build: oplabs/talos#50.What
Bump the
@oplabs/talos-clientpeer pin to0.0.31.dockerfile-actionsreads that pin to install the client into the runner image. Nothing else pins the version.Changes in the client since 0.0.28 include a seed-file lint that rejects
ON CONFLICT … DO UPDATE:migrations/seed_schedules.sqlhas none, so the runner boot is unaffected.Merge only after
@oplabs/talos-client@0.0.31is published (tagv0.0.31on oplabs/talos). Before that, the image build cannot install the package. Once merged, the new image still needs the signed release (release:propose+release:sign) to roll out.🤖 Generated with Claude Code