diff --git a/changelog/0.7.0.yaml b/changelog/0.7.0.yaml new file mode 100644 index 0000000..c5b45dd --- /dev/null +++ b/changelog/0.7.0.yaml @@ -0,0 +1,56 @@ +version: 0.7.0 +entries: + - kind: feature + summary: Default new fragment title to git branch name + description: | + New changelog fragments are often created while working inside a git branch. This change makes the title argument to the `new` sub-command optional, defaulting the title to the name of the current git branch. + component: "" + pr: + - https://github.com/elastic/elastic-agent-changelog-tool/pull/142 + issue: [] + timestamp: 1686835318 + file: + name: 1686835318-new-title-optional.yaml + checksum: 83a654f503e76ae5fc77dcbdfd4bad36244b0d28 + - kind: feature + summary: Remove single quote from file names + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent-changelog-tool/pull/168 + issue: [] + timestamp: 1695368036 + file: + name: 1695368036-remove-single-quote-from-file-names.yaml + checksum: 73af69dcab0549aaee2abb615c415aa6b92dc286 + - kind: enhancement + summary: Update go version to 1.21.9 and dependencies + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent-changelog-tool/pull/181 + issue: [] + timestamp: 1713993914 + file: + name: 1713993914-Update-go-version-and-dependencies.yaml + checksum: cae29df4fd7ad3864b4752f58f05c596a53bf35f + - kind: feature + summary: Support outputting Markdown files. + description: | + Updates the `render` command to accept `--file_type` set to either `asciidoc` or `markdown`. + + When set to `asciidoc`, it renders a single AsciiDoc file for a given version using the existing `asciidoc-embedded` template. + + When set to `markdown`, it renders three Markdown files for a given version: + + * Release notes: Creates an `index.md` file using `markdown-index-template`. + * Breaking changes: Creates a `breaking.md` file using `markdown-breaking-template`. + * Deprecations: Creates a `deprecations.md` file using `markdown-deprecations-template`. + component: "" + pr: + - https://github.com/elastic/elastic-agent-changelog-tool/pull/213 + issue: [] + timestamp: 1755717164 + file: + name: 1755717164-markdown.yaml + checksum: 3713fe85263bd84ac018a8e3373d0b824d798ecb diff --git a/changelog/fragments/1686835318-new-title-optional.yaml b/changelog/fragments/1686835318-new-title-optional.yaml deleted file mode 100644 index 952d958..0000000 --- a/changelog/fragments/1686835318-new-title-optional.yaml +++ /dev/null @@ -1,35 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Default new fragment title to git branch name - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -description: > - New changelog fragments are often created while working inside a - git branch. This change makes the title argument to the `new` sub-command - optional, defaulting the title to the name of the current git branch. - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1695368036-remove-single-quote-from-file-names.yaml b/changelog/fragments/1695368036-remove-single-quote-from-file-names.yaml deleted file mode 100644 index 9627158..0000000 --- a/changelog/fragments/1695368036-remove-single-quote-from-file-names.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Remove single quote from file names - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1713993914-Update-go-version-and-dependencies.yaml b/changelog/fragments/1713993914-Update-go-version-and-dependencies.yaml deleted file mode 100644 index ef58678..0000000 --- a/changelog/fragments/1713993914-Update-go-version-and-dependencies.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Update go version to 1.21.9 and dependencies - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1755717164-markdown.yaml b/changelog/fragments/1755717164-markdown.yaml deleted file mode 100644 index 4aaad53..0000000 --- a/changelog/fragments/1755717164-markdown.yaml +++ /dev/null @@ -1,55 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Support outputting Markdown files. - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: | - Updates the `render` command to accept `--file_type` set to either `asciidoc` or `markdown`. - - When set to `asciidoc`, it renders a single AsciiDoc file for a given version using the existing `asciidoc-embedded` template. - - When set to `markdown`, it renders three Markdown files for a given version: - - * Release notes: Creates an `index.md` file using `markdown-index-template`. - * Breaking changes: Creates a `breaking.md` file using `markdown-breaking-template`. - * Deprecations: Creates a `deprecations.md` file using `markdown-deprecations-template`. - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: - - https://github.com/elastic/elastic-agent-changelog-tool/pull/213 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234