chore: release v0.30.0

[github-actions]

🤖 New release

• octocrab: 0.29.3 -> 0.30.0 (⚠️ API breaking changes)

⚠️ octocrab breaking changes

--- failure struct_missing: pub struct removed or renamed ---

Description:
A publicly-visible struct cannot be imported by its prior path. A `pub use` may have been removed, or the struct itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-check/tree/v0.22.1/src/lints/struct_missing.ron

Failed in:
  struct octocrab::models::webhook_events::payload::CommitComment, previously in file /tmp/.tmpGzP1x8/octocrab/src/models/webhook_events/payload/commit_comment.rs:25

Changelog

0.30.0 - 2023-09-01

Other

• Fix commit_comment webhook event parsing (#453)
• Add Octocrab::users() and UsersHandler::repos (#451)
• Add CommitHandler::associated_check_runs (#450)
• Fix installation token cache issue (#442)
• Add projects Api (#447)
• Enhance installation webhook events
• Add test for push webhook event
• Implement custom deserialization for hybrid Github API timestamps
• Make webhook_events deserialization tests more robust

---

This PR was generated with release-plz.

[gagbo]

Note: it's weird that the changeset is not considered a breaking change and bumped to 0.30.0:

In this commit I changed models::webhook_events::InstallationWebhookEventPayload::repositories from Vec<_> to Option<Vec<_>>, even had to change the tests to make the old version compile. And if I didn't miss anything, this field is part of the public API of the crate (at least, it should be and that's a bug if the field is not exposed)

[XAMPPRocky]

Note: it's weird that the changeset is not considered a breaking change and bumped to 0.30.0

There are limitations to cargo-semver-checks and this is one of them, thanks for flagging, it I'll set it to 0.30.0 in the PR before merging.