@ctavan: Finally pulling the trigger on enabing release-please here. 🎉

Merging this PR should publish uuid@11.0.0 to NPM, but this'll be the first actual test of that.

'Wish I could say this has gone smoothly, but there's been a couple hiccups:

• RP initially marked this as version 10.0.0. Why? I don't know. But I fixed that by manually overriding the version with chore: release 11.0.0 #805. (Note: manual-override like that also provides a way of doing prerelease versions, if all else fails.)
• The CHANGELOG updates here include some outdated commits from pre-v11. Why? Again, I don't know. Maybe something to do with non-linear git commit history? 'Not at all sure that's the issue here, but I saw something similar with standard-version when doing the v11-prerelease, so I suspect it's more an issue with the git repo structure and not RP.

The upshot of this is that I'm hopefull these are one-off issues and that things will go more smoothly moving forward.

Regarding the actual release, it's worth noting that there's no actual changes to the built NPM release. All the recent code churn has just been fixing up the dev and CI toolchains.

Anyhow... let me know if you have any concerns.

@ctavan Note: I've created a uuidbot account to use for automated tasks like this, and updated the PAT used by the RP workflow to one generated from that account. Moving forward, release PRs should show up as coming from uuidbot instead of me.

I'm sharing the account info with you via lastpass, so keep an eye out for that email. It'll ask you to create an account if you don't have one, which is a nuisance. Let me know if there's a better way of sharing. (I use 1password as well, but lastpass is where I keep this sort of thing so that's what's convenient on my end.)

One last note before merging: PR is blocked because the commits need to be signed... but I don't see an obvious way of fixing that at the moment. So yet another reason to allow admins to override and merge anyway.

🤖 Created releases:

• v11.0.0
  🌻