chore: cut 0.0.370 - #1478
Merged
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
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.
Release 0.0.370.
Ships #1476 — a deployment somebody else can repeat: a rewritten
docs/deploy.md, two scripts, Traefik as overlay files, and a GitHub deploy behind an approval on theproductionenvironment.It also fixes four things found by putting the stack on a real host. The one that mattered:
apphad a 1 GB limit for four uvicorn workers, and a worker measures 460 MiB — so the shipped production ceiling OOM-killed the API as soon as all four were warm.And #1477, which stops
journey.specreloading over the write it was testing — four failures in nine runs, twice on branches that touched no application code.Verified: CI green on both merges,
make checkon the tree.