docs: document posthog-js release flow - #4591
Open
dustinbyrne wants to merge 3 commits into
Open
Conversation
Contributor
📝 No Changeset FoundThis PR doesn't include a changeset. A changeset is required to release a new version. How to add a changesetRun this command and follow the prompts: pnpm changesetRemember: Never use |
Contributor
Replay incident risk checkThis diff touches code involved in past incidents. This is a heads-up, not a verdict: read the matched sections of INCIDENTS.md and answer their review questions before merging. For a judgment on whether this diff has the same failure mode, run the |
Contributor
|
Reviews (1): Last reviewed commit: "docs: document S3 release recovery" | Re-trigger Greptile |
Contributor
Contributor
|
Size Change: 0 B Total Size: 20.2 MB ℹ️ View Unchanged
|
turnipdabeets
approved these changes
Aug 21, 2026
turnipdabeets
left a comment
turnipdabeets
left a comment
Contributor
There was a problem hiding this comment.
LGMT, just a few suggestions
dustinbyrne
enabled auto-merge (squash)
August 25, 2026 18:59
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
2 participants
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.
Problem
RELEASING.mdstill described the old failure mode where npm could publish before the browser S3/CDN release failed. The release workflow now gates all coordinated npm publishing on successful US and EU browser uploads, and the protected recovery path was undocumented.Changes
This updates internal release tooling and documentation and does not require a package changeset.
Release info Sub-libraries affected
Libraries affected
Checklist
If releasing new changes
pnpm changesetto generate a changeset fileValidation
git diff --checkposthog-js@1.418.2representative assets in US and EUarray.jsresponses with the recovery workflow artifact🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Pi updated the release documentation and approval message based on the implemented workflows. Fresh builtin reviewers checked the operational instructions against the workflow and release tooling, confirmed earlier ambiguity in mismatch and verification guidance was addressed, and reviewed the final Block Kit payload with no actionable findings.