We use the go-changelog to generate and update the changelog from files created in the .changelog/ directory. It is important that when you raise your Pull Request, there is a changelog entry which describes the changes your contribution makes. Not all changes require an entry in the CHANGELOG, guidance follows on what changes do.
The changelog format requires an entry in the following format, where HEADER corresponds to the changelog category, and the entry is the changelog entry itself. The entry should be included in a file in the .changelog directory with the naming convention {PR-NUMBER}.txt. For example, to create a changelog entry for pull request 1234, there should be a file named .changelog/1234.txt.
```release-note:{HEADER}
{ENTRY}
```If a pull request should contain multiple changelog entries, then multiple blocks can be added to the same changelog file. For example:
```release-note:note
resource/cloudflare_example: The `broken` attribute has been deprecated. All configurations using `broken` should be updated to use the new `not_broken` attribute instead.
```
```release-note:enhancement
resource/cloudflare_example: Add `not_broken` attribute
```In order to skip/pass the automated checks where a CHANGELOG entry is not required, apply the workflow/skip-changelog-entry label.
The CHANGELOG is intended to show operator-impacting changes to the codebase for a particular version. If every change or commit to the code resulted in an entry, the CHANGELOG would become less useful for operators. The lists below are general guidelines and examples for when a decision needs to be made to decide whether a change should have an entry.
A new resource entry should only contain the name of the resource, and use the release-note:new-resource header.
```release-note:new-resource
cloudflare_new_thing
```A new datasource entry should only contain the name of the datasource, and use the release-note:new-data-source header.
```release-note:new-data-source
cloudflare_new_data_thing
```A new full length documentation entry gives the title of the documentation added, using the release-note:new-guide header.
```release-note:new-guide
How To Get Started With Tool X
```A new bug entry should use the release-note:bug header and have a prefix indicating the resource or datasource it corresponds to, a colon, then followed by a brief summary. Use a provider prefix for provider level fixes.
```release-note:bug
resource/cloudflare_example: Fix 'thing' being optional
```A new enhancement entry should use the release-note:enhancement header and have a prefix indicating the resource or datasource it corresponds to, a colon, then followed by a brief summary. Use a provider prefix for provider level enchancements.
```release-note:enhancement
resource/cloudflare_example: Add new capability
```A breaking-change entry should use the release-note:note header and have a prefix indicating the resource or datasource it corresponds to, a colon, then followed by a brief summary. Use a provider prefix for provider level changes.
```release-note:note
resource/cloudflare_example: X attribute is being deprecated in favor of the new Y attribute
```A breaking-change entry should use the release-note:breaking-change header and have a prefix indicating the resource or datasource it corresponds to, a colon, then followed by a brief summary. Use a provider prefix for provider level changes.
```release-note:breaking-change
resource/cloudflare_example: Resource no longer works for 'EXAMPLE' parameters
```Dependency updates: If the update contains relevant bug fixes or enhancements that affect operators, those should be called out. Any changes which do not fit into the above categories but warrant highlighting. Use resource/datasource/provider prefixes where appropriate.
```release-note:note
resource/cloudflare_example: Example resource now does X slightly differently
```
```release-note:dependency
`cloudflare-go` v0.1.0 => v0.1.1
```- Resource and provider documentation updates
- Testing updates
- Code refactoring (context dependant)