diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1b8d02613..d522ed13e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -20,6 +20,9 @@ This is a rough outline of what a contributor's workflow looks like: - Create a topic branch from where you want to base your work (usually main). - Make commits of logical units. - Make sure your commit messages are in the proper format (see below). +- Add a descriptively named release-note fragment for user-visible changes. See + [`docs/release-notes.d/README.md`](docs/release-notes.d/README.md) for the + filename format, categories, and validation commands. - Push your changes to a topic branch in your fork of the repository. - Make sure the tests pass, and add any new tests as appropriate. - Submit a pull request to the original repository. diff --git a/docs/release-notes.d/azure-provider-unit-tests.change.md b/docs/release-notes.d/azure-provider-unit-tests.change.md new file mode 100644 index 000000000..e89474a9e --- /dev/null +++ b/docs/release-notes.d/azure-provider-unit-tests.change.md @@ -0,0 +1,2 @@ + +Add Azure provider unit tests covering the fallback to custom data when IMDS userdata is empty and the indefinite wait for a missing OVF config drive diff --git a/docs/release-notes.d/butane-inline-gzip-validation.bugfix.md b/docs/release-notes.d/butane-inline-gzip-validation.bugfix.md new file mode 100644 index 000000000..ec0f2b7c8 --- /dev/null +++ b/docs/release-notes.d/butane-inline-gzip-validation.bugfix.md @@ -0,0 +1,4 @@ + +Butane: report an error when `compression: gzip` is set on inline contents +that are not gzip-compressed, instead of generating a config that fails at +first boot diff --git a/docs/release-notes.d/go-fix-pipeline.change.md b/docs/release-notes.d/go-fix-pipeline.change.md new file mode 100644 index 000000000..6597f17f8 --- /dev/null +++ b/docs/release-notes.d/go-fix-pipeline.change.md @@ -0,0 +1,2 @@ + +Restore `go fix` behavior on go.yml pipeline