Skip to content

Manifest renames#1202

Merged
jsuereth merged 33 commits intoopen-telemetry:mainfrom
lmolkova:manifest-renames
Feb 23, 2026
Merged

Manifest renames#1202
jsuereth merged 33 commits intoopen-telemetry:mainfrom
lmolkova:manifest-renames

Conversation

@lmolkova
Copy link
Member

@lmolkova lmolkova commented Feb 14, 2026

Fixes #1197

Renames:

  • registry_manifest.yaml is now deprecated (but supported), use manifest.yaml instead
  • schema_url is now used consistently in resolved schema and manifest instead of registry_id, registry_url, ... . It can be a source of the registry contents, but does not have to be. When specifying dependencies, it's allowed to pass registry_path in addition to schema_url. This way, schema url is essentially a combination of name and version in a certain format.
  • resolved_schema_url -> resolved_schema_uri

Changes should be backward compatible, old properties of RegistryManifest and Dependency are supported, but deprecated

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request implements naming convention changes for multi-registry manifests as specified in issue #1197. The changes standardize the way registries are identified and referenced across the Weaver codebase.

Changes:

  • Renames registry_manifest.yaml to manifest.yaml (with backward compatibility for the old name)
  • Introduces SchemaUrl type to standardize registry identification using OTel schema URL format
  • Replaces separate name, version, and schema_base_url fields with unified schema_url field
  • Renames resolved_schema_url to resolved_schema_uri for consistency
  • Updates all test data and references throughout the codebase to use the new naming conventions

Reviewed changes

Copilot reviewed 49 out of 50 changed files in this pull request and generated 6 comments.

Show a summary per file
File Description
crates/weaver_semconv/src/schema_url.rs New SchemaUrl type for URL-based registry identification with name/version extraction
crates/weaver_semconv/src/manifest.rs Updated RegistryManifest and Dependency with schema_url field, deprecated old fields
crates/weaver_semconv/src/registry_repo.rs Updated RegistryRepo to use schema_url, added legacy manifest file support
crates/weaver_semconv/src/registry.rs Updated registry loading to use SchemaUrl
crates/weaver_resolver/* Updated resolver to work with schema_url instead of registry_id
crates/weaver_resolved_schema/src/v2/* Updated V2 schema to use SchemaUrl, removed registry_url field
crates/weaver_forge/src/v2/registry.rs Updated ForgeResolvedRegistry to use schema_url
crates/weaver_live_check/* Updated to use boxed V2 types and schema_url
tests/* Updated test code to use new API with schema_url
Test data files Updated manifest files to use new schema_url format

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codecov
Copy link

codecov bot commented Feb 14, 2026

Codecov Report

❌ Patch coverage is 84.82143% with 34 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.4%. Comparing base (93546fb) to head (09721d2).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
crates/weaver_semconv/src/registry_repo.rs 81.1% 10 Missing ⚠️
crates/weaver_resolver/src/loader.rs 69.2% 8 Missing ⚠️
crates/weaver_semconv/src/manifest.rs 88.4% 6 Missing ⚠️
crates/weaver_semconv/src/registry.rs 50.0% 3 Missing ⚠️
crates/weaver_resolved_schema/src/lib.rs 0.0% 2 Missing ⚠️
crates/weaver_resolved_schema/src/error.rs 0.0% 1 Missing ⚠️
crates/weaver_resolved_schema/src/v2/mod.rs 80.0% 1 Missing ⚠️
crates/weaver_resolver/src/dependency.rs 83.3% 1 Missing ⚠️
crates/weaver_resolver/src/lib.rs 85.7% 1 Missing ⚠️
crates/weaver_semconv/src/schema_url.rs 98.4% 1 Missing ⚠️
Additional details and impacted files
@@          Coverage Diff           @@
##            main   #1202    +/-   ##
======================================
  Coverage   80.3%   80.4%            
======================================
  Files        109     110     +1     
  Lines       8855    8984   +129     
======================================
+ Hits        7113    7225   +112     
- Misses      1742    1759    +17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

lmolkova and others added 6 commits February 14, 2026 14:56
…registry_manifest.yaml

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…/registry_manifest.yaml

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 49 out of 50 changed files in this pull request and generated 3 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@lmolkova lmolkova requested a review from a team as a code owner February 15, 2026 02:20
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 50 out of 51 changed files in this pull request and generated 7 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

lmolkova added a commit to lmolkova/opentelemetry-specification that referenced this pull request Feb 15, 2026
Copy link
Contributor

@jsuereth jsuereth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good!

  • Should we have some kind of "TODO" tracker to remove the backwards compatibility support after version X or some such?
  • How will we add warnings around supporting legacy manifest file names, or legacy structure for name/version? We may want to keep some flag on a Manifest we can later producer "diagnostic" warnings from, post serde.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 50 out of 51 changed files in this pull request and generated 3 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@lmolkova
Copy link
Member Author

Overall looks good!

  • Should we have some kind of "TODO" tracker to remove the backwards compatibility support after version X or some such?
  • How will we add warnings around supporting legacy manifest file names, or legacy structure for name/version? We may want to keep some flag on a Manifest we can later producer "diagnostic" warnings from, post serde.

I've updated the PR to:

  • error when registry_manifest.yaml is used with --future, there is a warning (diag message) otherwise
  • error when old props are used in new manifest.yaml, and warning diag messages for them when used with old manifest

Let's chat about back-compat policy on the SIG call tomorrow

@lmolkova lmolkova moved this to To consider for the next release in OTel Weaver Project Feb 18, 2026
@jsuereth jsuereth moved this from To consider for the next release to Next Release in OTel Weaver Project Feb 18, 2026
Copy link
Contributor

@jsuereth jsuereth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, almost ready to merge, but a bunch of rust-related cleanups.

@jsuereth jsuereth enabled auto-merge (squash) February 23, 2026 16:17
@jsuereth jsuereth merged commit 4da6fa6 into open-telemetry:main Feb 23, 2026
23 checks passed
@github-project-automation github-project-automation bot moved this from Next Release to Done in OTel Weaver Project Feb 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Update naming conventions for multi-registry manifests

3 participants