Bump the patch-updates group across 1 directory with 4 updates

[dependabot]

Bumps the patch-updates group with 4 updates in the / directory: @iconify-json/material-symbols, astro, @biomejs/biome and postcss-import.

Updates @iconify-json/material-symbols from 1.2.26 to 1.2.28

Commits

• See full diff in compare view

Updates astro from 5.10.0 to 5.10.2

Release notes

Sourced from astro's releases.

astro@5.10.2

Patch Changes

• #14000 3cbedae Thanks @​feelixe! - Fix routePattern JSDoc examples to show correct return values

• #13990 de6cfd6 Thanks @​isVivek99! - Fixes a case where astro:config/client and astro:config/server virtual modules would not contain config passed to integrations updateConfig() during the build

• #14019 a160d1e Thanks @​ascorbic! - Removes the requirement to set type: 'live' when defining experimental live content collections

  Previously, live collections required a type and loader configured. Now, Astro can determine that your collection is a live collection without defining it explicitly.

  This means it is now safe to remove type: 'live' from your collections defined in src/live.config.ts:

  import { defineLiveCollection } from 'astro:content';
  import { storeLoader } from '@mystore/astro-loader';
  const products = defineLiveCollection({
  
  type: 'live',
  loader: storeLoader({
  apiKey: process.env.STORE_API_KEY,
  endpoint: 'https://api.mystore.com/v1',
  }),
  });
  
  export const collections = { products };

  This is not a breaking change: your existing live collections will continue to work even if you still include type: 'live'. However, we suggest removing this line at your earliest convenience for future compatibility when the feature becomes stable and this config option may be removed entirely.

• #13966 598da21 Thanks @​msamoylov! - Fixes a broken link on the default 404 page in development

astro@5.10.1

Patch Changes

• #13988 609044c Thanks @​ascorbic! - Fixes a bug in live collections that caused it to incorrectly complain about the collection being defined in the wrong file

• #13909 b258d86 Thanks @​isVivek99! - Fixes rendering of special boolean attributes for custom elements

• #13983 e718375 Thanks @​florian-lefebvre! - Fixes a case where the toolbar audit would incorrectly flag images processed by Astro in content collections documents

• #13999 f077b68 Thanks @​ascorbic! - Adds lastModified field to experimental live collection cache hints

  Live loaders can now set a lastModified field in the cache hints for entries and collections to indicate when the data was last modified. This is then available in the cacheHint field returned by getCollection and getEntry.

• #13987 08f34b1 Thanks @​ematipico! - Adds an informative message in dev mode when the CSP feature is enabled.

• #14005 82aad62 Thanks @​ematipico! - Fixes a bug where inline styles and scripts didn't work when CSP was enabled. Now when adding <styles> elements inside an Astro component, their hashes care correctly computed.

• #13985 0b4c641 Thanks @​jsparkdev! - Updates wrong link

Changelog

Sourced from astro's changelog.

5.10.2

Patch Changes

• #14000 3cbedae Thanks @​feelixe! - Fix routePattern JSDoc examples to show correct return values

• #13990 de6cfd6 Thanks @​isVivek99! - Fixes a case where astro:config/client and astro:config/server virtual modules would not contain config passed to integrations updateConfig() during the build

• #14019 a160d1e Thanks @​ascorbic! - Removes the requirement to set type: 'live' when defining experimental live content collections

  Previously, live collections required a type and loader configured. Now, Astro can determine that your collection is a live collection without defining it explicitly.

  This means it is now safe to remove type: 'live' from your collections defined in src/live.config.ts:

  import { defineLiveCollection } from 'astro:content';
  import { storeLoader } from '@mystore/astro-loader';
  const products = defineLiveCollection({
  
  type: 'live',
  loader: storeLoader({
  apiKey: process.env.STORE_API_KEY,
  endpoint: 'https://api.mystore.com/v1',
  }),
  });
  
  export const collections = { products };

  This is not a breaking change: your existing live collections will continue to work even if you still include type: 'live'. However, we suggest removing this line at your earliest convenience for future compatibility when the feature becomes stable and this config option may be removed entirely.

• #13966 598da21 Thanks @​msamoylov! - Fixes a broken link on the default 404 page in development

5.10.1

Patch Changes

• #13988 609044c Thanks @​ascorbic! - Fixes a bug in live collections that caused it to incorrectly complain about the collection being defined in the wrong file

• #13909 b258d86 Thanks @​isVivek99! - Fixes rendering of special boolean attributes for custom elements

• #13983 e718375 Thanks @​florian-lefebvre! - Fixes a case where the toolbar audit would incorrectly flag images processed by Astro in content collections documents

• #13999 f077b68 Thanks @​ascorbic! - Adds lastModified field to experimental live collection cache hints

  Live loaders can now set a lastModified field in the cache hints for entries and collections to indicate when the data was last modified. This is then available in the cacheHint field returned by getCollection and getEntry.

• #13987 08f34b1 Thanks @​ematipico! - Adds an informative message in dev mode when the CSP feature is enabled.

• #14005 82aad62 Thanks @​ematipico! - Fixes a bug where inline styles and scripts didn't work when CSP was enabled. Now when adding <styles> elements inside an Astro component, their hashes care correctly computed.

... (truncated)

Commits

• 5891056 [ci] release (#14007)
• 508e6bf [ci] format
• a160d1e Make "type" optional when defining live collections (#14019)
• 041a37d [ci] format
• 33f2d15 chore: upgrade to Biome v2 (#13984)
• f9ffd3c [ci] format
• de6cfd6 fix client/server config changes in the integrations object during setup (#13...
• 598da21 Fix broken documentation link (#13966)
• 3cbedae fix invalid examples in Astro.routePattern docstring (#14000)
• e7df795 [ci] format
• Additional commits viewable in compare view

Updates @biomejs/biome from 2.0.0 to 2.0.6

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.0.6

2.0.6

Patch Changes

• #6557 fd68458 Thanks @​ematipico! - Fixed a bug where Biome didn't provide all the available code actions when requested by the editor.

• #6511 72623fa Thanks @​Conaclos! - Fixed #6492. The organizeImports assist action no longer duplicates a comment at the start of the file when :BLANK_LINE: precedes the first import group.

• #6557 fd68458 Thanks @​ematipico! - Fixed #6287 where Biome Language Server didn't adhere to the settings.requireConfiguration option when pulling diagnostics and code actions. Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.

• #6551 0b63b1d Thanks @​Conaclos! - Fixed #6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.

• #6503 9a8fe0f Thanks @​ematipico! - Fixed #6482 where nursery rules that belonged to a domain were incorrectly enabled.

• #6565 e85761c Thanks @​daivinhtran! - Fixed #4677: Now the noUnusedImports rule won't produce diagnostics for types used in JSDoc comment of exports.

• #6166 b8cbd83 Thanks @​mehm8128! - Added the nursery rule noExcessiveLinesPerFunction. This rule restrict a maximum number of lines of code in a function body.

  The following code is now reported as invalid when the limit of maximum lines is set to 2:

  function foo() {
    const x = 0;
    const y = 1;
    const z = 2;
  }

  The following code is now reported as valid when the limit of maximum lines is set to 3:

  const bar = () => {
    const x = 0;
    const z = 2;
  };

• #6553 5f42630 Thanks @​denbezrukov! - Fixed #6547. Now the Biome CSS parser correctly parses @starting-style when it's used inside other at-rules. The following example doesn't raise an error anymore:

  @layer my-demo-layer {
    @starting-style {
      div.showing {
        background-color: red;

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.0.6

Patch Changes

• #6557 fd68458 Thanks @​ematipico! - Fixed a bug where Biome didn't provide all the available code actions when requested by the editor.

• #6511 72623fa Thanks @​Conaclos! - Fixed #6492. The organizeImports assist action no longer duplicates a comment at the start of the file when :BLANK_LINE: precedes the first import group.

• #6557 fd68458 Thanks @​ematipico! - Fixed #6287 where Biome Language Server didn't adhere to the settings.requireConfiguration option when pulling diagnostics and code actions. Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.

• #6551 0b63b1d Thanks @​Conaclos! - Fixed #6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.

• #6503 9a8fe0f Thanks @​ematipico! - Fixed #6482 where nursery rules that belonged to a domain were incorrectly enabled.

• #6565 e85761c Thanks @​daivinhtran! - Fixed #4677: Now the noUnusedImports rule won't produce diagnostics for types used in JSDoc comment of exports.

• #6166 b8cbd83 Thanks @​mehm8128! - Added the nursery rule noExcessiveLinesPerFunction. This rule restrict a maximum number of lines of code in a function body.

  The following code is now reported as invalid when the limit of maximum lines is set to 2:

  function foo() {
    const x = 0;
    const y = 1;
    const z = 2;
  }

  The following code is now reported as valid when the limit of maximum lines is set to 3:

  const bar = () => {
    const x = 0;
    const z = 2;
  };

• #6553 5f42630 Thanks @​denbezrukov! - Fixed #6547. Now the Biome CSS parser correctly parses @starting-style when it's used inside other at-rules. The following example doesn't raise an error anymore:

  @layer my-demo-layer {
    @starting-style {
      div.showing {
        background-color: red;
      }
    }

... (truncated)

Commits

• a69bbe8 ci: release (#6507)
• 6a24bd9 chore: link packages differently (#6558)
• f62e748 feat(lint): implement noImplicitCoercion rule (#6395)
• e128ea9 feat(lint): no-alert rule (#6355)
• 5705f1a feat(lint): implement useUnifiedTypeSignature rule (#6320)
• a3a3715 feat(linter): implement noUnassignedVariables rule (#6219)
• b8cbd83 feat(biome_js_analyze): implement noExcessiveLinesPerFunction (#6166)
• 09f49ba ci: release (#6467)
• 4209030 chore: update vscode badges (#6468)
• c939e54 chore: fix invalid link in CHANGELOG.md
• Additional commits viewable in compare view

Updates postcss-import from 16.1.0 to 16.1.1

Changelog

Sourced from postcss-import's changelog.

16.1.1 / 2025-06-17

• Fix incorrect cascade layer order when some resources can not be inlined (#567, #574)

Commits

• 4ae9894 16.1.1
• a3f3889 Test on modern Node versions (#577)
• 10325fc Upgrade eslint & config; use flat config (#576)
• 9227642 Migrate config renovate.json (#575)
• 2544155 Update dependency prettier to ~3.5.0 (#572)
• 83108aa Fix incorrect cascade layer order when some resources can not be inlined (#574)
• cad0022 Update dependency sugarss to v5 (#568)
• 32deb08 Update dependency c8 to v10 (#565)
• d43ca15 Update dependency prettier to ~3.4.0 (#569)
• 9af465e Update dependency prettier to ~3.3.0 (#564)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by romainmenke, a new releaser for postcss-import 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 <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]

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