-
Notifications
You must be signed in to change notification settings - Fork 620
Expand file tree
/
Copy pathfeat_blocked-upgrades.yaml
More file actions
20 lines (16 loc) · 1.15 KB
/
feat_blocked-upgrades.yaml
File metadata and controls
20 lines (16 loc) · 1.15 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: enhancement
# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action)
component: auto-instrumentation
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
note: Allow instrumentation upgrades to be blocked for versions containing major breaking changes.
# One or more tracking issues related to the change
issues: [4646, 2542]
# (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: |
Some instrumentation upgrades involve major breaking changes. The operator can't help with those, but it can
alert the user about them. This change makes this possible. It will also allow us to set the latest version
for new Instrumentation resources by default.
See https://github.com/open-telemetry/opentelemetry-operator/issues/2542 for the primary example.