fix(release): update package name to align to SDK naming#24
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "name": "@youversion/platform-sdk-reactnative", | ||
| "name": "@youversion/platform-react-native", | ||
| "version": "0.7.1", |
There was a problem hiding this comment.
Update docs and example imports to new package name
The package was renamed to @youversion/platform-react-native, but the rest of the repo still instructs and imports @youversion/platform-sdk-reactnative (e.g., README.md install commands around lines 40–64 and example/metro.config.js line 22), so anyone following the README or running the example against the published package will hit module-not-found errors because the import specifier no longer matches the published name. Please align the documentation, example imports, and alias mappings to the new package name so consumers can install and run without resolution failures.
Useful? React with 👍 / 👎.
|
🎉 This PR is included in version 0.7.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Switching package name to match NPM convention (thank you @davidfedor for the callout)
Type of Change
feat:New feature (non-breaking change which adds functionality)fix:Bug fix (non-breaking change which fixes an issue)docs:Documentation updaterefactor:Code refactoring (no functional changes)perf:Performance improvementtest:Test additions or updatesbuild:Build system or dependency changesci:CI configuration changeschore:Other changes (maintenance, etc.)