🦋 New version release - #88
Merged
Merged
Conversation
brentrager
force-pushed
the
changeset-release/main
branch
from
August 15, 2026 19:40
fa2bf62 to
58e612d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@smooai/observability@0.17.0
Minor Changes
7aecf45: TypeScript, Go, Python and .NET bootstraps now report whether they are actually
EXPORTING, not just whether they ran, and warn loudly when no OTLP endpoint is
configured — the same fix already landed for Rust.
installed/Installedkept its old meaning (bootstrap ran) and now says sohonestly in its doc comment; the new
exporting/Exportinganswers thequestion that actually matters: does telemetry have anywhere to go. In TS and
Python the no-endpoint case is worse than a no-op — the OTel exporters fall back
to
http://localhost:4318and retry into the void forever.