Test run of release prep here. Everything looks good. The codeql pack release command correctly handles the manual version bump by setting the release version to the maximum of (current pack version) and (previous release version plus bump).

I forgot where we came down on this, but do we want to add a changelog note to each pack describing why we are bumping to 1.0.0?

Updated to add a change note to each pack explaining the bump to 1.0.0. Sample release prep here.

Thanks. With the category: breaking metadata, would this make the next release step bump all versions to 2.0.0?

@aeisenberg

With the category: breaking metadata, would this make the next release step bump all versions to 2.0.0?

No (although that's exactly what I was worried about). codeql pack release computes the new version number by bumping the version number of the previous release, and then uses either that or the current version number, whichever is higher. So, for a pack that was last released as 0.9.1, we get:

previousVersion = 0.9.1
bumpedVersion = 0.10.0  // 0.9.1, bumped for a breaking change, which bumps the minor version number because the major version number is 0
currentVersion = 1.0.0  // We removed the '-dev' suffix already
newVersion = 1.0.0  // max(0.10.0, 1.0.0)

(You can see the result in the test release prep PR I linked above).

I went ahead and merged it. The corresponding issue has been open for a week, and publicized on Slack, so I think we've had adequate opportunity for discussion.