Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 26, 2026

Bumps the patch-updates group with 5 updates in the / directory:

Package From To
@fancyapps/ui 6.1.8 6.1.9
@iconify-json/material-symbols 1.2.52 1.2.53
astro 5.16.12 5.16.15
katex 0.16.27 0.16.28
@biomejs/biome 2.3.11 2.3.13

Updates @fancyapps/ui from 6.1.8 to 6.1.9

Release notes

Sourced from @​fancyapps/ui's releases.

v6.1.9

Please refer to CHANGELOG.md for details.

Changelog

Sourced from @​fancyapps/ui's changelog.

6.1.9 (2026-01-23)

Features

  • Fancybox Add slug option to Hash plugin (821)
Commits

Updates @iconify-json/material-symbols from 1.2.52 to 1.2.53

Commits

Updates astro from 5.16.12 to 5.16.15

Release notes

Sourced from astro's releases.

astro@5.16.15

Patch Changes

  • #15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

astro@5.16.14

Patch Changes

  • #15213 c775fce Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Updates how the local provider must be used when using the experimental Fonts API

    Previously, there were 2 kinds of font providers: remote and local.

    Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

    -import { defineConfig } from "astro/config";
    +import { defineConfig, fontProviders } from "astro/config";
    export default defineConfig({
    experimental: {
    fonts: [{
    name: "Custom",
    cssVariable: "--font-custom",
    
    
           provider: "local",
    
    
    
    
    
           provider: fontProviders.local(),
    
    
    
           options: {
          variants: [
              {
                  weight: 400,
                  style: "normal",
                  src: ["./src/assets/fonts/custom-400.woff2"]
              },
              {
                  weight: 700,
                  style: "normal",
                  src: ["./src/assets/fonts/custom-700.woff2"]
              }
              // ...
          ]
    
    
    
           }
      }]
    
    }
    });

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

See the experimental Fonts API docs for more information.

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.15

Patch Changes

  • #15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

5.16.14

Patch Changes

  • #15213 c775fce Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Updates how the local provider must be used when using the experimental Fonts API

    Previously, there were 2 kinds of font providers: remote and local.

    Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

    -import { defineConfig } from "astro/config";
    +import { defineConfig, fontProviders } from "astro/config";
    export default defineConfig({
    experimental: {
    fonts: [{
    name: "Custom",
    cssVariable: "--font-custom",
    
    
           provider: "local",
    
    
    
    
    
           provider: fontProviders.local(),
    
    
    
           options: {
          variants: [
              {
                  weight: 400,
                  style: "normal",
                  src: ["./src/assets/fonts/custom-400.woff2"]
              },
              {
                  weight: 700,
                  style: "normal",
                  src: ["./src/assets/fonts/custom-700.woff2"]
              }
              // ...
          ]
    
    
    
           }
      }]
    
    }
    });

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

... (truncated)

Commits

Updates katex from 0.16.27 to 0.16.28

Release notes

Sourced from katex's releases.

v0.16.28

0.16.28 (2026-01-25)

Bug Fixes

  • type: add missing types definition path to package.json (#4125) (0ef8921)
Changelog

Sourced from katex's changelog.

0.16.28 (2026-01-25)

Bug Fixes

  • type: add missing types definition path to package.json (#4125) (0ef8921)
Commits
  • dd50cde chore(release): 0.16.28 [ci skip]
  • 0ef8921 fix(type): add missing types definition path to package.json (#4125)
  • a2fcfe3 docs: add MintApps to list of users (#4066)
  • d37328c docs: fix typo in comment about infix precedence (#4095)
  • dd2e2fb docs(supported.md): fix typo in \textquoteleft example
  • b73f941 docs: add Educase as user, fix user icon links (#4104)
  • See full diff in compare view

Updates @biomejs/biome from 2.3.11 to 2.3.13

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.3.13

2.3.13

Patch Changes

  • #8815 f924f23 Thanks @​dyc3! - Improved useVueValidVOn to be more closely aligned with the source rule. It will now properly allow modifiers for all possible keyboard events. It should have better performance when there are no violations of the rule as well.

    Now treated valid:

    <div @keydown.arrow-down="handler"></div>
    <div @keydown.a="handler"></div>
    <div @keydown.b="handler"></div>
    <div @keydown.27="foo"></div>
  • #8856 85f81f9 Thanks @​dyc3! - Fixed #8710: Biome now parses Vue dynamic slot shorthand arguments that use template literals in [].

  • #8850 2a190e0 Thanks @​dyc3! - Fixed #8708: Tailwind @utility directives now parse functional utility names like px-* when Tailwind directives are enabled.

  • #8863 79386e0 Thanks @​dyc3! - Fixed an issue with biome migrate eslint where it couldn't detect rules for CSS, GraphQL, and HTML.

  • #8771 6f56b6e Thanks @​lghuahua! - Fix the --reporter=summary output incorrectly merging and displaying wrong issue counts for different rules. Fixes #8730

  • #8714 ac3a71f Thanks @​Netail! - Added new nursery rule use-consistent-enum-value-type. This rule disallows enums from having both number and string members.

What's Changed

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.3.13

Patch Changes

  • #8815 f924f23 Thanks @​dyc3! - Improved useVueValidVOn to be more closely aligned with the source rule. It will now properly allow modifiers for all possible keyboard events. It should have better performance when there are no violations of the rule as well.

    Now treated valid:

    <div @keydown.arrow-down="handler"></div>
    <div @keydown.a="handler"></div>
    <div @keydown.b="handler"></div>
    <div @keydown.27="foo"></div>
  • #8856 85f81f9 Thanks @​dyc3! - Fixed #8710: Biome now parses Vue dynamic slot shorthand arguments that use template literals in [].

  • #8850 2a190e0 Thanks @​dyc3! - Fixed #8708: Tailwind @utility directives now parse functional utility names like px-* when Tailwind directives are enabled.

  • #8863 79386e0 Thanks @​dyc3! - Fixed an issue with biome migrate eslint where it couldn't detect rules for CSS, GraphQL, and HTML.

  • #8771 6f56b6e Thanks @​lghuahua! - Fix the --reporter=summary output incorrectly merging and displaying wrong issue counts for different rules. Fixes #8730

  • #8714 ac3a71f Thanks @​Netail! - Added new nursery rule use-consistent-enum-value-type. This rule disallows enums from having both number and string members.

2.3.12

Patch Changes

  • #8653 047576d Thanks @​dyc3! - Added new nursery rule noDuplicateAttributes to forbid duplicate attributes in HTML elements.

  • #8648 96d09f4 Thanks @​BaeSeokJae! - Added a new nursery rule noVueOptionsApi.

    Biome now reports Vue Options API usage, which is incompatible with Vue 3.6's Vapor Mode. This rule detects Options API patterns in <script> blocks, defineComponent(), and createApp() calls, helping prepare codebases for Vapor Mode adoption.

    For example, the following now triggers this rule:

    <script>
    export default {
      data() {
        return { count: 0 };
      },
    };
    </script>
  • #8832 b08270b Thanks @​Exudev! - Fixed #8809, #7985, and #8136: the noSecrets rule no longer reports false positives on common CamelCase identifiers like paddingBottom, backgroundColor, unhandledRejection, uncaughtException, and IngestGatewayLogGroup.

... (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

…pdates

Bumps the patch-updates group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@fancyapps/ui](https://github.com/fancyapps/ui) | `6.1.8` | `6.1.9` |
| [@iconify-json/material-symbols](https://github.com/iconify/icon-sets) | `1.2.52` | `1.2.53` |
| [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `5.16.12` | `5.16.15` |
| [katex](https://github.com/KaTeX/KaTeX) | `0.16.27` | `0.16.28` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.3.11` | `2.3.13` |



Updates `@fancyapps/ui` from 6.1.8 to 6.1.9
- [Release notes](https://github.com/fancyapps/ui/releases)
- [Changelog](https://github.com/fancyapps/ui/blob/main/CHANGELOG.md)
- [Commits](fancyapps/ui@v6.1.8...v6.1.9)

Updates `@iconify-json/material-symbols` from 1.2.52 to 1.2.53
- [Commits](https://github.com/iconify/icon-sets/commits)

Updates `astro` from 5.16.12 to 5.16.15
- [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.16.15/packages/astro)

Updates `katex` from 0.16.27 to 0.16.28
- [Release notes](https://github.com/KaTeX/KaTeX/releases)
- [Changelog](https://github.com/KaTeX/KaTeX/blob/main/CHANGELOG.md)
- [Commits](KaTeX/KaTeX@v0.16.27...v0.16.28)

Updates `@biomejs/biome` from 2.3.11 to 2.3.13
- [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.3.13/packages/@biomejs/biome)

---
updated-dependencies:
- dependency-name: "@fancyapps/ui"
  dependency-version: 6.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-updates
- dependency-name: "@iconify-json/material-symbols"
  dependency-version: 1.2.53
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-updates
- dependency-name: astro
  dependency-version: 5.16.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-updates
- dependency-name: katex
  dependency-version: 0.16.28
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-updates
- dependency-name: "@biomejs/biome"
  dependency-version: 2.3.13
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: patch-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 Jan 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant