feat: prepare Mesh 0.2.0 beta source - #33
Draft
dhawal-ss wants to merge 3 commits into
Draft
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.
Scope
Integrates the completed Mesh 0.2.0 public-beta source hardening tranche. Current exact head:
ec405614448eac9874f4be714efe83abd8fa0522.Verified
1.30.4-alpineand LiveKit1.13.5pass the unchanged fixable-high container policyFail-closed release blockers
The protected security evidence manifest remains red because current compatible upstream images for Caddy, Synapse, PostgreSQL, and lk-jwt-service still contain fixable high or critical vulnerabilities. No exception or severity reduction has been added. This PR must remain draft and must not advance
mainuntil compatible upstream rebuilds or separately approved patched derivatives clear the existing policy.Release boundary
This PR does not tag, sign, deploy, publish, or promote a release. The readiness ledger, signed Windows candidate, 54-case R2 campaign, provider/operations/legal evidence, and manual accessibility evidence remain separate required gates. Voice and macOS/Linux remain unavailable pending R3/R4 evidence.