Repository navigation
docs: build-your-own replaces release downloads, say where each part runs - #109
Merged
Merged
Conversation
…runs Refs #106 Refs #107 Refs CryptOS-PKI/cryptos-manager#182 Refs CryptOS-PKI/cryptos-release#38 Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Bugs5382
marked this pull request as ready for review
October 14, 2026 15:53
cryptos-manager#181 makes a release tag publish the manager image and chart. Update the repo overview and the Helm/break-glass pages from "build your own" to pulling the published image at a release tag, with building your own as the alternative. Refs #109 Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
The appliance release comes back, unsigned: each v* tag attaches the unsigned ISO and UKI, cryptosctl, a build-manifest.json and SHA256SUMS -- never a project-signed image. State plainly, near the top of the download and Secure Boot pages, that every image a user runs is signed by them: sign the download with your own Secure Boot key, or build and sign from source. Verification is sha256sum against SHA256SUMS, or rebuilding from the tag and comparing the hash -- no attestation, since the project signs nothing. Refs #109 Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Contributor
Author
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
Combines website#106 and website#107 in one PR because they land on the same file (
docs/install-deploy/build-bootable-image.md): #106 removes its "Release downloads" section, #107 adds the "where it runs" statement right above it.install-deploy/build-bootable-image.md) and a near-identical stray section intry-it-locally/install-cryptosctl.md; fixesabout/repos.md's release-asset and release-manifest wording; fixes two more "download a release binary" mentions found while mapping references (install-deploy/bootstrap-apply.md,using/setup.md) and one more release-asset table (concepts/image-factory.md).cryptos-appliance'sdocs/image-upgrade.md) and "Check the source you built" (verifying tags/commits/pins).install-deploy/build-bootable-image.md,use-cases/kubernetes.md(also makes the certificate-consumer framing explicit) andfleet-manager/overview.md.fleet-manager/helm.mdandfleet-manager/first-run/break-glass.mdto match cryptos-manager#182's "build and push your own image" default (the website half of that issue).Refs #106
Refs #107
Refs CryptOS-PKI/cryptos-manager#182
Verification
How this was verified
npm ci --ignore-scripts && npm run buildsucceeds with no broken-link warnings (onBrokenLinks: 'warn'indocusaurus.config.ts, matchingjob-build.yaml).npm run typecheckpasses. Grepped the repo afterward for "release asset", "manifest/release", "Release downloads" andghcr.io/cryptos-pki: no hits left indocs/orREADME.md.