31 lines
1.4 KiB
YAML
31 lines
1.4 KiB
YAML
# Use this changelog template to create an entry for release notes.
|
|
#
|
|
# If your change doesn't affect end users you should instead start
|
|
# your pull request title with [chore] or use the "Skip Changelog" label.
|
|
|
|
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
|
|
change_type: enhancement
|
|
|
|
# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
|
|
component: other
|
|
|
|
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
|
|
note: Update resource to include stability in the YAML file
|
|
|
|
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
|
|
# The values here must be integers.
|
|
issues: [1399]
|
|
|
|
# (Optional) One or more lines of additional information to render under the primary note.
|
|
# These lines will be padded with 2 spaces and then inserted directly into the document.
|
|
# Use pipe (|) for multiline entries.
|
|
subtext: |
|
|
Makes the following changes:
|
|
|
|
- Require `name` on resource groups.
|
|
- Enforce backwards compatibility stability requirements on resource groups.
|
|
- Rename `telemetry` to `telemetry.sdk`, attributes are unchanged.
|
|
- Mark `telemetry.sdk` and `resource` as stable in YAML model.
|
|
- Markdown templates for resource groups NOW includes header describing
|
|
the reosurce `type`, `stability` and `description`.
|