@youversion/platform-react-native 0.7.2

package/.releaserc.json

@@ -0,0 +1,104 @@
+{
+  "branches": ["main"],
+  "tagFormat": "${version}",
+  "repositoryUrl": "git@github.com:youversion/platform-sdk-reactnative.git",
+  "plugins": [
+    [
+      "@semantic-release/commit-analyzer",
+      {
+        "preset": "conventionalcommits",
+        "releaseRules": [
+          { "type": "feat", "release": "minor" },
+          { "type": "fix", "release": "patch" },
+          { "type": "perf", "release": "patch" },
+          { "type": "revert", "release": "patch" },
+          { "type": "docs", "release": false },
+          { "type": "style", "release": false },
+          { "type": "chore", "release": false },
+          { "type": "refactor", "release": "patch" },
+          { "type": "test", "release": false },
+          { "type": "build", "release": false },
+          { "type": "ci", "release": false }
+        ],
+        "parserOpts": {
+          "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES", "BREAKING"]
+        }
+      }
+    ],
+    [
+      "@semantic-release/release-notes-generator",
+      {
+        "preset": "conventionalcommits",
+        "writerOpts": {
+          "commitsSort": ["subject", "scope"]
+        },
+        "presetConfig": {
+          "types": [
+            { "type": "feat", "section": "Features" },
+            { "type": "fix", "section": "Bug Fixes" },
+            { "type": "perf", "section": "Performance Improvements" },
+            { "type": "revert", "section": "Reverts" },
+            { "type": "docs", "section": "Documentation", "hidden": false },
+            { "type": "style", "section": "Styles", "hidden": true },
+            {
+              "type": "chore",
+              "section": "Miscellaneous Chores",
+              "hidden": true
+            },
+            { "type": "refactor", "section": "Code Refactoring" },
+            { "type": "test", "section": "Tests", "hidden": true },
+            { "type": "build", "section": "Build System", "hidden": true },
+            {
+              "type": "ci",
+              "section": "Continuous Integration",
+              "hidden": true
+            }
+          ]
+        }
+      }
+    ],
+    [
+      "@semantic-release/changelog",
+      {
+        "changelogFile": "CHANGELOG.md",
+        "changelogTitle": "# Changelog\n\nAll notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines."
+      }
+    ],
+    [
+      "@semantic-release/npm",
+      {
+        "npmPublish": true,
+        "tarballDir": "dist"
+      }
+    ],
+    [
+      "@semantic-release/exec",
+      {
+        "prepareCmd": "node scripts/sync-android-version.js ${nextRelease.version}"
+      }
+    ],
+    [
+      "@semantic-release/git",
+      {
+        "assets": [
+          "CHANGELOG.md",
+          "package.json",
+          "package-lock.json",
+          "android/build.gradle"
+        ],
+        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+      }
+    ],
+    [
+      "@semantic-release/github",
+      {
+        "assets": [
+          {
+            "path": "dist/*.tgz",
+            "label": "Distribution package"
+          }
+        ]
+      }
+    ]
+  ]
+}

package/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
+
+## <small>0.7.2 (2025-11-24)</small>
+
+* fix(release): update package name to align to SDK naming (#24) ([9d4a1d7](https://github.com/youversion/platform-sdk-reactnative/commit/9d4a1d7)), closes [#24](https://github.com/youversion/platform-sdk-reactnative/issues/24)
+* ci(release): simplify manual release steps, align to ci (#20) ([b6ddda6](https://github.com/youversion/platform-sdk-reactnative/commit/b6ddda6)), closes [#20](https://github.com/youversion/platform-sdk-reactnative/issues/20)
+
+## <small>0.7.1 (2025-11-20)</small>
+
+* fix(release): aligning package name to standard (#22) ([e096edb](https://github.com/youversion/platform-sdk-reactnative/commit/e096edb)), closes [#22](https://github.com/youversion/platform-sdk-reactnative/issues/22)
+
+## 0.7.0 (2025-11-20)
+
+* feat(docs): update example app language for publishing release (#21) ([2abf72d](https://github.com/youversion/platform-sdk-reactnative/commit/2abf72d)), closes [#21](https://github.com/youversion/platform-sdk-reactnative/issues/21)
+* chore: Update to use new `signIn` function (#6) ([136578f](https://github.com/youversion/platform-sdk-reactnative/commit/136578f)), closes [#6](https://github.com/youversion/platform-sdk-reactnative/issues/6)
+
+## 0.6.0 (2025-11-18)
+
+* fix(ci): change releaserc url to ssh to use deploy keys (#18) ([08ea4fb](https://github.com/youversion/platform-sdk-reactnative/commit/08ea4fb)), closes [#18](https://github.com/youversion/platform-sdk-reactnative/issues/18)
+* fix(ci): disable husky commitlint hook in ci (#14) ([b08d88c](https://github.com/youversion/platform-sdk-reactnative/commit/b08d88c)), closes [#14](https://github.com/youversion/platform-sdk-reactnative/issues/14)
+* fix(ci): remove huksy output from prepare step (#15) ([ab5efcc](https://github.com/youversion/platform-sdk-reactnative/commit/ab5efcc)), closes [#15](https://github.com/youversion/platform-sdk-reactnative/issues/15)
+* feat: add link to platform in example app (#13) ([a5d37cf](https://github.com/youversion/platform-sdk-reactnative/commit/a5d37cf)), closes [#13](https://github.com/youversion/platform-sdk-reactnative/issues/13)
+* chore: adjust token and commitlint # (#12) ([e3ca175](https://github.com/youversion/platform-sdk-reactnative/commit/e3ca175)), closes [#12](https://github.com/youversion/platform-sdk-reactnative/issues/12) [#9](https://github.com/youversion/platform-sdk-reactnative/issues/9)
+
+---
+
+**Note:** This changelog is automatically generated by [semantic-release](https://github.com/semantic-release/semantic-release) based on conventional commit messages. Manual edits to this file will be overwritten on the next release.

package/CONTRIBUTING.md

@@ -0,0 +1,319 @@
+# Contributing to YouVersion React Native SDK
+
+Thank you for your interest in contributing to the YouVersion React Native SDK! This document provides guidelines and instructions for contributing to this project.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [Development Setup](#development-setup)
+- [Conventional Commits](#conventional-commits)
+- [Pull Request Process](#pull-request-process)
+- [Code Style Guidelines](#code-style-guidelines)
+- [Testing Requirements](#testing-requirements)
+- [Release Process](#release-process)
+
+## Code of Conduct
+
+By participating in this project, you agree to maintain a respectful and collaborative environment. Please be kind and courteous to all contributors.
+
+## Getting Started
+
+1. **Fork the repository** on GitHub
+2. **Clone your fork** locally:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/platform-sdk-reactnative.git
+   cd platform-sdk-reactnative
+   ```
+3. **Install dependencies**:
+   ```bash
+   npm install
+   ```
+4. **Set up git hooks**:
+   ```bash
+   npx husky install
+   ```
+
+## Development Setup
+
+### Prerequisites
+
+- Node.js 20.x or later
+- npm 10.x or later
+- Xcode (for iOS development)
+- Android Studio (for Android development)
+
+### Available Scripts
+
+- `npm run build` - Build the module
+- `npm run clean` - Clean build artifacts
+- `npm run lint` - Run ESLint
+- `npm run test` - Run unit tests
+- `npm run typecheck` - Run TypeScript type checking
+- `npm run release:dry-run` - Test release process without publishing
+
+### Running the Example App
+
+```bash
+# iOS
+cd example
+npm run ios
+
+# Android
+cd example
+npm run android
+```
+
+## Conventional Commits
+
+This project uses [Conventional Commits](https://www.conventionalcommits.org/) to automate versioning and changelog generation. **All commit messages must follow this format.**
+
+### Commit Message Format
+
+```
+<type>(<scope>): <subject>
+
+[optional body]
+
+[optional footer]
+```
+
+### Commit Types
+
+- **feat**: A new feature (triggers MINOR version bump)
+- **fix**: A bug fix (triggers PATCH version bump)
+- **docs**: Documentation changes only
+- **style**: Code style changes (formatting, missing semicolons, etc.)
+- **refactor**: Code changes that neither fix bugs nor add features (triggers PATCH version bump)
+- **perf**: Performance improvements (triggers PATCH version bump)
+- **test**: Adding or updating tests
+- **build**: Changes to build system or dependencies
+- **ci**: CI configuration changes
+- **chore**: Other changes that don't modify src or test files
+- **revert**: Reverts a previous commit
+
+### Breaking Changes
+
+Breaking changes trigger a MAJOR version bump. Indicate breaking changes in one of two ways:
+
+1. Add `!` after the type/scope:
+   ```
+   feat!: remove deprecated API endpoint
+   ```
+
+2. Add `BREAKING CHANGE:` in the footer:
+   ```
+   feat: update authentication flow
+   
+   BREAKING CHANGE: The old auth token format is no longer supported.
+   Users must migrate to the new format.
+   ```
+
+### Commit Message Examples
+
+#### Good Examples ✅
+
+```bash
+# New feature
+feat(api): add support for Bible verse lookup
+
+# Bug fix
+fix(auth): resolve token refresh race condition
+
+# Documentation
+docs: update README with installation instructions
+
+# Breaking change
+feat(api)!: redesign Bible content API structure
+
+BREAKING CHANGE: The Bible content API now returns a different
+response structure. See migration guide for details.
+```
+
+#### Bad Examples ❌
+
+```bash
+# Missing type
+Update readme
+
+# Vague subject
+fix: fix bug
+
+# Subject too long
+feat: add new feature that does something really cool and amazing and changes everything
+
+# Wrong case
+Feat: Add feature
+```
+
+### Scope (Optional)
+
+The scope should specify the area of the codebase affected:
+
+- `api` - API changes
+- `auth` - Authentication related
+- `bible` - Bible content features
+- `ui` - UI components
+- `deps` - Dependency updates
+- `config` - Configuration changes
+
+### Commit Message Validation
+
+Commit messages are validated in two places:
+
+1. **Locally** - Via Husky git hook (blocks invalid commits)
+2. **In CI** - During pull request validation
+
+If your commit message doesn't follow the convention, you'll see an error like:
+
+```
+⧗   input: bad commit message
+✖   subject may not be empty [subject-empty]
+✖   type may not be empty [type-empty]
+```
+
+## Pull Request Process
+
+### Before Submitting a PR
+
+1. **Ensure all tests pass**: `npm test`
+2. **Run type checking**: `npm run typecheck`
+3. **Run linting**: `npm run lint`
+4. **Build successfully**: `npm run build`
+5. **Use conventional commits** for all commit messages
+
+### PR Submission
+
+1. **Create a branch** from `main`:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. **Make your changes** with conventional commits
+
+3. **Push to your fork**:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+4. **Open a Pull Request** against the `main` branch
+
+5. **Fill out the PR template** completely
+
+### PR Requirements
+
+- ✅ All CI checks must pass
+- ✅ Code must be reviewed by at least one maintainer
+- ✅ Conventional commit format required
+- ✅ Linear history (squash merge)
+- ✅ No merge conflicts
+
+### Breaking Changes in PRs
+
+If your PR contains breaking changes:
+
+- **Clearly mark it** in the PR title (e.g., `[BREAKING]`)
+- **Document the breaking change** in the PR description
+- **Provide migration instructions**
+- **Get additional review approval**
+
+## Code Style Guidelines
+
+### TypeScript
+
+- Use TypeScript for all source code
+- Prefer `interface` over `type` for object shapes
+- Use strict type checking (no `any` unless absolutely necessary)
+- Export public APIs explicitly
+
+### Naming Conventions
+
+- **Files**: camelCase (e.g., `bibleReader.ts`)
+- **Components**: PascalCase (e.g., `BibleReaderView`)
+- **Functions**: camelCase (e.g., `fetchBibleContent`)
+- **Constants**: UPPER_SNAKE_CASE (e.g., `API_BASE_URL`)
+
+### Code Organization
+
+- Keep files focused and single-purpose
+- Export public APIs from `index.ts`
+- Place tests in `__tests__` directories
+- Place mocks in `mocks/` directory
+
+### ESLint
+
+This project uses ESLint with Expo module scripts configuration. Run `npm run lint` to check your code.
+
+## Testing Requirements
+
+### Unit Tests
+
+- Write unit tests for all new features
+- Maintain or improve test coverage
+- Place tests in `src/__tests__/` with `.test.ts` or `.test.tsx` extension
+- Use descriptive test names
+
+### Test Structure
+
+```typescript
+describe('ComponentName', () => {
+  it('should do something specific', () => {
+    // Arrange
+    const input = 'test';
+    
+    // Act
+    const result = doSomething(input);
+    
+    // Assert
+    expect(result).toBe('expected');
+  });
+});
+```
+
+### Running Tests
+
+```bash
+# Run all tests
+npm test
+
+# Run tests in watch mode
+npm test -- --watch
+
+# Run tests with coverage
+npm test -- --coverage
+```
+
+## Release Process
+
+Releases are **fully automated** using semantic-release. You don't need to manually version or publish.
+
+### How Releases Work
+
+1. **PR is merged** to `main` with conventional commits
+2. **Semantic-release analyzes** commits to determine version bump
+3. **Version is bumped** automatically (in package.json, Android build.gradle)
+4. **CHANGELOG.md is updated** with release notes
+5. **Package is published** to npm
+6. **GitHub release is created** with release notes
+
+### Version Bump Rules
+
+- `feat:` commits → MINOR version bump (0.5.0 → 0.6.0)
+- `fix:` commits → PATCH version bump (0.5.0 → 0.5.1)
+- `BREAKING CHANGE:` → MAJOR version bump (0.5.0 → 1.0.0)
+- Other commit types → No release
+
+### Manual Release (Emergency Only)
+
+In rare cases where automation fails, see [RELEASING.md](./RELEASING.md) for manual release procedures.
+
+## Questions?
+
+If you have questions about contributing, please:
+
+1. Check the [README](./README.md)
+2. Read [RELEASING.md](./RELEASING.md)
+3. Open a discussion on GitHub
+4. Reach out to the maintainers
+
+Thank you for contributing! 🎉

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.