Skip to content

v0.2.11

Choose a tag to compare

@GGULBAE GGULBAE released this 03 Jul 02:42

Status: published to npm on July 2, 2026 at 08:49:37 UTC (17:49:37 KST), tagged as v0.2.11.

This docs-only patch corrects the README that is shown on the npm package page
after the 0.2.10 tarball shipped release-ready/pre-publish status text. It
keeps Android and iOS runtime behavior unchanged while publishing a new package
version whose packaged README reports the 0.2.11 published package state.

Goals

  • Publish a docs-only package version so the npm package page reflects the published state after 0.2.11 is released.
  • Remove stale 0.2.10 release-ready/pre-publish package-page status wording from the packaged README.
  • Keep Android runtime behavior, iOS runtime behavior, and the public TypeScript API unchanged.
  • Verify the 0.2.10 registry tarball README before preparation and the 0.2.11 registry tarball README after publish.
  • Keep the release dry-run packed README stale-status check and post-publish registry smoke flow in place.

Included

  • package.json version bump to 0.2.11.
  • README status, installation, release guidance, and registry smoke examples updated for the docs-only npm README correction.
  • README copy now describes 0.2.11 as a docs-only README correction while preserving the 0.2.10 runtime behavior surface.
  • Source-level tests and Android verification doctor expectations are updated for the 0.2.11 docs-only status.
  • Release dry-run packed README stale checks now reject the stale 0.2.10 release-ready/pre-publish snippets and old 0.2.10 package-page status snippets.
  • npm package publication under the latest dist-tag.
  • Git tag v0.2.11 and GitHub Release v0.2.11.

Not Included

  • Android or iOS runtime behavior changes.
  • Native code changes.
  • New public TypeScript API surface.
  • AVIF output, animated AVIF preservation, HEIC/HEIF output, iOS metadata preservation, cancellation, or progress support.

v0.2.10 Registry README Inspection

Before preparing this patch, the published 0.2.10 registry tarball README was
checked explicitly:

tmpdir=$(mktemp -d)
npm pack react-native-image-compression-kit@0.2.10 --pack-destination "$tmpdir"
tar -xOf "$tmpdir"/react-native-image-compression-kit-0.2.10.tgz package/README.md | rg -n 'Status: v0\.2\.10 release-ready|It has not been published to npm yet|latest published npm package remains `0\.2\.9`|v0\.2\.10 release-ready notes'
rm -rf "$tmpdir"

The inspection found Status: v0.2.10 release-ready, It has not been published to npm yet, the "latest published npm package remains 0.2.9"
wording, and v0.2.10 release-ready notes in the published 0.2.10 README.

Release Checklist

Before npm publish:

git status --short --branch
pnpm verify
pnpm example:typecheck
git diff --check
pnpm pack --dry-run
pnpm release:dry-run

After npm publish:

npm publish --tag latest
pnpm smoke:registry -- --version 0.2.11
git tag -a v0.2.11 -m "v0.2.11"
git push origin v0.2.11

The release dry run includes a packed README stale status check before the consumer smoke and publish dry run. Release promotion also requires GitHub Actions CI, Android Instrumentation, and iOS Validation to pass on the pushed release-ready commit. After npm publish, the registry smoke must confirm the real 0.2.11 tarball README no longer includes the stale 0.2.10 release-ready/pre-publish package-page status snippets.

Release commit validation before npm publish:

Completed after npm publish and GitHub Release creation:

  • npm publish --tag latest published react-native-image-compression-kit@0.2.11.
  • npm view react-native-image-compression-kit@0.2.11 version dist.tarball dist.integrity dist.shasum time.modified --json confirmed version 0.2.11, registry tarball URL, integrity sha512-JMBebCxcpwdiLspK8s8pIF8xIEpgqxWjO5BZEkBEoCdRp09wvqj8b3UXLczGqXSgcAZtTL+UuE2mF+nptKWDpw==, shasum e3c067a00949e93f29f80dee5eabfaaf4bf1fa72, and publish timestamp 2026-07-02T08:49:36.915Z.
  • npm view react-native-image-compression-kit dist-tags version --json confirmed latest dist-tag 0.2.11.
  • npm package: react-native-image-compression-kit@0.2.11
  • npm tarball: https://registry.npmjs.org/react-native-image-compression-kit/-/react-native-image-compression-kit-0.2.11.tgz
  • npm integrity: sha512-JMBebCxcpwdiLspK8s8pIF8xIEpgqxWjO5BZEkBEoCdRp09wvqj8b3UXLczGqXSgcAZtTL+UuE2mF+nptKWDpw==
  • npm shasum: e3c067a00949e93f29f80dee5eabfaaf4bf1fa72
  • Git tag: v0.2.11
  • GitHub Release: https://github.com/GGULBAE/react-native-image-compression-kit/releases/tag/v0.2.11.
  • Registry smoke confirmed 49 files, 46.4 kB package size, 204.3 kB unpacked size, clean npm install --ignore-scripts --legacy-peer-deps, and public TypeScript import/typecheck success.
  • Registry tarball README stale-status check passed for the 0.2.11 package-page status.