Skip to content

chore(deps): bump the minor-updates group across 1 directory with 6 updates#15

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot-npm_and_yarn-minor-updates-f3f2d3d9f3
Closed

chore(deps): bump the minor-updates group across 1 directory with 6 updates#15
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot-npm_and_yarn-minor-updates-f3f2d3d9f3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 15, 2025 •
edited
Loading

Copy link
Copy Markdown

Bumps the minor-updates group with 6 updates in the / directory:

Package From To
@astrojs/sitemap 3.4.1 3.5.0
@swup/astro 1.6.0 1.7.0
astro 5.10.1 5.13.0
svelte 5.34.8 5.38.1
typescript 5.8.3 5.9.2
@biomejs/biome 2.0.5 2.2.0

Updates @astrojs/sitemap from 3.4.1 to 3.5.0

Release notes

Sourced from @​astrojs/sitemap's releases.

@​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

Changelog

Sourced from @​astrojs/sitemap's changelog.

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

Commits

Updates @swup/astro from 1.6.0 to 1.7.0

Release notes

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)
Changelog

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)
Commits

Updates astro from 5.10.1 to 5.13.0

Release notes

Sourced from astro's releases.

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


}
});

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.ENABLED;
+ const enabled: boolean = import.meta.env.ENABLED === "true";

If you were relying on the transformation into process.env calls, you may need to update your project code to apply it manually:

// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.DB_PASSWORD;
+ const enabled: boolean = process.env.DB_PASSWORD;

You may also need to update types:








... (truncated)





Changelog

Sourced from astro's changelog.




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


}
});
    • 



Updating your project


If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:


// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.ENABLED;
+ const enabled: boolean = import.meta.env.ENABLED === "true";


If you were relying on the transformation into process.env calls, you may need to update your project code to apply it manually:


// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.DB_PASSWORD;
+ const enabled: boolean = process.env.DB_PASSWORD;


You may also need to update types:







... (truncated)





Commits






Updates svelte from 5.34.8 to 5.38.1



Release notes

Sourced from svelte's releases.




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


Patch Changes


    

  • fix: reset attribute cache after setting corresponding property (#16543)
    • 



svelte@5.37.2


Patch Changes


    

  • 

    fix: double event processing in firefox due to event object being garbage collected (#16527)
    

    • 

  • 

    fix: add bindable dimension attributes types to SVG and MathML elements (#16525)
    

    • 

  • 

    fix: correctly differentiate static fields before emitting duplicate_class_field (#16526)
    

    • 

  • 

    fix: prevent last_propagated_event from being DCE'd (#16538)
    

    • 



svelte@5.37.1


Patch Changes


    

  • 

    chore: remove some todos (#16515)
    

    • 

  • 

    fix: allow await expressions inside {#await ...} argument (#16514)
    

    • 

  • 

    fix: append_styles in an effect to make them available on mount (#16509)
    

    • 

  • 

    chore: remove parser.template_untrimmed (#16511)
    

    • 

  • 

    fix: always inject styles when compiling as a custom element (#16509)
    

    • 






... (truncated)





Changelog

Sourced from svelte's changelog.




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)
    

    • 



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)
    

    • 



5.37.3


Patch Changes


    

  • fix: reset attribute cache after setting corresponding property (#16543)
    • 



5.37.2


Patch Changes


    

  • 

    fix: double event processing in firefox due to event object being garbage collected (#16527)
    

    • 

  • 

    fix: add bindable dimension attributes types to SVG and MathML elements (#16525)
    

    • 

  • 

    fix: correctly differentiate static fields before emitting duplicate_class_field (#16526)
    

    • 

  • 

    fix: prevent last_propagated_event from being DCE'd (#16538)
    

    • 



5.37.1


Patch Changes


    

  • 

    chore: remove some todos (#16515)
    

    • 

  • 

    fix: allow await expressions inside {#await ...} argument (#16514)
    

    • 






... (truncated)





Commits






Updates typescript from 5.8.3 to 5.9.2



Release notes

Sourced from typescript's releases.




TypeScript 5.9


For release notes, check out the release announcement



Downloads are available on:



TypeScript 5.9 RC


For release notes, check out the release announcement



Downloads are available on:



TypeScript 5.9 Beta


For release notes, check out the release announcement.



Downloads are available on:








Commits

    

  • 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
    • 







Updates @biomejs/biome from 2.0.5 to 2.2.0



Release notes

Sourced from @​biomejs/biome's releases.




Biome CLI v2.2.0


2.2.0


Minor Changes


    

  • 

    #5506 1f8755b Thanks @​sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.
    

    You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.
    

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}
    

    Invalid examples
    

    import foo from "import-foo/foo";
import bar from "import-foo/bar";
    

    Valid examples
    

    import baz from "import-foo/baz";
    

    Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions.
The following example restricts the import names that match x , y or z letters from modules under import-foo/.
    

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}
    

    • 






... (truncated)





Changelog

Sourced from @​biomejs/biome's changelog.




2.2.0


Minor Changes


    

  • 

    #5506 1f8755b Thanks @​sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.
    

    You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.
    

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}
    

    Invalid examples
    

    import foo from "import-foo/foo";
import bar from "import-foo/bar";
    

    Valid examples
    

    import baz from "import-foo/baz";
    

    Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions.
The following example restricts the import names that match x , y or z letters from modules under import-foo/.
    

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}
    

    • 






... (truncated)





Commits






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
    • 




    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          chore(deps): bump the minor-updates group across 1 directory with 6 u…
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          117cefe
        
      

    

  

    

      
…pdates

Bumps the minor-updates group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@astrojs/sitemap](https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap) | `3.4.1` | `3.5.0` |
| [@swup/astro](https://github.com/swup/astro) | `1.6.0` | `1.7.0` |
| [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `5.10.1` | `5.13.0` |
| [svelte](https://github.com/sveltejs/svelte/tree/HEAD/packages/svelte) | `5.34.8` | `5.38.1` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.8.3` | `5.9.2` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.0.5` | `2.2.0` |



Updates `@astrojs/sitemap` from 3.4.1 to 3.5.0
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/sitemap/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/sitemap@3.5.0/packages/integrations/sitemap)

Updates `@swup/astro` from 1.6.0 to 1.7.0
- [Release notes](https://github.com/swup/astro/releases)
- [Changelog](https://github.com/swup/astro/blob/master/CHANGELOG.md)
- [Commits](swup/astro@1.6.0...1.7.0)

Updates `astro` from 5.10.1 to 5.13.0
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/astro@5.13.0/packages/astro)

Updates `svelte` from 5.34.8 to 5.38.1
- [Release notes](https://github.com/sveltejs/svelte/releases)
- [Changelog](https://github.com/sveltejs/svelte/blob/main/packages/svelte/CHANGELOG.md)
- [Commits](https://github.com/sveltejs/svelte/commits/svelte@5.38.1/packages/svelte)

Updates `typescript` from 5.8.3 to 5.9.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release-publish.yml)
- [Commits](microsoft/TypeScript@v5.8.3...v5.9.2)

Updates `@biomejs/biome` from 2.0.5 to 2.2.0
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.2.0/packages/@biomejs/biome)

---
updated-dependencies:
- dependency-name: "@astrojs/sitemap"
  dependency-version: 3.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@swup/astro"
  dependency-version: 1.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: astro
  dependency-version: 5.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: svelte
  dependency-version: 5.38.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: typescript
  dependency-version: 5.9.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@biomejs/biome"
  dependency-version: 2.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-updates
...

Signed-off-by: dependabot[bot] <support@github.com>

    







  








      

  
            

    

      
    

    


      


          @dependabot
dependabot
Bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  javascript

  Pull requests that update javascript code

  labels


      Aug 15, 2025

    

  








      

  
      



  

  @dependabot


    @github




  



    

      

  

    

      
          
      

      
            dependabot
  Bot

      

      

      commented

        on behalf of github

        Aug 18, 2025



      
    


  


  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

              
  
      
                Copy Markdown

  

        
      

    


    

        



        

  Author


    

  





      


        



  
    

      
          
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.


      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
      



  

  @dependabot


    @github




  



    

      

  

    

      
          
      

      
            dependabot
  Bot

      

      

      commented

        on behalf of github

        Aug 27, 2025



      
    


  


  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

              
  
      
                Copy Markdown

  

        
      

    


    

        



        

  Author


    

  





      


        



  
    

      
          
Looks like these dependencies are updatable in another way, so this is no longer needed.


      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
            

    

      
    

    


      


          @dependabot
dependabot
Bot



          closed this


      Aug 27, 2025

    

  


    


  

  
  

  
      @dependabot
  dependabot
Bot

    
    deleted the
    
      
        dependabot-npm_and_yarn-minor-updates-f3f2d3d9f3
    
    branch

    August 27, 2025 04:54    
    













  
  

    

      

  










  








  
      

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  










      

  

    
    

    

  

    Reviewers
  


    

    No reviews




  




    

  


      
  

    Assignees
  



        


    No one assigned







      


  


  

    Labels
  



    

      

    dependencies

  Pull requests that update a dependency file
  

    javascript

  Pull requests that update javascript code








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
  

    Development
  



            


Successfully merging this pull request may close these issues.





  
  



      
    

  




      

    

  
        

  

    

      0 participants