chore: replace bolt.com domain with boltapp.com and bump version to 0.10.0 - #108
Merged
Merged
Conversation
….10.0 Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
davidminin
approved these changes
Jul 20, 2026
1 task
alanthai
added a commit
that referenced
this pull request
Jul 22, 2026
### Description Corrective release PR to actually publish the `boltapp.com` domain migration as `0.10.0`. **Background:** PR #108 migrated the domain and manually bumped `package.json` to `0.10.0`, but it merged as a `chore:` squash commit. Releases here are driven by `@release-it/conventional-changelog` (`bumpStrict: true`), where `chore` is hidden and triggers no version bump — so the release workflow logged "No new version to release" and skipped npm publish. The manual bump also broke the workflow's publish gate (`VERSION_BEFORE != VERSION_AFTER`), since `package.json` already read `0.10.0`. **This PR:** - Reverts `package.json` `0.10.0` → `0.9.11`, letting release-it own the version bump. - Merges with a `feat:` subject so release-it computes a minor bump `0.9.11 → 0.10.0` on merge, changing `package.json` and thus satisfying the publish gate. Plain `feat:` (no `!` / `BREAKING CHANGE`) is intentional — a breaking marker pre-1.0 risks a `1.0.0` bump; we want exactly `0.10.0`. No source/domain changes here — those already landed in #108. ### Testing - `yarn test` / `yarn typecheck` / `yarn lint` unaffected (only `package.json` version changes). Release behavior is verified by the `Release & Publish` workflow on merge: it should log `Version bumped: 0.9.11 → 0.10.0`, then build and publish `@boltpay/react-native@0.10.0`. ### Security Review - [x] I have considered and reviewed security implications of this PR and included the summary below. #### Security Impact Summary Version/release-metadata change only; no logic or data-handling changes. Publish still occurs via npm Trusted Publishing (OIDC) with provenance. Link to Devin session: https://app.devin.ai/sessions/57bf0ac839ea4ade9dcea0391d96df2c Requested by: @alanthai Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Global find-and-replace of the
bolt.comdomain withboltapp.comacross the SDK, plus a pre-1.0 minor version bump for this breaking change.bolt.comoccurrence (including subdomains likeconnect.bolt.com,api-sandbox.bolt.com,tokenizer.bolt.com,help.bolt.com,www.bolt.com, and thebolt@bolt.com/bolt-ci@bolt.comemails) with theboltapp.comequivalent across 16 files (src/,android/,ios/,README.md,.github/workflows/main-release.yml,package.json).package.jsonversion0.9.11→0.10.0.@boltpay/react-nativeand Java/Kotlin package pathscom.boltreactnativesdk(neither contains the literalbolt.com).No lockfile/
example/package.jsonversion change was needed —yarn.lockreferences the SDK as a workspace (@boltpay/react-native@workspace:., no pinned version) andexample/package.jsonhas its own unrelated0.0.1version.Testing
yarn test— 17 suites, 180 tests pass.yarn typecheck— clean.yarn lint— clean.grep -rIn 'bolt\.com'(excludingnode_modules/.git) — no matches remain.Security Review
Security Impact Summary
Domain-only string change. The SDK now points to
*.boltapp.comhosts (connect/api/tokenizer) instead of*.bolt.com. No logic, auth, or data-handling changes. Ensure the correspondingboltapp.comendpoints are live before releasing, since these URLs drive tokenization and checkout WebView loading.Link to Devin session: https://app.devin.ai/sessions/57bf0ac839ea4ade9dcea0391d96df2c
Requested by: @alanthai