chore(release): bump version to 1.0.0 and rn 2.5.0

[glenn-klaviyo]

Summary

Bumps the Expo plugin 0.4.0 -> 1.0.0 (the Q2 major release) and re-pins the example app to the RN SDK release version.

Generated via ./bump-version.sh 1.0.0 plus one manual edit to the example's RN SDK pin.

Changelog

• Plugin version root package.json, example/package.json, example/app.config.js, iOS klaviyo-plugin-configuration.plist (klaviyo_sdk_plugin_version_override), plugin/withKlaviyoAndroid.ts (setStringResource), and tests/withKlaviyoAndroid.internal.test.ts assertions -> 1.0.0
• Example RN SDK pin example/package.json: klaviyo-react-native-sdk 2.3.0 -> 2.5.0

The Expo plugin does not pin native iOS/Android SDK versions directly; those come transitively through klaviyo-react-native-sdk, so the RN pin is the only dependency change.

Test plan

• npm install (root) + cd example && npm install regenerate lockfiles cleanly against RN 2.5.0
• npm run prepare (build) passes
• Example app prebuild + build on both platforms

Blocked on upstream publish

• Lockfiles are intentionally NOT regenerated in this PR: klaviyo-react-native-sdk 2.5.0 is not on npm yet, so npm install cannot resolve it. Once RN 2.5.0 publishes, run npm install (root) and cd example && npm install, then commit the updated lockfiles here.
• This is the last wrapper in the Q2 chain: it waits on RN 2.5.0 on npm, which in turn waits on iOS 5.4.0 + Android 4.5.0 being published.

Hold merge until RN 2.5.0 is published and the lockfiles are refreshed.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Released version 1.0.0 of the Expo integration.
  • Upgraded the Klaviyo React Native SDK to version 2.5.0.

• Tests

  • Updated Android integration checks to validate the new plugin version metadata.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 928fba34-2879-41ce-aa45-147847f684ad

📥 Commits

Reviewing files that changed from the base of the PR and between 08c7ce9 and b5dfbfa.

📒 Files selected for processing (6)

• example/app.config.js
• example/package.json
• ios/klaviyo-plugin-configuration.plist
• package.json
• plugin/withKlaviyoAndroid.ts
• tests/withKlaviyoAndroid.internal.test.ts

---

📝 Walkthrough

Walkthrough

The release version changes from 0.4.0 to 1.0.0 across package metadata and platform configuration. The example app upgrades klaviyo-react-native-sdk from 2.3.0 to 2.5.0. Android tests now expect the new plugin version.

Changes

Release Version Alignment

Layer / File(s)	Summary
Package and platform version updates package.json, example/app.config.js, example/package.json, ios/klaviyo-plugin-configuration.plist	Package metadata and platform configuration use version 1.0.0. The example app upgrades klaviyo-react-native-sdk to 2.5.0.
Android override and test updates plugin/withKlaviyoAndroid.ts, tests/withKlaviyoAndroid.internal.test.ts	The Android plugin writes version 1.0.0. Tests update normal, duplicate, and malformed resource expectations.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• klaviyo/klaviyo-expo-plugin#121: Both PRs update the Expo plugin for the 1.0.0 release and modify Android plugin code and tests.

Suggested labels: SDK Auto Integration

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the version bump to 1.0.0 and the React Native SDK update to 2.5.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch gb/bump-1.0.0

---

_{Comment @coderabbitai help to get the list of available commands.}

[belleklaviyo]

🚀 we're in the majors now!! lgtm pending the lock file generation when available