Skip to content

chore: version packages - #365

Merged
cameronapak merged 1 commit into
mainfrom
changeset-release/main
Aug 27, 2026
Merged

chore: version packages#365
cameronapak merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

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-react-hooks@2.12.0

Minor Changes

  • c55f690: Data hooks now cache reads with TanStack Query: revisiting previously fetched content (chapters, verses, versions, highlights) renders instantly from an in-memory cache and revalidates in the background instead of blanking and refetching. Two components reading the same thing now share one request. Public hook APIs are unchanged and no new providers or peer installs are required — @tanstack/react-query ships as a direct dependency of the hooks package with a private QueryClient inside YouVersionProvider. Cache entries are keyed by provider config, including additionalHeaders, so two header sets never share a response. Account-scoped queries (highlights) are keyed per user, so one account can never see another account's cached data — while the signed-in account is still resolving, or while a live access token disagrees with a signed-out session, useHighlights holds off fetching rather than sharing a cache entry. Returning to the tab no longer refetches; mounting, changing what you are reading, and refetch() still do. A read that failed while the network was down fetches again on its own once the connection returns. useOrganizations shares that cache too, keyed per organization exactly as useOrganization keys it, so a list of versions that share publishers costs one request per publisher and reopening a picker renders them from cache. The cache is memory-only and never persisted.

Patch Changes

  • 1f258fa: Sign-in no longer fails when the token endpoint returns expires_in as a string. Callback failures are logged in development so a failed exchange is visible in the console.
  • Updated dependencies [1f258fa]
    • @youversion/platform-core@2.12.0

@youversion/platform-core@2.12.0

Patch Changes

  • 1f258fa: Sign-in no longer fails when the token endpoint returns expires_in as a string. Callback failures are logged in development so a failed exchange is visible in the console.

@youversion/platform-react-ui@2.12.0

Patch Changes

  • 22c36dd: Sync localization from platform-localization (032e300): add Serbian (sr); update 43 keys in af, zh.
  • c55f690: Data hooks now cache reads with TanStack Query: revisiting previously fetched content (chapters, verses, versions, highlights) renders instantly from an in-memory cache and revalidates in the background instead of blanking and refetching. Two components reading the same thing now share one request. Public hook APIs are unchanged and no new providers or peer installs are required — @tanstack/react-query ships as a direct dependency of the hooks package with a private QueryClient inside YouVersionProvider. Cache entries are keyed by provider config, including additionalHeaders, so two header sets never share a response. Account-scoped queries (highlights) are keyed per user, so one account can never see another account's cached data — while the signed-in account is still resolving, or while a live access token disagrees with a signed-out session, useHighlights holds off fetching rather than sharing a cache entry. Returning to the tab no longer refetches; mounting, changing what you are reading, and refetch() still do. A read that failed while the network was down fetches again on its own once the connection returns. useOrganizations shares that cache too, keyed per organization exactly as useOrganization keys it, so a list of versions that share publishers costs one request per publisher and reopening a picker renders them from cache. The cache is memory-only and never persisted.
  • Updated dependencies [1f258fa]
  • Updated dependencies [c55f690]
    • @youversion/platform-core@2.12.0
    • @youversion/platform-react-hooks@2.12.0

Greptile Summary

The PR prepares the monorepo’s synchronized 2.12.0 release.

  • Bumps core, hooks, and UI packages from 2.11.0 to 2.12.0.
  • Moves three consumed changesets into the corresponding package changelogs.
  • Records propagated internal-package updates for hooks and UI.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
packages/core/package.json Bumps the core package to 2.12.0, matching every other publishable package.
packages/hooks/package.json Bumps the hooks package to 2.12.0 while retaining workspace-linked internal dependencies.
packages/ui/package.json Bumps the UI package to 2.12.0, preserving unified monorepo versioning.
packages/core/CHANGELOG.md Records the consumed authentication patch for the 2.12.0 release.
packages/hooks/CHANGELOG.md Records the caching enhancement, authentication patch, and propagated core update.
packages/ui/CHANGELOG.md Records localization and caching changes plus propagated core and hooks updates.

Reviews (3): Last reviewed commit: "chore: version packages" | Re-trigger Greptile

Context used:

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 6f8a8fc to 4aba989 Compare August 27, 2026 16:19
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 4aba989 to c8d53de Compare August 27, 2026 16:57
@cameronapak
cameronapak merged commit e580502 into main Aug 27, 2026
14 checks passed
@cameronapak
cameronapak deleted the changeset-release/main branch August 27, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant