chore(release): 0.1.3

[Fiona2016]

Why

0.1.2 bumped the packages but not the native SdkVersion.swift / SdkVersion.kt, which feed _dd.sdk_version. The published 0.1.2 therefore reports 0.1.1 in its events while npm serves 0.1.2, so support reads the wrong version off an event. npm versions are immutable, so the correction is the next release.

No functional change since 0.1.2 — the custom endpoint fix it carries is unchanged.

Bump

All thirteen places the version is written: lerna.json, every packages/*/package.json, the generated packages/core/src/version.ts, and both native SdkVersion files. NATIVE_SDK_VERSIONS.md gains a 0.1.3 row; the native pins are unchanged (Android 0.5.0, iOS ~> 0.5).

example/ios/Podfile.lock is left alone. It still records 0.1.0 and was not touched by the 0.1.1 or 0.1.2 bumps either — it locks the example app, not a published artifact.

Checks

$ ./check-version-matches-tag.sh v0.1.3
  ok        lerna.json
  ... 13 files ...
Every declared version is 0.1.3.

That check is exactly what 0.1.2 would have failed. yarn test: 876 passed, 1 skipped, 0 failed.

Releasing

After this merges, tag the merge commit v0.1.3 and push it — that is what publishes now.