Publish a package

Publish version 2.3.0 of the client SDK to the public registry and tag the repository release. Ensure the package metadata lists the new CHANGELOG entries, the CI artifacts include the compiled binaries for Linux and macOS, and notify the integrations channel after the publish is complete. Do a final sanity install from a fresh environment before announcing.

Before I publish this SDK, make the package approval-ready: surface the breaking changes at the top of the release notes, make the semver rationale and migration steps findable, confirm the compiled artifacts match the checksums in the release, and flag anything that would make our platform or enterprise customers hesitate to upgrade.

The publish pipeline succeeded and artifacts uploaded, but two downstream teams told me their integration tests failed against 2.3.0. I don’t know if it’s a packaging issue, a real breaking change we missed, or a misconfiguration in their test. Which quick diagnostics should I run first to isolate packaging from API breakage, who on the integrations teams must I pull in immediately, and what’s the stop-gap rollback or mitigation I should trigger if this is a real breaking change?

Across six releases this year we’ve had three urgent rollbacks due to packaging mistakes, missing artifacts, or unnoticed breaking changes. Where are we repeatedly failing—release signoff, CI checks, or dependency validation—and what single habit will prevent most of these emergencies going forward? Specify the check, who must own it, and a metric to prove it’s working.