chore: release 0.7.4#533
Merged
Merged
Conversation
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.
What/Why?
Bumps the package version on
mainto 0.7.4 to match the published release.0.7.4was cut as a scoped hotfix from the0.7.3tag (0.7.4-stablebranch = 0.7.3 + the #527 iOS x86_64 simulator fix) and is already published to npm (latest). The fix itself is already onmainvia #531 — this PR only carries thepackage.jsonversion bump somainreflects the released version.0.7.3 → 0.7.4(cherry-pick of the release bump commit)Testing
0.7.4verified end-to-end from the npm registry in a clean consumer project:npm install react-native-enriched-markdown@0.7.4→pod install→ universal-simulator Release build succeeds (theiOS RaTeX mathdependency breaks x86_64 simulator builds in react-native-enriched-markdown >= 0.7 #527 scenario).PR Checklist