Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release 0.4.4 #47

Merged

Conversation

nito-bot[bot]
Copy link
Contributor

@nito-bot nito-bot bot commented Mar 22, 2024

🤖 I have created a release beep boop

0.4.4 (2024-04-04)

Bug Fixes

  • deps: bun.lockb (faf95a4)
  • deps: update dependency @astrojs/check to v0.5.10 (5d12e3d)
  • deps: update dependency @astrojs/starlight to v0.21.2 (68cb93d)
  • deps: update dependency @astrojs/starlight to v0.21.3 (d6196b8)
  • deps: update dependency astro to v4.5.12 (c52b708)
  • deps: update dependency astro to v4.5.15 (3f66599)
  • deps: update dependency astro to v4.5.8 (407c15f)
  • deps: update dependency astro to v4.5.9 (f65e9d2)
  • deps: update dependency sharp to v0.33.3 (b57a0bf)

This PR was generated with Release Please. See documentation.

Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://190a6a64.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch from 0cd976a to 321f974 Compare March 22, 2024 05:55
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://351369b0.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch 2 times, most recently from 4199289 to 80b35ed Compare March 23, 2024 23:48
@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch from 80b35ed to 827b3af Compare March 23, 2024 23:49
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://d12ccd95.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch from 827b3af to ad2fc0f Compare March 25, 2024 18:57
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://3fc7760c.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch from ad2fc0f to 44da4f3 Compare March 29, 2024 08:28
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://4ff1097e.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch from 44da4f3 to 25a60d5 Compare March 29, 2024 08:32
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://a49107ac.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch 2 times, most recently from 163949b to b01227b Compare April 1, 2024 17:05
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://9fd58e5d.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch 3 times, most recently from ec60d29 to 467bde3 Compare April 4, 2024 14:53
@nito-bot nito-bot bot requested a deployment to nito-docs (Preview) April 4, 2024 14:53 Abandoned
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://d709f486.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito-docs branch from 467bde3 to 7364733 Compare April 4, 2024 14:56
@tatsutakein tatsutakein enabled auto-merge April 4, 2024 14:56
@tatsutakein tatsutakein merged commit 42d8117 into main Apr 4, 2024
7 checks passed
@tatsutakein tatsutakein deleted the release-please--branches--main--components--nito-docs branch April 4, 2024 14:57
@nito-bot
Copy link
Contributor Author

nito-bot bot commented Apr 4, 2024

🤖 Release is at https://github.com/nitoclub/nito-docs/releases/tag/v0.4.4 🌻

Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://2983627e.nito-docs.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant