Skip to content

Release 1.21.0: send the environment as deployment.environment.name (runtime-node 1.17.0) - #59

Merged
sagnik11 merged 1 commit into
mainfrom
claude/deployment-environment-name
Nov 16, 2026
Merged

sagnik11 merged 1 commit into
mainfrom
claude/deployment-environment-name

Conversation

@sagnik11

@sagnik11 sagnik11 commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

OpenTelemetry's semantic conventions renamed the resource attribute deployment.environment to deployment.environment.name. Every Autter ingester reads both and prefers the new name (since v0.1), but Autter's own SDKs and docs still set the old one, which the monorepo's new observability gap finder (Plan 034 WP4) flags as deprecated in customers' code.

Changes

  • runtime-node (1.17.0): initAutterServer sends deployment.environment.name on spans and metrics; log records already did. npx @autter/runtime-node verify uses the new name too.
    • A value in OTEL_RESOURCE_ATTRIBUTES still wins under either name. The NodeSDK merges those values over the SDK's resource. A value under the old name is now also sent under the new one, so the SDK's own default doesn't override it. Before this change the two shared one key, so the user's value won simply by replacing it.
    • New helper environmentFromResourceAttributes() reads that value (trimmed and percent-decoded).
  • Python adapter (copied, not published):
    • The test-run environment and the compat.py verify test event use deployment.environment.name.
    • An environment the service sets, under either name, still wins and is left as set.
  • Docs, examples and the ingester README use the new name. The ingester's fallback to the old name and its old-name test fixtures are kept.
  • Release: runtime-node 1.17.0 and CHANGELOG 1.21.0. This is a behaviour change only for a collector of the user's own that reads deployment.environment from Autter's Node spans or from the Python adapter's test environment.

Tests (Windows)

  • runtime-node: 289 pass, 4 skipped. The environment test now checks the old-name override end to end against a local collector.
  • Python adapter (unittest discover -s adapters/python, pinned requirements): 109 pass, 1 skipped.

Release

After merge, tag v1.21.0. The Release workflow publishes only @autter/runtime-node@1.17.0; every other package keeps a version that is already on npm, so it is skipped.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

…runtime-node 1.17.0)

OpenTelemetry's semantic conventions renamed the resource attribute
deployment.environment to deployment.environment.name. Every Autter ingester
reads both and prefers the new name, but Autter's own SDKs and docs still set
the old one, which the monorepo's observability gap finder (Plan 034 WP4) now
flags as deprecated in customers' code.

- runtime-node: initAutterServer sends deployment.environment.name on spans
  and metrics (log records already did). A value in OTEL_RESOURCE_ATTRIBUTES
  still wins under either name: the NodeSDK merges those over the SDK's
  resource, and a value under the old name is now also sent under the new
  one, so it is not overridden by the SDK's own default. verify uses the new
  name. environmentFromResourceAttributes() reads it, percent-decoded.
- Python adapter: the test-run environment and the compat.py verify event use
  deployment.environment.name; an environment the service sets, under either
  name, still wins and is left as set.
- Docs, examples and the ingester README use the new name; the ingester's
  fallback to the old name and its old-name fixtures are kept.
- runtime-node 1.17.0, CHANGELOG 1.21.0. Behaviour change for a collector of
  the user's own that reads deployment.environment from Autter's Node spans.

Tests: runtime-node 289 pass, 4 skipped; Python adapter 109 pass, 1 skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sagnik11
sagnik11 merged commit 3d4d604 into main Nov 16, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant