feat(config): bump declarative configuration schema to v1.1.0#5345
Merged
xrmx merged 6 commits intoJun 25, 2026
Conversation
MikeGoldsmith
approved these changes
Jun 24, 2026
MikeGoldsmith
left a comment
MikeGoldsmith
left a comment
Member
There was a problem hiding this comment.
Looks good, thanks @aman-panjwani - just need to remove the duplicate changelog file 👍🏻
herin049
approved these changes
Jun 24, 2026
xrmx
approved these changes
Jun 25, 2026
github-project-automation
Bot
moved this from Ready for merge
to Approved PRs
in Python PR digest
Contributor
|
LGTM, I think we should write somewhere in the doc the version of the schema we support since people writing configs need to know. |
Contributor
Author
|
Thanks @xrmx! Good point - I'll open a follow-up issue to track adding the supported schema version to the docs so it doesn't block this merge. Happy to work on that as well! |
Member
|
Actually, we already have a PR open to add a compatibility matrix, which would include what version of the config spec the SDK works with. I think we can merge this PR and let that PR handle the versioning note 👍🏻 |
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
4 participants
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.
Description
Bumps the bundled JSON schema from v1.0 to v1.1.0 and updates the Python SDK to match.
Fixes #5333
Changes
schema.jsonto v1.1.0models.pyviatox -e generate-config-from-jsonschema_meter_provider.py:without_target_info_development→target_info_enabled_development(with logic flip + None handling)without_scope_info→scope_info_enabledwith_resource_constant_labels→resource_constant_labelsIdGeneratoronTracerProvider(model-only; factory wiring tracked in feat(config): wire id_generator from declarative configuration to TracerProvider #5334)max_export_batch_size_developmentonPeriodicMetricReaderevent_to_span_event_bridge_developmentonLogRecordProcessorType of change
How Has This Been Tested?
models.pyviatox -e generate-config-from-jsonschematox -e opentelemetry-sdk— all tests passingtox -e ruff— linter and formatter passingDoes This PR Require a Contrib Repo Change?
Checklist: