Bump the all group with 2 updates

[dependabot]

Bumps the all group with 2 updates: astro and sanity.

Updates astro from 4.15.1 to 4.15.4

Release notes

Sourced from astro's releases.

[email protected]

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

[email protected]

Patch Changes

• #11902 d63bc50 Thanks @​ascorbic! - Fixes case where content layer did not update during clean dev builds on Linux and Windows

• #11886 7ff7134 Thanks @​matthewp! - Fixes a missing error message when actions throws during astro sync

• #11904 ca54e3f Thanks @​wtchnm! - perf(assets): avoid downloading original image when using cache

[email protected]

Patch Changes

• #11870 8e5257a Thanks @​ArmandPhilippot! - Fixes typo in documenting the fallbackType property in i18n routing

• #11884 e450704 Thanks @​ascorbic! - Correctly handles content layer data where the transformed value does not match the input schema

• #11900 80b4a18 Thanks @​delucis! - Fixes the user-facing type of the new i18n.routing.fallbackType option to be optional

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

4.15.3

Patch Changes

• #11902 d63bc50 Thanks @​ascorbic! - Fixes case where content layer did not update during clean dev builds on Linux and Windows

• #11886 7ff7134 Thanks @​matthewp! - Fixes a missing error message when actions throws during astro sync

• #11904 ca54e3f Thanks @​wtchnm! - perf(assets): avoid downloading original image when using cache

4.15.2

Patch Changes

• #11870 8e5257a Thanks @​ArmandPhilippot! - Fixes typo in documenting the fallbackType property in i18n routing

• #11884 e450704 Thanks @​ascorbic! - Correctly handles content layer data where the transformed value does not match the input schema

• #11900 80b4a18 Thanks @​delucis! - Fixes the user-facing type of the new i18n.routing.fallbackType option to be optional

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)
• 65bfefb [ci] release (#11909)
• ca54e3f perf(astro/assets): avoid downloading original image when using cache (#11904)
• 5d7bc70 [ci] format
• 7ff7134 Provide an error message when Actions throws in setup (#11886)
• f696051 [ci] format
• Additional commits viewable in compare view

Updates sanity from 3.56.0 to 3.57.1

Release notes

Sourced from sanity's releases.

v3.57.1

🐛 Notable bugfixes

• Fixes a performance regression introduced in v3.51.0 (#7471)

Install or upgrade Sanity Studio

To initiate a new Sanity Studio project or upgrade an existing one, please refer to our comprehensive guide on Installing and Upgrading Sanity Studio.

If you are updating from a version earlier than 3.37.0, you should also check out this article to ensure your dependencies are up to date.

📓 Full changelog

Author	Message	Commit
Rico Kahler	fix(core): ensure all keys are reconciled	6393df8

v3.57.0

✨ Highlights

Significant rendering perf. improvements (up to x10) in dev mode

This change enables styled-components "speedy mode" in sanity dev, improving developer mode performance. This change impacts only development builds (sanity dev) – production builds (sanity build or sanity start) remain unaffected since "speedy mode" has always been enabled in production.

Developers embedding Sanity Studio in other frameworks like Next.js or Remix need to adjust their own build tooling to declare the SC_DISABLE_SPEEDY flag to achieve the same performance benefits. For example, Next.js users can add this snippet to their next.config.{js,mjs,ts} file:

export default {
  env: {
    SC_DISABLE_SPEEDY: 'false' // makes styled-components as fast in dev mode as it is in production mode
  }
}

For Safari users, while they will still be able to inspect and see CSS rules coming from styled-components, these will now be read-only in the DevTools inspector. The performance benefits from enabling "speedy mode" in development mode are significant for Safari users and outweigh the convenience of being able to edit these rules directly in the inspector. With Hot Module Reload, developers can still quickly make changes to their source code, and the new styles will apply immediately.

Enabling "speedy mode" offers a faster development experience across the board. Developers using Safari for testing purposes can still verify the functionality of the studio, and for more detailed CSS editing, they can switch to Chrome, Firefox, or other Chromium-based browsers like Arc or Brave.

It's still possible to restore the old behaviour of disabling speedy in dev mode in userland with a custom sanity.cli.ts override:

import {defineCliConfig} from 'sanity/cli'
import {type UserConfig} from 'vite'
export default defineCliConfig({

vite(viteConfig: UserConfig): UserConfig {

return {

...viteConfig,

define: {

...viteConfig.define,

</tr></table>

... (truncated)

Commits

• 22e2cfb v3.57.1
• 6393df8 fix(core): ensure all keys are reconciled
• 0587ee5 v3.57.0
• 85b0538 feat(cli): allow setting --max-fetch-concurrency to prevent stalled validat...
• 8bc721b chore: support for sticky params in URL and intent ops (#7429)
• 5ebff0d fix(deps): update dependency @​portabletext/editor to ^1.0.19 (#7405)
• c5a4207 chore(deps): update dependency styled-components to ^6.1.13 (#7442)
• 713c3f9 test(sanity): skip toolbar test (#7446)
• deca138 chore: improved data testing by ui and test id (#7428)
• 9da634e chore(core): single addon dataset context (#7432)
• Additional commits viewable 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions