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.8 #185

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nito-bot[bot]
Copy link
Contributor

@nito-bot nito-bot bot commented Jul 23, 2024

🤖 I have created a release beep boop

0.4.8 (2025-01-07)

Bug Fixes

  • deps: update dependency @astrojs/check to v0.8.3 (706716e)
  • deps: update dependency @astrojs/check to v0.9.0 (b9056e2)
  • deps: update dependency @astrojs/check to v0.9.1 (1c863b0)
  • deps: update dependency @astrojs/check to v0.9.2 (e823cd6)
  • deps: update dependency @astrojs/check to v0.9.3 (295036f)
  • deps: update dependency @astrojs/check to v0.9.4 (ba9c82a)
  • deps: update dependency @astrojs/starlight to v0.25.2 (df6603b)
  • deps: update dependency @astrojs/starlight to v0.25.3 (759c8d8)
  • deps: update dependency @astrojs/starlight to v0.25.4 (1e76b6e)
  • deps: update dependency @astrojs/starlight to v0.25.5 (c47fdfa)
  • deps: update dependency @astrojs/starlight to v0.26.1 (999716b)
  • deps: update dependency @astrojs/starlight to v0.26.2 (0d9e559)
  • deps: update dependency @astrojs/starlight to v0.26.3 (c5e1a2b)
  • deps: update dependency @astrojs/starlight to v0.26.4 (fac6c61)
  • deps: update dependency @astrojs/starlight to v0.27.0 (be17e22)
  • deps: update dependency @astrojs/starlight to v0.27.1 (5930b63)
  • deps: update dependency @astrojs/starlight to v0.28.1 (76902d2)
  • deps: update dependency @astrojs/starlight to v0.28.2 (900d90b)
  • deps: update dependency @astrojs/starlight to v0.28.3 (a6196ba)
  • deps: update dependency @astrojs/starlight to v0.28.4 (6ef4335)
  • deps: update dependency @astrojs/starlight to v0.28.5 (dd994cb)
  • deps: update dependency @astrojs/starlight to v0.28.6 (807277f)
  • deps: update dependency @astrojs/starlight to v0.29.0 (#293) (9e8e65f)
  • deps: update dependency @astrojs/starlight to v0.29.1 (#300) (502a2d5)
  • deps: update dependency @astrojs/starlight to v0.29.2 (#301) (fe44ec4)
  • deps: update dependency @astrojs/starlight to v0.29.3 (#315) (0956a23)
  • deps: update dependency @astrojs/starlight to v0.30.0 (#317) (394e359)
  • deps: update dependency @astrojs/starlight to v0.30.1 (#318) (944ef02)
  • deps: update dependency @astrojs/starlight to v0.30.2 (#320) (93e1a73)
  • deps: update dependency @astrojs/starlight to v0.30.3 (#324) (2031fc0)
  • deps: update dependency @astrojs/starlight to v0.30.4 (#333) (24ad31c)
  • deps: update dependency @astrojs/starlight to v0.30.5 (#334) (ac8b3d5)
  • deps: update dependency astro to v4.12.3 (60c5b92)
  • deps: update dependency astro to v4.13.0 (ae016d4)
  • deps: update dependency astro to v4.13.1 (eda946f)
  • deps: update dependency astro to v4.13.2 (95f5e08)
  • deps: update dependency astro to v4.13.3 (0cd2543)
  • deps: update dependency astro to v4.13.4 (4a9b29d)
  • deps: update dependency astro to v4.14.0 (39f4753)
  • deps: update dependency astro to v4.14.2 (79ed5ad)
  • deps: update dependency astro to v4.14.3 (8273700)
  • deps: update dependency astro to v4.14.4 (8a86cf0)
  • deps: update dependency astro to v4.14.5 (e54c0d7)
  • deps: update dependency astro to v4.14.6 (06e9622)
  • deps: update dependency astro to v4.15.0 (92b466d)
  • deps: update dependency astro to v4.15.1 (4d820c7)
  • deps: update dependency astro to v4.15.10 (61de102)
  • deps: update dependency astro to v4.15.11 (02fa5c4)
  • deps: update dependency astro to v4.15.12 (62a1b89)
  • deps: update dependency astro to v4.15.2 (ec069a2)
  • deps: update dependency astro to v4.15.3 (d29ed39)
  • deps: update dependency astro to v4.15.4 (38cab6b)
  • deps: update dependency astro to v4.15.5 (f73d0cd)
  • deps: update dependency astro to v4.15.6 (3fa321f)
  • deps: update dependency astro to v4.15.7 (e866758)
  • deps: update dependency astro to v4.15.8 (7ed49b1)
  • deps: update dependency astro to v4.15.9 (69b6e77)
  • deps: update dependency astro to v4.16.0 (b50c728)
  • deps: update dependency astro to v4.16.1 (fda02a9)
  • deps: update dependency astro to v4.16.10 (18a9833)
  • deps: update dependency astro to v4.16.11 (#294) (e156830)
  • deps: update dependency astro to v4.16.12 (#295) (ea0ae05)
  • deps: update dependency astro to v4.16.13 (#296) (4aec3a0)
  • deps: update dependency astro to v4.16.14 (#303) (a0b5cce)
  • deps: update dependency astro to v4.16.15 (#307) (4e4e39a)
  • deps: update dependency astro to v4.16.16 (#309) (335ed5c)
  • deps: update dependency astro to v4.16.17 (#314) (934c7ed)
  • deps: update dependency astro to v4.16.18 (#323) (3dbb9cf)
  • deps: update dependency astro to v4.16.2 (eef092c)
  • deps: update dependency astro to v4.16.3 (3371fda)
  • deps: update dependency astro to v4.16.4 (3d76f2e)
  • deps: update dependency astro to v4.16.5 (329eb3e)
  • deps: update dependency astro to v4.16.6 (48de907)
  • deps: update dependency astro to v4.16.7 (320b27e)
  • deps: update dependency astro to v4.16.8 (7796d43)
  • deps: update dependency astro to v4.16.9 (bf81f93)
  • deps: update dependency sharp to v0.33.5 (1053b12)

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://36a7eb40.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 71b611e to 0a3e057 Compare July 25, 2024 16:50
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://fe0f01c4.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 0a3e057 to c111576 Compare July 25, 2024 22:45
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://917ae1b1.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 c111576 to 4aae869 Compare July 26, 2024 20:35
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://9a3f09f5.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 4aae869 to 9d9d583 Compare July 27, 2024 09:45
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://8443c6a6.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 9d9d583 to 865108d Compare July 29, 2024 15:20
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://35d2c04b.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 865108d to 48e6085 Compare July 29, 2024 15:22
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://ef5da6de.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 48e6085 to 365fa06 Compare July 30, 2024 19:51
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://85982612.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 365fa06 to 4c8c60e Compare July 31, 2024 13:31
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://224fce24.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 4c8c60e to 23e485e Compare July 31, 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://a4814dfa.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 23e485e to 9fca9f7 Compare August 1, 2024 12:53
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://bf145c65.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 9fca9f7 to 02143e8 Compare August 2, 2024 13:51
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://e93c5502.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 02143e8 to 8483900 Compare August 6, 2024 10: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://220a52f0.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 8483900 to c0826f2 Compare August 6, 2024 17:41
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://212d18ee.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 c0826f2 to 12cb55f Compare August 7, 2024 10:13
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://16bda73f.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 16e4082 to 8afcb0d Compare December 16, 2024 16:58
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://cd19744a.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 8afcb0d to 9801ab8 Compare December 17, 2024 16:38
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://030d9293.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 9801ab8 to 0f46905 Compare December 18, 2024 10:26
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://106bf321.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 0f46905 to fcb7077 Compare December 18, 2024 13:52
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://6576d302.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 fcb7077 to 4d49686 Compare December 19, 2024 14: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://8f2828a3.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 4d49686 to 91899e7 Compare December 20, 2024 17:39
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://01f97411.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 91899e7 to ae6e14e Compare December 21, 2024 06: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://1253c58c.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 ae6e14e to 9362a96 Compare December 24, 2024 00:26
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://8c6cb152.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 9362a96 to 56a102c Compare December 29, 2024 09:48
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://15632137.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 56a102c to f6de68b Compare December 30, 2024 18:23
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://6e4ac766.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 f6de68b to c3e2d31 Compare January 3, 2025 12:59
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://ec564bc9.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 c3e2d31 to 1984490 Compare January 5, 2025 18:04
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://a99f506f.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 1984490 to 0f38be3 Compare January 7, 2025 01:40
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://09fb104e.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 0f38be3 to c93e53f Compare January 7, 2025 16:47
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://d328ffad.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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants