chore(deps): bump astro from 4.15.3 to 4.15.4

[dependabot]

Bumps astro from 4.15.3 to 4.15.4.

Release notes

Sourced from astro's releases.

astro@4.15.4

Patch Changes

• #11879 bd1d4aa Thanks @​matthewp! - Allow passing a cryptography key via ASTRO_KEY

  For Server islands Astro creates a cryptography key in order to hash props for the islands, preventing accidental leakage of secrets.

  If you deploy to an environment with rolling updates then there could be multiple instances of your app with different keys, causing potential key mismatches.

  To fix this you can now pass the ASTRO_KEY environment variable to your build in order to reuse the same key.

  To generate a key use:

  astro create-key
  

  This will print out an environment variable to set like:

  ASTRO_KEY=PIAuyPNn2aKU/bviapEuc/nVzdzZPizKNo3OqF/5PmQ=
  

• #11935 c58193a Thanks @​Princesseuh! - Fixes astro add not using the proper export point when adding certain adapters

Changelog

Sourced from astro's changelog.

4.15.4

Patch Changes

• #11879 bd1d4aa Thanks @​matthewp! - Allow passing a cryptography key via ASTRO_KEY

  For Server islands Astro creates a cryptography key in order to hash props for the islands, preventing accidental leakage of secrets.

  If you deploy to an environment with rolling updates then there could be multiple instances of your app with different keys, causing potential key mismatches.

  To fix this you can now pass the ASTRO_KEY environment variable to your build in order to reuse the same key.

  To generate a key use:

  astro create-key
  

  This will print out an environment variable to set like:

  ASTRO_KEY=PIAuyPNn2aKU/bviapEuc/nVzdzZPizKNo3OqF/5PmQ=
  

• #11935 c58193a Thanks @​Princesseuh! - Fixes astro add not using the proper export point when adding certain adapters

Commits

• 0d50d75 [ci] release (#11936)
• c0c9645 [ci] format
• bd1d4aa Allow passing into the crypto key via ASTRO_KEY (#11879)
• 4a44e82 fix: explicitly check for null props in serializeSignals (#11930)
• c58193a fix(add): Use proper export names when adding adapters (#11935)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
main-branch-openresource-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 9, 2024 7:07am