chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@youversion/platform-core@2.3.0

Minor Changes

• d6ab2d5: Fix HighlightsClient to match the live highlights API contract. The client previously sent requests the API rejects on every call (401/400), so highlights could never be fetched, created, or deleted.

  • Auth token is now sent as an Authorization: Bearer <token> header instead of a lat query parameter
  • Query/body fields now use the API's bible_id naming on the wire (the SDK keeps version_id in its public types and maps at the boundary)
  • createHighlight now sends the required { request_id, highlight: { ... } } envelope (request_id is a unique per-request id the API requires)
  • getHighlights now requires version_id and passage_id (verse or chapter USFM), and deleteHighlight requires version_id, matching the API's required parameters; useHighlights options are updated accordingly
  • getHighlights now treats a 204 (no highlights for the passage) as an empty collection instead of throwing
  • createHighlight normalizes color to lowercase before sending, since the API accepts lowercase hex only
  • Added getRecentColors() (GET /v1/highlights/recent-colors) to HighlightsClient and exposed it from useHighlights for building color pickers
  • API responses are validated with Zod and mapped from the wire shape

• 683c123: Allow requesting YouVersion data-exchange permissions (e.g. highlights) at sign-in. These are intentionally not OIDC scopes: they ride alongside the standard scope param as repeatable requested_permissions[] query params on the authorize URL and are authorized via a separate per-app ACL rather than the token's scope claim.

  • YouVersionAPIUsers.signIn(redirectURL, scopes?, permissions?) and the underlying PKCE authorization request builder now accept a permissions array typed as SignInWithYouVersionPermissionValues[].
  • useYVAuth().signIn({ permissions }) forwards them from React.
  • <YouVersionAuthButton permissions={['highlights']} /> requests them from the sign-in button.

  Scopes and permissions are separate arguments; existing calls that only pass scopes are unaffected.

@youversion/platform-react-hooks@2.3.0

Minor Changes

• d6ab2d5: Fix HighlightsClient to match the live highlights API contract. The client previously sent requests the API rejects on every call (401/400), so highlights could never be fetched, created, or deleted.

  • Auth token is now sent as an Authorization: Bearer <token> header instead of a lat query parameter
  • Query/body fields now use the API's bible_id naming on the wire (the SDK keeps version_id in its public types and maps at the boundary)
  • createHighlight now sends the required { request_id, highlight: { ... } } envelope (request_id is a unique per-request id the API requires)
  • getHighlights now requires version_id and passage_id (verse or chapter USFM), and deleteHighlight requires version_id, matching the API's required parameters; useHighlights options are updated accordingly
  • getHighlights now treats a 204 (no highlights for the passage) as an empty collection instead of throwing
  • createHighlight normalizes color to lowercase before sending, since the API accepts lowercase hex only
  • Added getRecentColors() (GET /v1/highlights/recent-colors) to HighlightsClient and exposed it from useHighlights for building color pickers
  • API responses are validated with Zod and mapped from the wire shape

• ab38fb5: Surface a clear error when YouVersionProvider is given a missing or empty appKey instead of rendering a blank page. The UI provider now renders a styled "Missing app key" message, and the hooks provider throws a descriptive error for hooks-only consumers.

• 683c123: Allow requesting YouVersion data-exchange permissions (e.g. highlights) at sign-in. These are intentionally not OIDC scopes: they ride alongside the standard scope param as repeatable requested_permissions[] query params on the authorize URL and are authorized via a separate per-app ACL rather than the token's scope claim.

  • YouVersionAPIUsers.signIn(redirectURL, scopes?, permissions?) and the underlying PKCE authorization request builder now accept a permissions array typed as SignInWithYouVersionPermissionValues[].
  • useYVAuth().signIn({ permissions }) forwards them from React.
  • <YouVersionAuthButton permissions={['highlights']} /> requests them from the sign-in button.

  Scopes and permissions are separate arguments; existing calls that only pass scopes are unaffected.

Patch Changes

• Updated dependencies [d6ab2d5]
• Updated dependencies [683c123]
  • @youversion/platform-core@2.3.0

@youversion/platform-react-ui@2.3.0

Minor Changes

• ab38fb5: Surface a clear error when YouVersionProvider is given a missing or empty appKey instead of rendering a blank page. The UI provider now renders a styled "Missing app key" message, and the hooks provider throws a descriptive error for hooks-only consumers.

• 683c123: Allow requesting YouVersion data-exchange permissions (e.g. highlights) at sign-in. These are intentionally not OIDC scopes: they ride alongside the standard scope param as repeatable requested_permissions[] query params on the authorize URL and are authorized via a separate per-app ACL rather than the token's scope claim.

  • YouVersionAPIUsers.signIn(redirectURL, scopes?, permissions?) and the underlying PKCE authorization request builder now accept a permissions array typed as SignInWithYouVersionPermissionValues[].
  • useYVAuth().signIn({ permissions }) forwards them from React.
  • <YouVersionAuthButton permissions={['highlights']} /> requests them from the sign-in button.

  Scopes and permissions are separate arguments; existing calls that only pass scopes are unaffected.

• af37b90: Add a verse action popover to BibleReader. Tapping verses selects them (shown with an underline) and opens a popover anchored to the last-selected verse with five highlight colors, Copy, and Share. Highlights apply a translucent fill, persist to localStorage per Bible version (shaped like the future highlight API), and can be removed individually. Copy/Share output mirrors bible.com formatting: the verse text in curly quotes, gaps in a non-contiguous selection joined with ..., followed by the Book Chapter:verses VERSION reference. Share uses the Web Share API and falls back to copying where it isn't available.

  BibleReader also accepts optional onCopy / onShare props. When provided, they receive the structured selection payload and suppress the default Web Share / clipboard flow, so React Native / Expo hosts can forward it across the native bridge (mirrors VerseOfTheDay's onShare).

  Note: BibleTextViewProps.highlightedVerses changed from Record<number, boolean> to Record<number, string> (verse number → highlight hex). This prop was never wired into shipped usage, so no released consumer is affected; the bump stays minor.

Patch Changes

• Updated dependencies [d6ab2d5]
• Updated dependencies [ab38fb5]
• Updated dependencies [683c123]
  • @youversion/platform-core@2.3.0
  • @youversion/platform-react-hooks@2.3.0

Greptile Summary

Automated Changesets release PR bumping all three packages (platform-core, platform-react-hooks, platform-react-ui) from 2.2.0 to 2.3.0 in lockstep, satisfying the unified versioning requirement. Changeset source files are deleted as part of the release consumption.

• platform-core & platform-react-hooks 2.3.0: Fixes HighlightsClient to match the live API contract (Bearer auth header, correct field names, request_id envelope, 204 handling, lowercase color normalization), adds getRecentColors(), and introduces a permissions parameter to the sign-in flow for data-exchange scopes.
• platform-react-hooks 2.3.0 (additional): Surfaces a clear error when YouVersionProvider receives a missing or empty appKey.
• platform-react-ui 2.3.0: Adds the verse action popover to BibleReader (highlight colors, Copy, Share via Web Share API), the missing appKey UI error state, and the permissions sign-in button prop.

Confidence Score: 5/5

Safe to merge — purely automated version management with no code changes.

All three packages are bumped uniformly to 2.3.0, satisfying the unified versioning rule. The diff contains only changelog additions and version field updates in package.json files; the actual feature code was already reviewed and merged into main via the individual changeset PRs. No logic, configuration, or dependency wiring is changed here.

No files require special attention — all changes are generated by the Changesets action.

Important Files Changed

Filename	Overview
packages/core/package.json	Version bumped from 2.2.0 to 2.3.0; no other changes
packages/hooks/package.json	Version bumped from 2.2.0 to 2.3.0; no other changes
packages/ui/package.json	Version bumped from 2.2.0 to 2.3.0; no other changes
packages/core/CHANGELOG.md	2.3.0 changelog added: HighlightsClient API contract fix and permissions support
packages/hooks/CHANGELOG.md	2.3.0 changelog added: highlights fix, missing app key error, and permissions support
packages/ui/CHANGELOG.md	2.3.0 changelog added: missing app key error, permissions support, and verse action popover

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    CS1[".changeset/fix-highlights-api-contract.md"] -->|consumed| REL
    CS2[".changeset/missing-app-key-message.md"] -->|consumed| REL
    CS3[".changeset/request-highlights-permission.md"] -->|consumed| REL
    CS4[".changeset/verse-action-popover.md"] -->|consumed| REL

    REL["Changesets Release Action"] --> CORE["@youversion/platform-core\n2.2.0 → 2.3.0"]
    REL --> HOOKS["@youversion/platform-react-hooks\n2.2.0 → 2.3.0"]
    REL --> UI["@youversion/platform-react-ui\n2.2.0 → 2.3.0"]

    CORE -->|workspace:*| HOOKS
    CORE -->|workspace:*| UI
    HOOKS -->|workspace:*| UI

    UI -->|merge triggers| NPM["npm publish (all 3 packages)"]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    CS1[".changeset/fix-highlights-api-contract.md"] -->|consumed| REL
    CS2[".changeset/missing-app-key-message.md"] -->|consumed| REL
    CS3[".changeset/request-highlights-permission.md"] -->|consumed| REL
    CS4[".changeset/verse-action-popover.md"] -->|consumed| REL

    REL["Changesets Release Action"] --> CORE["@youversion/platform-core\n2.2.0 → 2.3.0"]
    REL --> HOOKS["@youversion/platform-react-hooks\n2.2.0 → 2.3.0"]
    REL --> UI["@youversion/platform-react-ui\n2.2.0 → 2.3.0"]

    CORE -->|workspace:*| HOOKS
    CORE -->|workspace:*| UI
    HOOKS -->|workspace:*| UI

    UI -->|merge triggers| NPM["npm publish (all 3 packages)"]

Loading

_{Reviews (5): Last reviewed commit: "chore: version packages" | Re-trigger Greptile}

Context used:

• Rule used - Unified versioning: All packages must maintain exa... (source)