docs: add backward incompat note about #10875

[schmichael]

Fixes #11002

Is this the best way to update the changelog for old releases? It's certainly easy enough and doesn't seem to conflict with the new go-changelog driven generation. Since we always link to tags for the changelog it seems moot to update it anyway, but maybe it will help someone.

Wording advice always eagerly accepted. I'll update https://github.com/hashicorp/nomad/releases/tag/v1.1.3 once this is merged.

Screenshot of the upgrade guide:

[notnoop]

Thanks for catching and noting it.

Is this the best way to update the changelog for old releases? It's certainly easy enough and doesn't seem to conflict with the new go-changelog driven generation

Yes. For historical edits, we need to bypass .changelog. Can you include a note about post-release modifications in contributing/CHANGELOG.md file as well? Thanks!

[schmichael]

@notnoop Oops, the FAQ at the bottom already covers this. My mistake! https://github.com/hashicorp/nomad/blob/2ffb7e1397403c13f1c7bef06528a3b245a3fa78/contributing/CHANGELOG.md#can-i-amend-the-changelog-entry-after-the-pr-merged

[notnoop]

hehe. I actually checked there as well but thought it only covered post-merge pre-release case. Oops!

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.