chore(release): 0.11.0-rc.8 - #473
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vck5KSX2CLxhohx14nb5Sh
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.
What's in it
Three
backup@1fixes from an end-to-end audit of the contract. The platform half of backup was already built; these are the gaps that made it not work, or not tell the truth about itself.DATABASE_IMAGE_FAMILIESwas missingpgautoupgrade— the Postgres image every catalog app but immich runs. guacamole, mealie, paperless-ngx and postiz therefore reportedrecognised: 0, which with participations declared renders asquiesced: the all-clear. The four apps that actually declare backup hooks were the four whose coverage was never judged.GETthe whole API. The capability table names capabilities only for mutating routes, so every read required none and the middleware skipped the check — the credential injected into a catalog container could read/api/deployments, another app's logs,/api/settingsand every job. Now closed by default.pg_dumpin every accepting app's data root — and those roots are what the next backup captures, so the stale dump rode into every later snapshot looking fresh. PlusContractRollup.activity, so the Backups page can say "has never announced a backup".Why an operator wants this one
If you run postiz, its
temporal-postgresis copied live on every backup and rc.7 renders the app asquiescedanyway. #470 makes that visible; postiz 2.1.0 in the catalog fixes it.Pairs with two catalog releases published today:
Verified
bun run typecheck·lint·test(1004 server + 360 web) ·build— green, re-run on the combinedmainbecause each PR's CI ran against an older base.🤖 Generated with Claude Code
https://claude.ai/code/session_01Vck5KSX2CLxhohx14nb5Sh