Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.5.1

Patch Changes

• #14233 896886c Thanks @​gouravkhunger! - Fixes the issue with the option lastmod where if it is defined it applies correctly to <url> entries in each sitemap-${i}.xml file but not the <sitemap> entries in the root sitemap-index.xml file.

@​astrojs/sitemap@​3.5.0

Minor Changes

• #13682 5824b32 Thanks @​gouravkhunger! - Adds a customSitemaps option to include extra sitemaps in the sitemap-index.xml file generated by Astro.

  This is useful for multi-framework setups on the same domain as your Astro site (example.com), such as a blog at example.com/blog whose sitemap is generated by another framework.

  The following example shows configuring your Astro site to include sitemaps for an externally-generated blog and help center along with the generated sitemap entries in sitemap-index.xml:

  Example:

  import { defineConfig } from 'astro/config';
  import sitemap from '@astrojs/sitemap';
  export default defineConfig({
  site: 'https://example.com',
  integrations: [
  sitemap({
  customSitemaps: [
  'https://example.com/blog/sitemap.xml',
  'https://example.com/helpcenter/sitemap.xml',
  ],
  }),
  ],
  });
  

  Learn more in the @astrojs/sitemap configuration documentation.

@​astrojs/sitemap@​3.4.2

Patch Changes

• #14127 2309ada Thanks @​florian-lefebvre! - Upgrades zod

Sourced from @​astrojs/sitemap's changelog.

3.5.1

Patch Changes

• #14233 896886c Thanks @​gouravkhunger! - Fixes the issue with the option lastmod where if it is defined it applies correctly to <url> entries in each sitemap-${i}.xml file but not the <sitemap> entries in the root sitemap-index.xml file.

3.5.0

Minor Changes

• #13682 5824b32 Thanks @​gouravkhunger! - Adds a customSitemaps option to include extra sitemaps in the sitemap-index.xml file generated by Astro.

  This is useful for multi-framework setups on the same domain as your Astro site (example.com), such as a blog at example.com/blog whose sitemap is generated by another framework.

  The following example shows configuring your Astro site to include sitemaps for an externally-generated blog and help center along with the generated sitemap entries in sitemap-index.xml:

  Example:

  import { defineConfig } from 'astro/config';
  import sitemap from '@astrojs/sitemap';
  export default defineConfig({
  site: 'https://example.com',
  integrations: [
  sitemap({
  customSitemaps: [
  'https://example.com/blog/sitemap.xml',
  'https://example.com/helpcenter/sitemap.xml',
  ],
  }),
  ],
  });
  

  Learn more in the @astrojs/sitemap configuration documentation.

3.4.2

Patch Changes

• #14127 2309ada Thanks @​florian-lefebvre! - Upgrades zod

• d471be5 [ci] release (#14242)
• 896886c fix(@​astro/sitemap): include lastmod for sitemap entries (#14233)
• a186848 [ci] release (#14217)
• cad3cc6 [ci] format
• 5824b32 feat(@​astro/sitemap): custom sitemaps (#13682)
• c12e216 [ci] release (#14128)
• 2309ada chore: upgrade zod (#14127)
• 9cfccc7 [ci] format
• 33f2d15 chore: upgrade to Biome v2 (#13984)
• See full diff in compare view

Sourced from @​swup/astro's releases.

1.7.0

• Add support for replacing dynamic fragments
• Add option for native mode View Transitions
• Optimize client script when not using ignore option (@​aleclarson)

Sourced from @​swup/astro's changelog.

1.7.0

• Add support for replacing dynamic fragments
• Add option for native mode View Transitions
• Optimize client script when not using ignore option (@​aleclarson)

• b517654 Merge pull request #40 from swup/version/automated
• df64414 Update changelog
• 49c807e Update package version
• a8f8211 Merge pull request #39 from swup/feat/native
• 5457624 Merge pull request #38 from swup/feat/fragments
• 82e3cac Document native mode
• d5d56a1 Pass along native option
• f04af0e Export fragment plugin from client script
• 0a95106 Document fragments option
• d7e7798 Include fragment plugin
• Additional commits viewable in compare view

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)

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)

• 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

Sourced from overlayscrollbars's changelog.

2.12.0

Improvements

• Improve accessibility when the native scrollbars can't be hidden. This can happen when the browser isn't supporting scrollbar styling & the ScrollbarsHidingPlugin is not being used. In this case the custom scrollbars aren't rendered over the native scrollbars anymore. [SimpleBar #726](Grsmto/simplebar#726)

2.11.5

Bug Fixes

• Sometimes when resizing the window, scrollbars applied to the body element werent updated accordingly.

• b9ced78 v2.12.0
• 5dbe819 fix test
• 505c71e improve accessibility by hiding custom scrollbar when native scrollbars cant ...
• 99c1d97 Merge branch 'master' of https://github.com/KingSora/OverlayScrollbars
• ea0099e small improvements
• cb63671 changelog & package json
• 9fd1f8c fix a bug where the scrollbar size was not update on body scrollbars
• See full diff in compare view

Sourced from svelte's releases.

svelte@5.38.5

Patch Changes

• fix: ensure async deriveds always get dependencies from thennable (#16672)

svelte@5.38.3

Patch Changes

• fix: ensure correct order of template effect values (#16655)

• fix: allow async {@const} in more places (#16643)

• fix: properly catch top level await errors (#16619)

• perf: prune effects without dependencies (#16625)

• fix: only emit for_await_track_reactivity_loss in async mode (#16644)

svelte@5.38.2

Patch Changes

• perf: run blocks eagerly during flush instead of aborting (#16631)

• fix: don't clone non-proxies in $inspect (#16617)

• fix: avoid recursion error when tagging circular references (#16622)

svelte@5.38.1

Patch Changes

• fix: wrap abort in without_reactive_context (#16570)

• fix: add hint as a possible value for popover attribute (#16581)

• fix: skip effects inside dynamic component that is about to be destroyed (#16601)

svelte@5.38.0

Minor Changes

• feat: allow await inside @const declarations (#16542)

Patch Changes

• fix: remount at any hydration error (#16248)

• chore: emit await_reactivity_loss in for await loops (#16521)

• fix: emit snippet_invalid_export instead of undefined_export for exported snippets (#16539)

svelte@5.37.3

... (truncated)

Sourced from svelte's changelog.

5.38.5

Patch Changes

• fix: ensure async deriveds always get dependencies from thennable (#16672)

5.38.4

Patch Changes

• fix: place instance-level snippets inside async body (#16666)

• fix: Add check for builtin custom elements in set_custom_element_data (#16592)

• fix: restore batch along with effect context (#16668)

• fix: wait until changes propagate before updating input selection state (#16649)

• fix: add "Accept-CH" as valid value for http-equiv (#16671)

5.38.3

Patch Changes

• fix: ensure correct order of template effect values (#16655)

• fix: allow async {@const} in more places (#16643)

• fix: properly catch top level await errors (#16619)

• perf: prune effects without dependencies (#16625)

• fix: only emit for_await_track_reactivity_loss in async mode (#16644)

5.38.2

Patch Changes

• perf: run blocks eagerly during flush instead of aborting (#16631)

• fix: don't clone non-proxies in $inspect (#16617)

• fix: avoid recursion error when tagging circular references (#16622)

5.38.1

Patch Changes

• fix: wrap abort in without_reactive_context (#16570)

... (truncated)

• 5314f48 Version Packages (#16673)
• 5912754 Version Packages (#16667)
• 677af57 fix: ensure async deriveds always get dependencies from thennable (#16672)
• 967431c chore(elements.d.ts): add "Accept-CH" as valid value for http-equiv (#16671)
• 0d48916 fix: cursor jumps in input two way binding (#16649)
• 6534aa0 fix: Add check for builtin custom elements in set_custom_element_data (#16592)
• 7105736 fix: restore batch along with effect context (#16668)
• 57fed6a fix: place instance-level snippets inside async body (#16666)
• e883cd0 Version Packages (#16642)
• d3cb148 perf: better effect pruning (#16625)
• Additional commits viewable in compare view

Sourced from typescript's releases.

TypeScript 5.9

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)

Downloads are available on:

• npm

TypeScript 5.9 RC

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).

Downloads are available on:

• npm

TypeScript 5.9 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.9.0 (Beta).

Downloads are available on:

• npm

• be86783 Give more specific errors for verbatimModuleSyntax (#62113)
• 22ef577 LEGO: Pull request from lego/hb_5378966c-b857-470a-8675-daebef4a6da1_20250714...
• d5a414c Don't use noErrorTruncation when printing types with maximumLength set (#...
• f14b5c8 Remove unused and confusing dom.iterable.d.ts file (#62037)
• 2778e84 Restore AbortSignal.abort (#62086)
• 65cb4bd LEGO: Pull request from lego/hb_5378966c-b857-470a-8675-daebef4a6da1_20250710...
• 9e20e03 Clear out checker-level stacks on pop (#62016)
• 87740bc Fix for Issue 61081 (#61221)
• 833a8d4 Fix Symbol completion priority and cursor positioning (#61945)
• 0018c9f LEGO: Pull request from lego/hb_5378966c-b857-470a-8675-daebef4a6da1_20250702...
• Additional commits viewable in compare view

Sourced from @​biomejs/biome's releases.

Biome CLI v2.2.2

2.2.2

Patch Changes

• #7266 b270bb5 Thanks @​ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.

• #7281 6436180 Thanks @​ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

• #7285 1511d0c Thanks @​rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.

• #7249 dff85c0 Thanks @​ematipico! - Fixed #748, where Biome Language Server didn't show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.

• #7266 b270bb5 Thanks @​ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.

• #7209 679b70e Thanks @​patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

  Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

  Example

  // Before
  -      import "./sub/index";
  +      import "./sub/index/index.js";
  // After
  
  
   import "./sub/index";
  
  
  
  
  
   import "./sub/index.js";
  
  
  
  

• #7270 953f9c6 Thanks @​arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.

• #7234 b7aa111 Thanks @​JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().

  The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.

• #7283 0b07f45 Thanks @​ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.

• #7239 1d643d8 Thanks @​minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.

• #7264 62fdbc8 Thanks @​ematipico! - Fixed a regression where when using --log-kind-pretty wasn't working anymore as expected.

• #7244 660031b Thanks @​JeetuSuthar! - Fixed #7225: The noExtraBooleanCast rule now preserves parentheses when removing Boolean calls inside negations.

  // Before
  !Boolean(b0 && b1);
  // After
  !(b0 && b1); // instead of !b0 && b1
  

... (truncated)

Sourced from @​biomejs/biome's changelog.

2.2.2

Patch Changes

• #7266 b270bb5 Thanks @​ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.

• #7281 6436180 Thanks @​ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

• #7285 1511d0c Thanks @​rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.

• #7249 dff85c0 Thanks @​ematipico! - Fixed #748, where Biome Language Server didn't show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.

• #7266 b270bb5 Thanks @​ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.

• #7209 679b70e Thanks @​patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

  Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

  Example

  // Before
  -      import "./sub/index";
  +      import "./sub/index/index.js";
  // After
  
  
   import "./sub/index";
  
  
  
  
  
   import "./sub/index.js";
  
  
  
  

• #7270 953f9c6 Thanks @​arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.

• #7234 b7aa111 Thanks @​JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().

  The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.

• #7283 0b07f45 Thanks @​ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.

• #7239 1d643d8 Thanks @​minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.

• #7264 62fdbc8 Thanks @​ematipico! - Fixed a regression where when using --log-kind-pretty wasn't working anymore as expected.

• #7244 660031b Thanks @​JeetuSuthar! - Fixed #7225: The noExtraBooleanCast rule now preserves parentheses when removing Boolean calls inside negations.

  // Before
  !Boolean(b0 && b1);
  // After
  !(b0 && b1); // instead of !b0 && b1
  

... (truncated)

• dcdd819 ci: release (#7303)
• 7886c98 chore: remove changeset, fix version number
• 941cd73 chore: revert version number
• 0f5fb2f ci: release (#7238)
• 27c93e8 docs: fix CHANGELOG to reflect operatorLinebreak (#7253)
• 38795eb chore: fix image sponsor (#7250)
• 1075b73 fix(changelog): correct dead links in 2.2 (#7243)
• e1ba03c chore: restore version and use different runner
• 1b783c8 chore: revert version
• ee7ec19 chore: update version and lockfile
• Additional commits viewable in compare view

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