chore: drop stale version anchor in otelconventions-lint registry comment#83
Conversation
…omment Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
There was a problem hiding this comment.
Pull request overview
This PR keeps the otelconventions-lint registry maintenance guidance accurate by removing a stale hard-coded semantic-convention version (“registry 1.40”) from a doc comment, relying on the repo’s actual pin instead.
Changes:
- Removed the specific “registry 1.40” anchor from the reserved-prefixes doc comment to avoid future drift.
- Kept the actionable maintenance instruction (“extend when Weaver advances; do not let the list drift silently”).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment-only. The reserved-prefix doc comment anchored itself to "registry 1.40" while the repo pin is v1.41.0. Numbers in comments drift — the pin lives in
common/types.tsp— so the version anchor is deleted entirely; the maintenance instruction stays.Verification:
npm run lint(build:emitters + tsp compile --warn-as-error) — Compilation completed successfully. Complete-and-verified.🤖 Generated with Claude Code