feat: React Native SDK update for version 0.27.1

[ChiragAgg5k]

This PR contains updates to the React Native SDK for version 0.27.1.

[greptile-apps]

Greptile Summary

This is a patch-version release (0.27.0 → 0.27.1) that primarily fixes a missing files field in package.json which, when absent, would cause the full repository source (including src/, node_modules/, dev config files, etc.) to be published to npm rather than only the built artifacts. The fix is minimal and correct — "files": ["dist", "types"] aligns with the existing main/module/types export paths, and package.json itself is always included by npm automatically.

Key changes:

• package.json: Added "files": ["dist", "types"] to scope npm publishes to compiled output only; version bumped to 0.27.1
• src/client.ts: Updated the x-sdk-version header to 0.27.1
• CHANGELOG.md: Documented the fix under a new 0.27.1 section
• package-lock.json: Version bumped, but also contains significant structural changes from peer dependency deduplication — worth confirming this re-generation was intentional

Confidence Score: 5/5

Safe to merge — the core fix is correct and low-risk; the lock file churn is a minor concern worth acknowledging but does not block the release.

All substantive code changes are a straightforward version bump and a missing files field fix. The only flag is unintended lock file regeneration affecting peer dependencies, which is a P2 style/hygiene concern and does not affect runtime correctness or the SDK's direct consumers.

package-lock.json — large structural changes beyond the version bump warrant a quick confirmation that the lock file was intentionally regenerated.

Important Files Changed

Filename	Overview
package.json	Version bumped from 0.27.0 to 0.27.1; added files field restricting npm publishes to dist and types directories only
src/client.ts	Updated x-sdk-version header from 0.27.0 to 0.27.1 to match the new release version
CHANGELOG.md	Added 0.27.1 entry documenting the files field addition in package.json
package-lock.json	Version bumped to 0.27.1; lock file was regenerated, flattening many previously nested @expo/* peer dependency overrides and removing "peer": true from @babel/traverse

Comments Outside Diff (1)

1. package-lock.json, line 1484-1490 (link)

   Unintended lock file regeneration

   The package-lock.json changes go well beyond a version bump. Several peer dependency entries (primarily under @expo/cli, @expo/config-plugins, @expo/config, @expo/fingerprint, and others) that previously appeared as nested node_modules overrides have been removed, and @babel/traverse had its "peer": true marker removed. This indicates npm install was re-run in an environment that resolved peer dependency deduplication differently.

   While these entries are all "peer": true dependencies (so they don't affect the SDK's direct runtime), a large unexpected lockfile churn makes it harder to audit the exact dependency tree and could introduce subtle compatibility differences when consumers install the package.

   It's worth confirming whether this regeneration was intentional and that the resulting resolved versions are still consistent with what is expected for the expo and @react-native ecosystem versions this SDK targets.

_{Reviews (1): Last reviewed commit: "chore: update React Native SDK to 0.27.1" | Re-trigger Greptile}

[ChiragAgg5k]

Fixing conflicts on dev directly instead