Repository navigation
chore: point the release manifest's image source at cryptos-appliance - #34
Merged
Merged
Conversation
The node boot image build moved to CryptOS-PKI/cryptos-appliance (cryptos-node#349). Rename the manifest key from node to appliance and point it at the new repo; nothing consumes the key programmatically yet, and the manifest is still v0.1.0-dev, so this is safe before any real release is cut. Refs CryptOS-PKI/cryptos-node#349 Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Bugs5382
marked this pull request as ready for review
October 6, 2026 19:38
github-actions
Bot
added
the
skip-changelog
Contributor
Author
|
Renamed the release manifest's |
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.
What and why
CryptOS-PKI/cryptos-node#349 moves the node boot image build to
CryptOS-PKI/cryptos-appliance. The release manifest's
nodekey pinned the image tocryptos-node, which no longer builds one. Renamed the key to
applianceand pointedrepo:at CryptOS-PKI/cryptos-appliance, and updatedmanifest/README.mdand thisrepo's README to match.
Nothing reads the manifest key programmatically yet (checked
Taskfile.ymland the repofor any script), and
versionis stillv0.1.0-dev(unreleased), so the rename is safe.Refs CryptOS-PKI/cryptos-node#349
Verification
How this was verified
task ci(helm lint, 0 failed),task license(0/8 changed). No code or chart templateschanged, only the manifest and docs, so no Go/Helm tests apply here.
Before merging: add a closing comment summarizing what was actually done in this PR
(not just the checked boxes).