Repository navigation
docs: complete 0.9.0 CHANGES with merged release fixes - #285
Merged
sciabarracom merged 1 commit intoNov 4, 2026
Merged
Conversation
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.
CHANGES stops at RC7 and omits the subsequent fixes already included in the 0.9.0 source pins. Append an unreleased 0.9.0 section with 19 entries covering 36 merged PRs across the platform repositories, while preserving the existing release history byte for byte.
The entries cover tenant authentication and isolation, IAM and Redis recovery, protected custom OPTIONS handlers, provisioning and SSO, builder hardening, Cron containment, setup readiness, component versions, licensing and integration checks. They retain the relevant limits: NetworkPolicies require an enforcing CNI, and Cron containment retains Allow concurrency without duplicate prevention or recovery of missed executions. Open, draft, superseded and unpublished work is excluded; the existing SSO backport entry is not duplicated.
Validation: checked each included code merge against the corresponding submodule pin at
d834957dcc72e61ac1a8daec9218758a39be432f; verified the approved diff and unchanged existing content; confirmed that the whitespace check reports no errors. Documentation-only change; no runtime files or submodule pins are changed. Rebuilt-image publication and release signatures were not assessed.Source PRs reviewed for the new entries