mcpField
O
otel-sdk-versions

otel-sdk-versions

github.com/ollygardenDevelopment117141 installsUpdated 2d ago
Repository

About otel-sdk-versions

A skill for looking up versions of OpenTelemetry SDKs, the Collector, and related components. It helps developers choose compatible dependencies using a bundled index as the default reference and official release sources for gaps.

Key features

  1. 01Look up SDK versions by language
  2. 02Check Collector and component versions
  3. 03Select versions based on compatibility
  4. 04Verify companion packages from releases

Use cases

  1. 01Choose an SDK version for a project
  2. 02Confirm component versions in a Collector build
  3. 03Find package versions missing from the index

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ollygarden/opentelemetry-agent-skills --skill otel-sdk-versions

After installing, type/otel-sdk-versionsin Claude Code to confirm it loaded.

Bundled filesreferences/generated/otel-version-index.md

Details

From the project README

OpenTelemetry SDK Versions

Workflow

  1. Open references/generated/otel-version-index.md.
  • the SDKs table has one primary SDK package per language; the Components table covers the Collector (core, contrib, distributions, builder), the configuration schema, semantic conventions, and Weaver
  • use the bundled tables as the default source of truth for what they cover
  • its "Versions last changed" date is the last day any row changed
  • offline, give each version with that date: "<version> as of <date>; a newer release may exist". Never call it the current latest
  1. Choose the version deliberately.
  • prefer the latest released version when it is compatible with the project
  • if the latest release is not compatible, choose the latest compatible version and state the compatibility reason explicitly
  • reuse that decision for the rest of the task unless the language, package, or constraints change
  1. Resolve companion packages from the release source.
  • if the task requires additional packages from the same ecosystem (exporters, instrumentations, resource detectors, Collector components), look up their versions from the release source — do not infer or reuse the primary package version
  • sub-packages within the same project often share a version line but not always; confirm each package individually
  • Collector components in one build must match the core release line its builder uses, which can trail core; see otel-collector-builder for manifest pinning
  1. Use the linked follow-up sources when needed.
  • use the Release Source or Release column to confirm the package, repo, or release notes
  • use the Setup Docs column for SDK setup guidance
  • use the Examples column for implementation references when examples are available
  1. Handle gaps explicitly.
  • if the requested language, package, or component is not in the bundled index, say that the index does not cover it
  • then fall back to the official release source and official docs for that package
  • do not assume an unreleased, prerelease, or incompatible version is acceptable without saying so

Comments

Markdown supported