Repository navigation
Release Cockpit newsletter with verified Staging delivery and Next.js security fix - #215
Merged
Merged
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
github-actions
Bot
force-pushed
the
deploy/main-to-production
branch
from
October 10, 2026 12:39
b9eadbb to
4634d4f
Compare
github-actions
Bot
force-pushed
the
deploy/main-to-production
branch
from
October 10, 2026 13:36
4634d4f to
4f7e401
Compare
github-actions
Bot
force-pushed
the
deploy/main-to-production
branch
from
October 10, 2026 13:50
4f7e401 to
97535ba
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
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.
Production release verified on 10 October 2026. PR #215 is merged, and https://cockpit.start-berlin.com/newsletter serves commit f9603cb. Production pipeline passed all 479 tests, migrations, deployment promotion, commit verification and Inngest synchronization. Direct test delivery and a real one-recipient broadcast from Production reached the approved QA mailbox in Gmail's inbox; SPF, DKIM and DMARC pass. The broadcast records one delivery and zero bounces. Production upload, autosave, scheduling, cancellation and preference links were rechecked. No future QA send remains.
Cockpit gains a newsletter app for Growth: authors can compose and preview issues, upload images to Vercel Blob, send direct test emails, select existing Resend segments, schedule or cancel broadcasts, and inspect delivery analytics. Department heads, co-leads, Legal Board positions and admins also have access; inactive accounts are excluded.
Writing assistance is removed completely, including its server action, OpenAI SDK and environment variables. The Images and Writing help settings cards are removed. The redundant status strip below Email preview is removed as well. Image upload remains supported. Test emails resolve first-name placeholders with or without a fallback.
The release also carries the separate Next.js security fix: Next 16.3.8, patched Sharp/libheif, consistent preview dependencies and React Email 6.9.2. Referrals, existing Cockpit schemas, membership rules and Inngest functions are unchanged. The newsletter only adds migrations 0059 and 0060; both were generated from the schema and applied by the Staging pipeline.
Validation:
Final Staging pipeline: Run 38057133375. Build and all 479 tests, database migration step, domain commit verification and Inngest synchronization passed. The release branch has the identical file tree as Main commit 0ac1480. Production deployment and post-release checks are complete.
Deployment configuration is scoped to start-berlin/cockpit. Staging remains live. Production's newsletter mode is prepared as live with explicit operator approval; the authorized Production deployment is complete. Other preview branches remain sandbox. The existing Production workflow builds first, requires the Production gate for migrations, then publishes the new application.
The newsletter's default segment is still empty. Growth must choose the intended audience and preserve its consent before the first regular issue. Custom tracking DNS is incomplete; tested shared Resend tracking URLs work. The patched production dependency audit has no critical findings but retains existing moderate/high findings. The full audit additionally has two dev-tool critical findings outside this fix. Outlook rendering was not tested live.
Full review and migration hashes: Pre-release review. Additive tables can remain during an application rollback. Cancel any newly scheduled live broadcasts before rolling back.