chore(release): 7.0.0#179
Merged
Merged
Conversation
Bumps to 7.0.0 to capture the Expo SDK 52 -> 55 breaking peer bumps from #161 that earlier failed publish runs lost track of. release-it should now publish 7.0.0 on next push to main.
This was referenced May 19, 2026
There was a problem hiding this comment.
Pull request overview
Manual release bump to 7.0.0, stamping the previously unreleased Expo SDK 55 / Reanimated 4 breaking peer-dep changes from #161 so the next publish workflow ships them under a major version rather than a computed patch.
Changes:
- Bump
packages/modal/package.jsonversion from6.0.6to7.0.0. - Rename
CHANGELOG.mdUnreleasedheading to7.0.0 (2026-05-19).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/modal/package.json | Version bump to 7.0.0 for the breaking peer-dep release. |
| packages/modal/CHANGELOG.md | Promotes the Unreleased section to the dated 7.0.0 release heading. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
auto-merge was automatically disabled
May 19, 2026 07:29
Pull request was converted to draft
4 tasks
GSTJ
added a commit
that referenced
this pull request
May 19, 2026
## Summary Two post-7.0.1 ship issues, observed in CI runs after #179 merged: 1. **🚀 Publish step succeeds with `npm publish`** but release-it then fails pushing the version-bump commit + tag back to main: `GH013: Repository rule violations found for refs/heads/main` (`GITHUB_TOKEN` can't bypass branch protection). Switch the checkout to `secrets.GH_PAT` so release-it's git push goes through. 2. **📚 Docs workflow** finishes in 5s and then errors with `tar: packages/modal/docs: Cannot open: No such file or directory`. Cause: turbo's `docs` task only declares `node_modules/.cache/docs.json` as an output, so on cache hit turbo doesn't restore the generated `docs/` directory. Add `docs/**` to the task outputs. Both issues are pre-existing in the workflows but only surfaced now that the Publish workflow actually gets past pnpm setup + npm auth. ## Test plan - [x] `pnpm typecheck` green - [ ] Branch Checkup green on this PR - [ ] After merge: 🚀 Publish workflow on main reaches end of release-it step without GH013 error - [ ] After merge: 📚 Docs workflow uploads non-empty artifact
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
react-native-magic-modalfrom6.0.6to7.0.0Unreleasedheading inCHANGELOG.mdto7.0.0 (2026-05-19)Why a manual bump?
The original
feat!: bump Expo SDK 52 -> 55lived in the squashed history of #161, but the most recent commits onmainareci(release):/chore:style, so release-it's conventional-changelog plugin computed apatch(6.0.6 → 6.0.7). This PR pre-stamps7.0.0so the next publish workflow run picks it up verbatim.Intentionally no
feat!:/BREAKING CHANGE:marker on the commit — that would cause release-it to compound the bump again.Test plan
package.jsonversion reads7.0.0CHANGELOG.mdtop section is## 7.0.0 (2026-05-19)with the BREAKING CHANGES intact7.0.0(gated onNPM_TOKENrotation — see follow-up issue)