chore: release

[github-actions]

🤖 New release

• tokio-console: 0.1.11 -> 0.2.0
• console-api: 0.7.0 -> 0.8.0
• console-subscriber: 0.3.0 -> 0.4.0

Changelog

tokio-console

0.2.0 - (2024-07-16)

Breaking Changes

• Upgrade tonic to 0.12 (#571) (5f6faa2)
  This is a breaking change for users of console-api and
  console-subscriber, as it changes the public tonic, prost and
  prost-types dependency to a semver-incompatible version. This breaks
  compatibility with tonic 0.11.x as well as prost/prost-types
  0.12.x.

Fixed

• Handle Windows path correctly (#555) (6ad0def)

Updated

• breaking Upgrade tonic to 0.12 (#571) (5f6faa2)

console-api

0.8.0 - (2024-07-16)

Breaking Changes

• Upgrade tonic to 0.12 (#571) (5f6faa2)
  This is a breaking change for users of console-api and
  console-subscriber, as it changes the public tonic, prost and
  prost-types dependency to a semver-incompatible version. This breaks
  compatibility with tonic 0.11.x as well as prost/prost-types
  0.12.x.

Updated

• breaking Upgrade tonic to 0.12 (#571) (5f6faa2)

console-subscriber

0.4.0 - (2024-07-16)

Breaking Changes

• Upgrade tonic to 0.12 (#571) (5f6faa2)
  This is a breaking change for users of console-api and
  console-subscriber, as it changes the public tonic, prost and
  prost-types dependency to a semver-incompatible version. This breaks
  compatibility with tonic 0.11.x as well as prost/prost-types
  0.12.x.

Added

• Add TOKIO_CONSOLE_BUFFER_CAPACITY env variable (#568) (a6cf14b)

Updated

• breaking Upgrade tonic to 0.12 (#571) (5f6faa2)

---

This PR was generated with release-plz.

[Rustin170506]

@hds Does this a bug from release-plz? I am not sure why it triggers a new release.

[hds]

@hi-rustin This is how release-plz works. The action creates (and the subsequently updates) a PR to release whenever there are changes. This means that we will effectively always have a release PR sitting around, and it's up to us to choose when to merge it (which will trigger a release).

Clearly I need to finish #558. (-: