Update published packages changelogs

[gziolo]

We missed this for the last 2 releases of packages. They contained only small bug fixes so it isn't a big deal but I added them for the record.

[tofumatt]

👍🏻

[noisysocks]

It's unfortunate that updating these CHANGELOG.md files means that Lerna treats the packages as having changed. For example, because this PR updates packages/annotations/CHANGELOG.md, @wordpress/annotations will be published the next time we do a packages release.

In fact, while doing the last publish, I noticed a few packages where the last few patch releases have been entirely CHANGELOG.md updates similar to this one. This is because we updated the CHANGELOG.md files after publishing.

Not sure how to address this other than to get into the habit of updating the CHANGELOG.md files before publishing. Ideally our process would be automated 😅

[noisysocks]

@wordpress/list-reusable-blocks is a good example. Check it out—the last 11 releases have been completely unnecessary 😛

https://github.com/WordPress/gutenberg/commits/master/packages/list-reusable-blocks

[ntwb]

@noisysocks Changes to any CHANGELOG.md should be ignored by Lerna: (docs)

gutenberg/lerna.json

Lines 7 to 11 in b5a709f

	"ignoreChanges": [
	"**/benchmark/*.js",
	"**/CHANGELOG.md",
	"**/test/**"
	],

[noisysocks]

Interesting—there must be some other problem with our configuration. Right now if I run npm run publish:check, I get:

@wordpress/block-library
@wordpress/blocks
@wordpress/components
@wordpress/edit-post
@wordpress/editor
@wordpress/format-library
@wordpress/html-entities
@wordpress/list-reusable-blocks
@wordpress/nux

Of those, @wordpress/list-reusable-blocks and @wordpress/nux have not been recently changed, which you can see by looking in the GitHub history:

https://github.com/WordPress/gutenberg/commits/master/packages/list-reusable-blocks
https://github.com/WordPress/gutenberg/commits/master/packages/nux

[ntwb]

Indeed they have not changed recently, but the package.json dependencies in @wordpress/nux:

gutenberg/packages/nux/package.json

Lines 24 to 28 in b5a709f

	"@wordpress/components": "file:../components",
	"@wordpress/compose": "file:../compose",
	"@wordpress/data": "file:../data",
	"@wordpress/element": "file:../element",
	"@wordpress/i18n": "file:../i18n",

Which are currently:

https://unpkg.com/@wordpress/[email protected]/package.json

@wordpress/components | "^7.0.2"
@wordpress/compose | "^3.0.0"
@wordpress/data | "^4.0.1"
@wordpress/element | "^2.1.8"
@wordpress/i18n | "^3.1.0"

And as @wordpress/components does include recent changes, the @wordpress/components | "^7.0.2" will get bumped to 7.0.3, 7.1.0, or 8.0.0 depending on semver bump of that package

[noisysocks]

🤦‍♂️ that makes total sense—thanks for explaining @ntwb!