chore: release main

[github-actions[bot]]

:robot: I have created a release *beep* *boop*

@amagaki/amagaki: 2.2.3

### Bug Fixes * alt text will only show once on a11y highlighter ([13ade79](https://www.github.com/blinkk/amagaki/commit/13ade7902ce179fbd3e5901820d0a7b8f829afbc))

@amagaki/amagaki-plugin-page-builder: 3.11.0

### Features * add image inspector ([#211](https://www.github.com/blinkk/amagaki/issues/211)) ([6db732d](https://www.github.com/blinkk/amagaki/commit/6db732ddeb297de455acc5fc55dabd3c9cbb7e4f)) ### Bug Fixes * alt text will only show once on a11y highlighter ([13ade79](https://www.github.com/blinkk/amagaki/commit/13ade7902ce179fbd3e5901820d0a7b8f829afbc))

create-amagaki: 0.1.1

### Bug Fixes * alt text will only show once on a11y highlighter ([13ade79](https://www.github.com/blinkk/amagaki/commit/13ade7902ce179fbd3e5901820d0a7b8f829afbc))

This PR was generated with Release Please. See documentation.

[hellomichael]

Hey @jeremydw,

Are there any best practices for releasing new amagaki versions? Is it just a matter of merging this in?

[stevenle]

IIRC you can merge to main and the release-please action should create a PR that bumps the package.json version. Once that other PR is merged, it should automatically update the npm package.

[jeremydw]

I just hit rebase and merge, and that should kick off the automated release

[github-actions[bot]]

:robot: Release for @amagaki/amagaki is at https://github.com/blinkk/amagaki/releases/tag/amagaki-v2.2.3 :sunflower:

[github-actions[bot]]

:robot: Release for @amagaki/amagaki-plugin-page-builder is at https://github.com/blinkk/amagaki/releases/tag/amagaki-plugin-page-builder-v3.11.0 :sunflower:

[github-actions[bot]]

:robot: Release for create-amagaki is at https://github.com/blinkk/amagaki/releases/tag/create-amagaki-v0.1.1 :sunflower: