sync: publish-aggregate writer from dev (#1300 + #1309)#1323
Merged
Conversation
… blobs (tier A + tier B) (#1309) Co-authored-by: Florent Tapponnier <contact@mobula.io>
Flotapponnier
force-pushed
the
sync/publish-aggregate-to-main
branch
from
July 22, 2026 23:28
d8ca2e3 to
25f0f9a
Compare
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
1 participant
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.
The CDN blob writer for /aggregate/*.json was on dev only. Production worker (built from main) had no writer → static CDN blobs went stale, spec edits didn't propagate through the read fast-path.
Cherry-picks:
Requires
AGGREGATE_OUTPUT_PATH=/state/aggregateenv var on the worker (already set on VPS).