Conversation
…on policy) Documents how catalog packages are versioned and how we handle updates to the underlying project: - two decoupled version numbers (upstream image pin vs our package.json bundle semver) - the validator-enforced image-pinning rule (immutable tag or @sha256 digest; prefer tag + digest for the project container) - bump-by-impact-on-the-Hola-user semver (we translate, not mirror, upstream) - what to do when the project releases (pin + infra + VM-test the upgrade path + bump) - the upgrade-hazard summary (forward-only/no-downgrade, no-version-skip, bundled- datastore major bumps, back-up-first) pending the structured metadata in try-hola/hola#284; tracked for the existing bundles in #45 Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Documents the versioning & update policy we'd been treating as tribal knowledge.
What's covered
compose.yamlvs our bundle version inpackage.json(the OCI tag + catalog version).build-catalog.shreadspackage.json.@sha256:digest; floating tags rejected) and why the project container should be tag + digest.postgres16→17 footgun), back-up-first — pending the structured metadata in Safe stateful app upgrades: migration signaling, version-skip guards, pre-upgrade snapshots & data-aware rollback hola#284.Related
🤖 Generated with Claude Code