chore: reconcile upstream v1.9.7 - #11
Merged
Merged
Conversation
This was referenced Aug 26, 2026
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.
Summary
mainmirror to upstream tagv1.9.7(d7b95aa5c8a7584b103eb35a48238c489baa79dd)growthpath-mailUpstream and migration review
The complete v1.9.7 delta from v1.9.6 is one commit and two files: the already-carried one-line BullMQ-safe campaign job ID plus its focused unit test. There are no dependency, configuration, or Prisma migration changes. The campaign service and test now match v1.9.7 exactly.
GrowthPath continues to carry these fork concerns intentionally:
The historical local BullMQ commit remains in immutable production ancestry, but it contributes no delta beyond upstream after this merge.
Verification
pnpm --filter=web typecheckpnpm test:web:all: unit, tRPC, API, and integration suites passed; all 41 migrations applied to disposable Postgressha256:1cb7639a370df19d6f9379f142b9f332624d08cdeea7b...)growthpath-mail: no findingspre-v1.9.7(e33e5854-5d90-4de8-9ce5-0e9875cd8568) created at2026-08-26T11:47:20.716Z; PITR enabled, bucket wired, live recovery availableRelease effect
No new migration is introduced. Merging deploys
growthpath-mail; the existing pre-deploy command will confirm the 41-migration database is current, then Railway must pass/api/health. The live response will be checked against the exact merge SHA.Closes #7