@@ -43,11 +43,9 @@ $ elastic-agent-changelog-tool build --version=next --owner <owner> --repo <repo
4343
4444then render the consolidated changelog with:
4545```
46- $ elastic-agent-changelog-tool render --version=next --template <template >
46+ $ elastic-agent-changelog-tool render --version=next --file_type <asciidoc|markdown >
4747```
4848
49- The template value can be chosen from a predefined internal list of templates (` render --help ` ) or use a full path to your template file.
50-
5149An example is [ ` ../changelog/0.1.0.yaml ` ] ( ../changelog/0.1.0.yaml ) .
5250
5351### My PR does not need a changelog
@@ -82,9 +80,8 @@ $ elastic-agent-changelog-tool build --version=next --owner <owner> --repo <repo
8280
8381then render the consolidated changelog with:
8482```
85- $ $ elastic-agent-changelog-tool render --version=next --template <template >
83+ $ elastic-agent-changelog-tool render --version=next --file_type <asciidoc|markdown >
8684```
87- The template value can be chosen from a predefined internal list of templates (` render --help ` ) or use a full path to your template file.
8885
8986An example is [ ` ../changelog/0.1.0.yaml ` ] ( ../changelog/0.1.0.yaml ) .
9087
@@ -97,8 +94,14 @@ The side effect is that the changelog will include all entries from latest stabl
9794
98951 . Create consolidated changelog with ` $ elastic-agent-changelog-tool build --version <version> --owner <owner> --repo <repo> ` ;
9996* This will create ` ./changelog/x.y.z.yaml ` ;
100- 2 . Create rendered changelog with ` $ elastic-agent-changelog-tool render --version <version> --template <template> ` ;
101- * This will generate an asciidoc file in the ` changelog/ ` directory;
97+ 2 . Create rendered changelog with ` $ elastic-agent-changelog-tool render --version <version> --file_type <asciidoc|markdown> ` ;
98+
99+ Depending on the specified ` file_type ` , this will generate the following files:
100+ * ` markdown ` :
101+ * Release notes: ` ./changelog/<version>/index.md `
102+ * Breaking changes: ` ./changelog/<version>/breaking.md `
103+ * Deprecations: ` ./changelog/<version>/deprecations.md `
104+ * ` asciidoc ` : ` changelog/<version>.asciidoc `
1021053 . Use the rendered changelog.
103106
104107** Note** : we do not remove fragments, as they will be needed for the stable release version changelog.
@@ -111,30 +114,39 @@ The side effect is that the changelog will include all entries from latest stabl
111114
112115These steps require [ GitHub Authentication] ( ./github-authentication.md ) .
113116
114- * Wait for the last BC of the release. If another BC is generated after that or a patch version for a previous minor is released, you might need to restart the process.
115- * Create a branch ** from the commit of the BC** .
116- * From the root folder of the repository run:
117-
118- ```
119- $ elastic-agent-changelog-tool build --version x.y.z --owner <owner> --repo <repo>
120- ```
121- * Where:
122- * ` x.y.z ` is the version to release.
123- * ` owner ` is the user / organization the repository to use belongs to. The default value is ` elastic ` .
124- * ` repo ` is the name of the repository containing the issues / PRs, etc. The default value is ` elastic-agent ` .
125- * This will create ` ./changelog/x.y.z.yaml ` .
126- * From the root of the repository run:
127- ```
128- $ elastic-agent-changelog-tool cleanup
129- ```
130- * Commit the previous changes (consolidated changelod and removed files)
131- * From the root folder of the repository run:
132- ```
133- $ elastic-agent-changelog-tool render --version x.y.z --template <template>
134- ```
135- * This will generate an asciidoc fragment in the ` changelog/ ` directory.
136- * Integrate the generated fragment into the changelog. If the changelog is stored in the same repository, commit the changes in this same branch.
137- * Create a PR with the changes to the ` x.y ` branch.
117+ 1 . Wait for the last BC of the release. If another BC is generated after that or a patch version for a previous minor is released, you might need to restart the process.
118+ 1 . Create a branch ** from the commit of the BC** .
119+ 1 . From the root folder of the repository run:
120+
121+ ```
122+ $ elastic-agent-changelog-tool build --version x.y.z --owner <owner> --repo <repo>
123+ ```
124+
125+ Where:
126+
127+ * `x.y.z` is the version to release.
128+ * `owner` is the user / organization the repository to use belongs to. The default value is `elastic`.
129+ * `repo` is the name of the repository containing the issues / PRs, etc. The default value is `elastic-agent`.
130+
131+ This will create `./changelog/x.y.z.yaml`.
132+ 1. From the root of the repository run:
133+ ```
134+ $ elastic-agent-changelog-tool cleanup
135+ ```
136+ 1. Commit the previous changes (consolidated changelod and removed files)
137+ 1. From the root folder of the repository run:
138+ ```
139+ $ elastic-agent-changelog-tool render --version x.y.z --file_type <asciidoc|markdown>
140+ ```
141+
142+ Depending on the specified `file_type`, this will generate the following files:
143+ * `markdown`:
144+ * Release notes: `./changelog/<version>/index.md`
145+ * Breaking changes: `./changelog/<version>/breaking.md`
146+ * Deprecations: `./changelog/<version>/deprecations.md`
147+ * `asciidoc`: `changelog/<version>.asciidoc`
148+ 1. Integrate the generated fragment into the changelog. If the changelog is stored in the same repository, commit the changes in this same branch.
149+ 1. Create a PR with the changes to the `x.y` branch.
138150
139151
140152### On Release Day
0 commit comments