Skip to content

chore: reconcile upstream v1.9.7 - #11

Merged
vladbisceanu merged 2 commits into
growthpath-mailfrom
chore/7-upstream-v1.9.7
Aug 26, 2026
Merged

chore: reconcile upstream v1.9.7#11
vladbisceanu merged 2 commits into
growthpath-mailfrom
chore/7-upstream-v1.9.7

Conversation

@vladbisceanu

Copy link
Copy Markdown
Owner

Summary

  • advance the public main mirror to upstream tag v1.9.7 (d7b95aa5c8a7584b103eb35a48238c489baa79dd)
  • merge that tagged commit into growthpath-mail
  • replace the fork's equivalent BullMQ test implementation with upstream's version, leaving no duplicate production change or regression test

Upstream 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:

  • authenticated and bounded SNS callbacks
  • the AGPL source link
  • Railway build/runtime compatibility
  • self-hosted bootstrap and standalone Prisma runtime support
  • native service ownership and operator docs
  • readiness, production-image CI, and fail-fast migration hardening

The historical local BullMQ commit remains in immutable production ancestry, but it contributes no delta beyond upstream after this merge.

Verification

  • focused campaign service unit test: 1 passed
  • pnpm --filter=web typecheck
  • pnpm test:web:all: unit, tRPC, API, and integration suites passed; all 41 migrations applied to disposable Postgres
  • production Docker image built successfully (sha256:1cb7639a370df19d6f9379f142b9f332624d08cdeea7b...)
  • independent review against growthpath-mail: no findings
  • locked Railway backup pre-v1.9.7 (e33e5854-5d90-4de8-9ce5-0e9875cd8568) created at 2026-08-26T11:47:20.716Z; PITR enabled, bucket wired, live recovery available

Release 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

@vladbisceanu
vladbisceanu merged commit d1e6e5a into growthpath-mail Aug 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants