release: v0.1.1215 - #3472
Merged
Merged
Conversation
kojiwakayama
enabled auto-merge
August 8, 2026 12:05
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe release version changed from ChangesVersion update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
This was referenced Aug 8, 2026
Merged
Merged
Merged
Merged
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.
Carries the CSP reporting endpoint and the project-less-domain fix to production.
/_vf/csp-report, and the endpoint records it. Until now the report-only floor did neither job: it does not enforce, so it protected nothing, and with no reporting endpoint the violations it named reached only whoever happened to open devtools. This is what makes theVERYFRONT_CSP_ENFORCEdecision evidence-based instead of a repeat of fix(modules,security,cli): unblock hydration and cut v0.1.1206 #3417. The endpoint is exempt fromsecurity.authandsecurity.csrf, without which any project using either would have advertised a reporting endpoint that answered 401/403 and collected nothing.staging.veryfront.comandpreview.veryfront.comanswered 502 "Missing project context" wheredevelopment.veryfront.comanswered 404 for the identical condition. They match the environment-root branch inparseProjectDomainand were forwarded withx-project-slug: "". Now all three answer 404. Local project-less hosts keep reaching the project chooser.load_skillis availability-gated.Delivery is unchanged: still report-only for projects that declared no policy, still enforced for those that did.
VERYFRONT_CSP_ENFORCEis untouched.Once merged this dispatches
veryfront-code-released; the veryfront-server promotion PR follows.Summary by CodeRabbit