Mixpanel release branch #2
Open
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.
This is the branch used by Mixpanel to publish to NPM
changes are mostly focused around package.json and bare minimum build changes to allow us to release (this way we can sync the master fork easily without changing business logic and having import conflicts)
Updating release:
Make a PR to core rrweb, but if we absolutely need a change before they do a release (or our able to review or contribution), we can merge that into this release branch.
if there's any changes that are not in rrweb's release commit, run
npm run mixpanel-version
. this will bump the version detailed belowto release, run
npx yarn release
Versioning: Base upstream version + Mixpanel patch suffix
2.0.0-alpha.18 → 2.0.0-alpha.18.1
Each Mixpanel change increments the patch number
Automated via version bump script
Build Changes:
Vite replace transforms @rrweb/* → @mixpanel/* package names for scoped npm publishing
Disabled Rollup types in Vite due to aliasing conflicts