You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# - breaking-change: a change to previously-documented behavior
4
+
# - deprecation: functionality that is being removed in a later release
5
+
# - bug-fix: fixes a problem in a previous version
6
+
# - enhancement: extends functionality but does not break or fix existing behavior
7
+
# - feature: new functionality
8
+
# - known-issue: problems that we are aware of in a given version
9
+
# - security: impacts on the security of a product or a user’s deployment.
10
+
# - upgrade: important information for someone upgrading from a prior version
11
+
# - other: does not fit into any of the other categories
12
+
kind: feature
13
+
14
+
# REQUIRED for all kinds
15
+
# Change summary; a 80ish characters long description of the change.
16
+
summary: Add a new `subsections` configuration option that specifies whether to show `component`s as subsections in rendered release notes.
17
+
18
+
# REQUIRED for breaking-change, deprecation, known-issue
19
+
# Long description; in case the summary is not enough to describe the change
20
+
# this field accommodate a description without length limits.
21
+
description: This should be set to `true` in repos with multiple `component`s. For example, the Beats repo, which contains changelog entries for multiple `component`s like `filebeat`, `metricbeat`, etc.
22
+
23
+
# REQUIRED for breaking-change, deprecation, known-issue
24
+
# impact:
25
+
26
+
# REQUIRED for breaking-change, deprecation, known-issue
27
+
# action:
28
+
29
+
# REQUIRED for all kinds
30
+
# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc.
31
+
component:
32
+
33
+
# AUTOMATED
34
+
# OPTIONAL to manually add other PR URLs
35
+
# PR URL: A link the PR that added the changeset.
36
+
# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added.
37
+
# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number.
38
+
# Please provide it if you are adding a fragment for a different PR.
Copy file name to clipboardExpand all lines: docs/configuration.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,7 @@ When generating Markdown files, at a minimum you should set the following settin
24
24
|`owner` (required) |`elastic`| The owner of the GitHub repo. |
25
25
|`repo` (required) | ‒ | The name of the GitHub repo. |
26
26
|`rendered_changelog_destination`|`changelog`| The directory where you want to put the generated files.<br><br>When generating Markdown files, this should probably be `docs/release-notes/_snippets`. |
27
+
|`subsections`|`false`| Whether to show `component`s as subsections in rendered release notes. This should be set to `true` in repos with multiple `component`s (for example, Beats). |
0 commit comments