Publishing

Release process for @0xsequence/oms-react-native-sdk.

Only maintainers with npm publish access should publish. Publish from master after CI is green.

1. Choose The Version

Pre-release versions use 0.x.y-alpha.N, for example 0.1.0-alpha.2.

Check that the version is not already published:

npm view @0xsequence/oms-react-native-sdk@<version> version

An npm 404 means the version is available. If npm prints a version, choose a new version.

Update:

package.json version
CHANGELOG.md
native SDK references if they changed:
- android/build.gradle
- OmsClientReactNativeSdk.podspec
- README.md
- API.md

Install after editing package metadata:

yarn install

Commit the release changes before publishing.

Run the standard checks from a clean worktree:

git status --short
yarn lint
yarn typecheck
yarn test
yarn sdk-example build:android
yarn sdk-example build:ios

Do not publish if any command fails. If native SDK versions changed, confirm those versions are already available from Maven Central and CocoaPods.

Build the package and inspect what npm would publish:

yarn prepare
yarn npm publish --dry-run --access public --tag alpha

The dry run should include lib, src, android, ios, and OmsClientReactNativeSdk.podspec.

Confirm the npm account, then publish:

yarn npm whoami
yarn npm publish --access public --tag alpha

Use --tag alpha for alpha releases so prereleases do not become the default latest install.

Verify npm sees the published version:

npm view @0xsequence/oms-react-native-sdk@<version> version

If the package should become the default install later, move the npm dist-tag deliberately in a separate step.