release: v0.1.1216 - #3478
Merged
Merged
release: v0.1.1216#3478
Conversation
kojiwakayama
enabled auto-merge
August 8, 2026 18:32
|
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 project version was incremented from ChangesRelease version 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 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 fix that makes derived CSP origins actually work in production.
getAllSourceFilesanswers[]while its own file list is cold and warms asynchronously; every pod is cold for a content version on the first request after a release, and that emptiness was written to the per-content-version cache, which is by design never revisited. The release then served the bare floor for the life of the pod. Verified against a probe project: preview served the derived origins, production served none, from the same release and the same source.<available_skills>to the skill catalogue.After this deploys,
vf-csp-probe.production.veryfront.comshould carryhttps://images.unsplash.comandhttps://cdn.jsdelivr.netinimg-src. That is the check this whole line of work has been missing, and it stays as a standing regression probe.VERYFRONT_CSP_ENFORCEis untouched. It should not be flipped until this is live and that check passes — the derived origins that make enforcement survivable are not being served today.Summary by CodeRabbit