Bump astro and @astrojs/svelte

[dependabot]

Bumps astro and @astrojs/svelte. These dependencies needed to be updated together.
Updates astro from 3.6.5 to 5.13.3

Release notes

Sourced from astro's releases.

astro@5.13.3

Patch Changes

• #14239 d7d93e1 Thanks @​wtchnm! - Fixes a bug where the types for the live content collections were not being generated correctly in dev mode

• #14221 eadc9dd Thanks @​delucis! - Fixes JSON schema support for content collections using the file() loader

• #14229 1a9107a Thanks @​jonmichaeldarby! - Ensures Astro.currentLocale returns the correct locale during SSG for pages that use a locale param (such as [locale].astro or [locale]/index.astro, which produce [locale].html)

astro@5.13.2

Patch Changes

• 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

• Updated dependencies [4d16de7]:

  • @​astrojs/internal-helpers@​0.7.2
  • @​astrojs/markdown-remark@​6.3.6

astro@5.13.1

Patch Changes

• #14225 f2490ab Thanks @​delucis! - Fixes the experimental.chromeDevtoolsWorkspace feature.

astro@5.13.0

Minor Changes

• #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

  Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

  However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

  The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

  Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

  The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

  To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

  // astro.config.mjs
  import { defineConfig } from "astro/config";
  export default defineConfig({
  
  experimental: {
  staticImportMetaEnv: true
  
  
  rawEnvValues: false
  
  
  }
  });

... (truncated)

Changelog

Sourced from astro's changelog.

5.13.3

Patch Changes

• #14239 d7d93e1 Thanks @​wtchnm! - Fixes a bug where the types for the live content collections were not being generated correctly in dev mode

• #14221 eadc9dd Thanks @​delucis! - Fixes JSON schema support for content collections using the file() loader

• #14229 1a9107a Thanks @​jonmichaeldarby! - Ensures Astro.currentLocale returns the correct locale during SSG for pages that use a locale param (such as [locale].astro or [locale]/index.astro, which produce [locale].html)

5.13.2

Patch Changes

• 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

• Updated dependencies [4d16de7]:

  • @​astrojs/internal-helpers@​0.7.2
  • @​astrojs/markdown-remark@​6.3.6

5.13.1

Patch Changes

• #14225 f2490ab Thanks @​delucis! - Fixes the experimental.chromeDevtoolsWorkspace feature.

5.13.0

Minor Changes

• #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

  Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

  However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

  The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

  Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

  The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

  To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

  // astro.config.mjs
  import { defineConfig } from "astro/config";
  export default defineConfig({
  
  experimental: {

... (truncated)

Commits

• d471be5 [ci] release (#14242)
• d7d93e1 fix(sync): add missing live check for generating content collections types (#...
• 682d8b8 [ci] format
• 1a9107a Properly compute currentLocale when path segment contains .html (#14229)
• eadc9dd Fix file() loader JSON schema (#14221)
• d95fbaf [ci] format
• dd481c8 chore(assets): compose source URL later (#14237)
• 9288133 [ci] release (#14232)
• 1040510 [ci] format
• 4d16de7 Merge commit from fork
• Additional commits viewable in compare view

Updates @astrojs/svelte from 4.0.4 to 7.1.0

Release notes

Sourced from @​astrojs/svelte's releases.

@​astrojs/netlify@​6.5.8

Patch Changes

• #14240 77b18fb Thanks @​delucis! - Increases the minimum supported version of Astro to 5.7.0

• Updated dependencies []:

  • @​astrojs/underscore-redirects@​1.0.0

@​astrojs/netlify@​6.5.7

Patch Changes

• Updated dependencies [4d16de7]:
  • @​astrojs/internal-helpers@​0.7.2
  • @​astrojs/underscore-redirects@​1.0.0

@​astrojs/netlify@​6.5.6

Patch Changes

• #14175 1e1cef0 Thanks @​ematipico! - Fixes a bug where the adapter would cause a runtime error when calling astro build in CI environments.

@​astrojs/netlify@​6.5.5

Patch Changes

• Updated dependencies [0567fb7]:
  • @​astrojs/internal-helpers@​0.7.1
  • @​astrojs/underscore-redirects@​1.0.0

@​astrojs/netlify@​6.5.4

Patch Changes

• Updated dependencies [f4e8889]:
  • @​astrojs/internal-helpers@​0.7.0
  • @​astrojs/underscore-redirects@​1.0.0

@​astrojs/netlify@​6.5.3

Patch Changes

• #14120 798b5fa Thanks @​ascorbic! - Adds mock feature flags in dev

• Updated dependencies []:

  • @​astrojs/underscore-redirects@​1.0.0

@​astrojs/netlify@​6.5.2

Patch Changes

• #14103 69d6871 Thanks @​ascorbic! - Upgrades Netlify Vite plugin to fix error in edge functions.

• Updated dependencies []:

  • @​astrojs/underscore-redirects@​1.0.0

... (truncated)

Changelog

Sourced from @​astrojs/svelte's changelog.

7.1.0

Minor Changes

• #13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

  Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

  ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

7.0.13

Patch Changes

• #13731 c3e80c2 Thanks @​jsparkdev! - update vite to latest version for fixing CVE

7.0.12

Patch Changes

• #13720 e1cd1ae Thanks @​florian-lefebvre! - Fixes SSR renderer type

7.0.11

Patch Changes

• #13663 a19a185 Thanks @​florian-lefebvre! - Improves type-safety of renderers

7.0.10

Patch Changes

• #13596 3752519 Thanks @​jsparkdev! - update vite to latest version to fix CVE

• #13547 360cb91 Thanks @​jsparkdev! - Updates vite to the latest version

7.0.9

Patch Changes

• #13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

7.0.8

Patch Changes

• #13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

7.0.7

... (truncated)

Commits

• 3632dda [ci] release (#13840)
• 3c3b492 fix: increase minimum Node version to 18.20.8 (#13809)
• bbfaf98 fix(deps): update astro client runtimes (#13822)
• f8cec06 fix(deps): update astro client runtimes (#13748)
• bfea0fb [ci] release (#13733)
• c3e80c2 fix(vite): update vite to latest version (#13731)
• d2ab7db [ci] release (#13721)
• e1cd1ae fix: renderers types (#13720)
• 21ca490 fix(deps): update dependency vite to ^6.3.3 (#13699)
• bd5d18f fix(deps): update astro client runtimes (#13661)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by matthewp, a new releaser for @​astrojs/svelte since your current version.

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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[cloudflare-workers-and-pages]

Deploying exam-timekeeper with    Cloudflare Pages

Latest commit:	f91ed9e
Status:	🚫  Build failed.

View logs

[cloudflare-workers-and-pages]

Deploying timekeeper with    Cloudflare Pages

Latest commit:	f91ed9e
Status:	🚫  Build failed.

View logs

[dependabot]

Superseded by #63.