/
builder-strict-versioning.yaml
29 lines (23 loc) · 1.39 KB
/
builder-strict-versioning.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
# Use this changelog template to create an entry for release notes.
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: breaking
# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
component: builder
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
note: Add strict version checking when using the builder. Add the temporary flag `--skip-strict-versioning `for skipping this check.
# One or more tracking issues or pull requests related to the change
issues: [9896]
# (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: |
Strict version checking will error on major and minor version mismatches
between the `otelcol_version` configured and the builder version or versions
in the go.mod. This check can be temporarily disabled by using the `--skip-strict-versioning`
flag. This flag will be removed in a future minor version.
# Optional: The change log or logs in which this entry should be included.
# e.g. '[user]' or '[user, api]'
# Include 'user' if the change is relevant to end users.
# Include 'api' if there is a change to a library API.
# Default: '[user]'
change_logs: []