chore(main): release 11.0.0 prerelease

[github-actions]

🤖 I have created a release beep boop

11.0.0 (2024-11-11)

⚠ BREAKING CHANGES

• adapt new engine range for Mocha 11 (#5216)

🌟 Features

• allow calling hook methods (#5231) (e3da641)

🩹 Fixes

• adapt new engine range for Mocha 11 (#5216) (80da25a)

📚 Documentation

• downgrade example/tests chai to 4.5.0 (#5245) (eac87e1)

---

This PR was generated with Release Please. See documentation.

[JoshuaKGoldberg]

https://github.com/mochajs/mocha/pull/5216/files#diff-79e894bd12b1ec1a260f6afff87ddaa3e1579fbac8cb64e8fac8cc88e8a6197eR6 should make this publish as a prerelease, not stable. But in case it publishes as stable after all I'll unpublish from npm.

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

[github-actions]

🤖 Created releases:

• v11.0.0
  🌻

[voxpelli]

Huh, wasn’t the intent to do a 11.0.0-beta or something first? 🤔

[JoshuaKGoldberg]

That's what I would have liked more. I suppose we'll need to reconfigure release-please?

[voxpelli]

It was what I intended it to do, but it’s hard to try the config before the PR is created and now that it’s merged it doesn’t matter much, we can only add on top of 11.0.0 – we could maybe reconfigure it to be 11.0.1-beta or such