Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update all non-major dependencies #77

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@biomejs/biome (source) 1.5.3 -> 1.8.0 age adoption passing confidence
@citation-js/core (source) 0.7.6 -> 0.7.11 age adoption passing confidence
@citation-js/plugin-bibtex (source) 0.7.8 -> 0.7.12 age adoption passing confidence
@citation-js/plugin-csl (source) 0.7.6 -> 0.7.11 age adoption passing confidence
@citation-js/plugin-doi (source) 0.7.8 -> 0.7.11 age adoption passing confidence
@iconify/json (source) 2.2.184 -> 2.2.216 age adoption passing confidence
@lucia-auth/adapter-postgresql (source) 3.1.0 -> 3.1.2 age adoption passing confidence
@melt-ui/svelte 0.74.1 -> 0.81.0 age adoption passing confidence
@playwright/test (source) 1.41.2 -> 1.44.1 age adoption passing confidence
@react-email/components (source) 0.0.14 -> 0.0.19 age adoption passing confidence
@react-email/render (source) 0.0.12 -> 0.0.15 age adoption passing confidence
@sveltejs/adapter-vercel (source) 5.1.0 -> 5.3.1 age adoption passing confidence
@sveltejs/kit (source) 2.5.0 -> 2.5.10 age adoption passing confidence
@sveltejs/vite-plugin-svelte (source) 3.0.2 -> 3.1.1 age adoption passing confidence
@t3-oss/env-core (source) 0.9.2 -> 0.10.1 age adoption passing confidence
@types/nodemailer (source) 6.4.14 -> 6.4.15 age adoption passing confidence
@types/react (source) 18.2.56 -> 18.3.3 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 7.0.2 -> 7.12.0 age adoption passing confidence
@typescript-eslint/parser (source) 7.0.2 -> 7.12.0 age adoption passing confidence
@​upstash/ratelimit 1.0.1 -> 1.1.3 age adoption passing confidence
@upstash/redis 1.28.4 -> 1.31.3 age adoption passing confidence
arctic 1.2.0 -> 1.9.0 age adoption passing confidence
autoprefixer 10.4.17 -> 10.4.19 age adoption passing confidence
bits-ui 0.18.1 -> 0.21.10 age adoption passing confidence
cmdk-sv 0.0.13 -> 0.0.17 age adoption passing confidence
dotenv-cli 7.3.0 -> 7.4.2 age adoption passing confidence
drizzle-kit 0.20.14 -> 0.22.2 age adoption passing confidence
drizzle-orm (source) 0.29.3 -> 0.31.1 age adoption passing confidence
eslint (source) 8.56.0 -> 8.57.0 age adoption passing confidence
eslint-plugin-svelte (source) 2.35.1 -> 2.39.0 age adoption passing confidence
formsnap 0.5.0 -> 0.5.1 age adoption passing confidence
formsnap 0.4.4 -> 0.5.1 age adoption passing confidence
lucia (source) 3.0.1 -> 3.2.0 age adoption passing confidence
nanoid 5.0.5 -> 5.0.7 age adoption passing confidence
nodemailer (source) 6.9.9 -> 6.9.13 age adoption passing confidence
oslo 1.1.2 -> 1.2.0 age adoption passing confidence
pg (source) 8.11.3 -> 8.12.0 age adoption passing confidence
pnpm (source) 8.15.3 -> 8.15.8 age adoption passing confidence
postcss (source) 8.4.35 -> 8.4.38 age adoption passing confidence
postgres 3.4.3 -> 3.4.4 age adoption passing confidence
prettier (source) 3.2.5 -> 3.3.1 age adoption passing confidence
prettier-plugin-svelte 3.2.1 -> 3.2.3 age adoption passing confidence
react (source) 18.2.0 -> 18.3.1 age adoption passing confidence
react-email (source) 2.0.0 -> 2.1.4 age adoption passing confidence
svelte (source) 4.2.11 -> 4.2.17 age adoption passing confidence
svelte-check 3.6.4 -> 3.8.0 age adoption passing confidence
sveltekit-search-params (source) 2.1.1 -> 2.1.2 age adoption passing confidence
sveltekit-superforms (source) 2.4.0 -> 2.14.0 age adoption passing confidence
tailwind-merge 2.2.1 -> 2.3.0 age adoption passing confidence
tailwind-variants 0.2.0 -> 0.2.1 age adoption passing confidence
tailwindcss (source) 3.4.1 -> 3.4.4 age adoption passing confidence
tslib (source) 2.6.2 -> 2.6.3 age adoption passing confidence
tsx 4.7.1 -> 4.11.2 age adoption passing confidence
turbo (source) 1.12.4 -> 1.13.4 age adoption passing confidence
typescript (source) 5.3.3 -> 5.4.5 age adoption passing confidence
unplugin-icons 0.18.5 -> 0.19.0 age adoption passing confidence
vitest (source) 1.3.0 -> 1.6.0 age adoption passing confidence
zod (source) 3.22.4 -> 3.23.8 age adoption passing confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v1.8.0

Compare Source

Analyzer
New features
  • Allow suppression comments to suppress individual instances of rules. This is
    used for the lint rule useExhaustiveDependencies, which is now able to
    suppress specific dependencies. Fixes #​2509. Contributed by @​arendjr
Enhancements
  • Assume Astro object is always a global when processing .astro files. Contributed by @​minht11
  • Assume Vue compiler macros are globals when processing .vue files. (#​2771) Contributed by @​dyc3
CLI
New features
  • New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.

    biome clean
  • Add two new options --only and --skip to the command biome lint (#​58).

    The --only option allows you to run a given rule or rule group,
    For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules.
    If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.

    biome lint --only=style/useNamingConvention --only=style/noInferrableTypes

    Passing a group does not change the severity level of the rules in the group.
    All the disabled rules in the group will remain disabled.
    To ensure that the group is run, the recommended field of the group is enabled.
    The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

    The --skip option allows you to skip the execution of a given group or a given rule.
    For example, the following command skips the style group and the suspicious/noExplicitAny rule.

    biome lint --skip=style --skip=suspicious/noExplicitAny

    You can also use --only and --skip together. --skip oevrrides --only.
    The following command executes only the rules from the style group, but the style/useNamingConvention rule.

    biome lint --only=style --skip=style/useNamingConvention

    These options are compatible with other options such as --write (previously --apply), and --reporter.

    Contributed by @​Conaclos

  • Add new command biome clean. Use this command to purge all the logs emitted by the Biome daemon. This command is really useful, because the Biome daemon tends
    log many files and contents during its lifecycle. This means that if your editor is open for hours (or even days), the biome-logs folder could become quite heavy. Contributed by @​ematipico

  • Add support for formatting and linting CSS files from the CLI. These operations are opt-in for the time being.

    If you don't have a configuration file, you can enable these features with --css-formatter-enabled and --css-linter-enabled:

    biome check --css-formatter-enabled=true --css-linter-enabled=true ./

    Contributed by @​ematipico

  • Add new CLI options to control the CSS formatting. Check the CLI reference page for more details. Contributed by @​ematipico

  • Add new options --write, --fix (alias of --write) and --unsafe to the command biome lint and biome check.
    Add a new option --fix (alias of --write) to the command biome format and biome migrate.

    biome <lint|check> --<write|fix> [--unsafe]
    biome format --<write|fix>
    biome migrate --<write|fix>

    The biome <lint|check> --<write|fix> has the same behavior as biome <lint|check> --apply.
    The biome <lint|check> --<write|fix> --unsafe has the same behavior as biome <lint|check> --apply-unsafe.
    The biome format --fix has the same behavior as biome format --write.
    The biome migrate --fix has the same behavior as biome migrate --write.

    This change allows these commands to write modifications in the same options.
    With this change, the --apply and --apply-unsafe options are deprecated.

    Contributed by @​unvalley

Enhancements
  • Biome now executes commands (lint, format, check and ci) on the working directory by default. #​2266 Contributed by @​unvalley

    - biome check .
    + biome check    # You can run the command without the path
  • biome migrate eslint now tries to convert ESLint ignore patterns into Biome ignore patterns.

    ESLint uses gitignore patterns.
    Biome now tries to convert these patterns into Biome ignore patterns.

    For example, the gitignore pattern /src is a relative path to the file in which it appears.
    Biome now recognizes this and translates this pattern to ./src.

    Contributed by @​Conaclos

  • biome migrate eslint now supports the eslintIgnore field in package.json.

    ESLint allows the use of package.json as an ESLint configuration file.
    ESLint supports two fields: eslintConfig and eslintIgnore.
    Biome only supported the former. It now supports both.

    Contributed by @​Conaclos

  • biome migrate eslint now propagates NodeJS errors to the user.

    This will help users to identify why Biome is unable to load some ESLint configurations.

    Contributed by @​Conaclos

  • Add a new --reporter called summary. This reporter will print diagnostics in a different way, based on the tools (formatter, linter, etc.) that are executed.
    Import sorting and formatter shows the name of the files that require formatting. Instead, the linter will group the number of rules triggered and the number of errors/warnings:

    Formatter ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    The following files needs to be formatted:
    main.ts
    index.ts
    
    Organize Imports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    The following files needs to have their imports sorted:
    main.ts
    index.ts
    
    Analyzer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Some analyzer rules were triggered
    
    Rule Name                                               Diagnostics
    lint/suspicious/noImplicitAnyLet                        12 (12 error(s), 0 warning(s), 0 info(s))
    lint/suspicious/noDoubleEquals                          8 (8 error(s), 0 warning(s), 0 info(s))
    lint/suspicious/noRedeclare                             12 (12 error(s), 0 warning(s), 0 info(s))
    lint/suspicious/noDebugger                              20 (20 error(s), 0 warning(s), 0 info(s))
    

    Contributed by @​ematipico

  • biome ci now enforces printing the output using colours. If you were previously using --colors=force, you can remove it because it's automatically set. Contributed by @​ematipico

  • Add a new --reporter called github. This reporter will print diagnostics using GitHub workflow commands:

    ::error title=lint/suspicious/noDoubleEquals,file=main.ts,line=4,endLine=4,col=3,endColumn=5::Use === instead of ==
    ::error title=lint/suspicious/noDebugger,file=main.ts,line=6,endLine=6,col=1,endColumn=9::This is an unexpected use of the debugger statement.
    ::error title=lint/nursery/noEvolvingAny,file=main.ts,line=8,endLine=8,col=5,endColumn=6::This variable's type is not allowed to evolve implicitly, leading to potential any types.
    

    Contributed by @​ematipico

  • Add a new --reporter called junit. This reporter will print diagnostics using GitHub workflow commands:

    <?xml version="1.0" encoding="UTF-8"?>
    <testsuites name="Biome" tests="16" failures="16" errors="20" time="<TIME>">
      <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
          <testcase name="org.biome.lint.suspicious.noDoubleEquals" line="4" column="3">
              <failure message="Use === instead of ==. == is only allowed when comparing against `null`">line 3, col 2, Use === instead of ==. == is only allowed when comparing against `null`</failure>
          </testcase>
      </testsuite>
      <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
          <testcase name="org.biome.lint.suspicious.noDebugger" line="6" column="1">
              <failure message="This is an unexpected use of the debugger statement.">line 5, col 0, This is an unexpected use of the debugger statement.</failure>
          </testcase>
      </testsuite>
      <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
          <testcase name="org.biome.lint.nursery.noEvolvingAny" line="8" column="5">
              <failure message="This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.">line 7, col 4, This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.</failure>
          </testcase>
      </testsuite>
    </testsuites>

    Contributed by @​ematipico

Bug fixes
  • Fix #​3024, where running biome init would create biome.json even if biome.jsonc already exists. Contributed by @​minht11
Configuration
New features
  • Add an rule option fix to override the code fix kind of a rule (#​2882).

    A rule can provide a safe or an unsafe code action.
    You can now tune the kind of code actions thanks to the fix option.
    This rule option takes a value among:

    • none: the rule no longer emits code actions.
    • safe: the rule emits safe code action.
    • unsafe: the rule emits unsafe code action.

    The following configuration disables the code actions of noUnusedVariables, makes the emitted code actions of style/useConst and style/useTemplate unsafe and safe respectively.

    {
      "linter": {
        "rules": {
          "correctness": {
            "noUnusedVariables": {
              "level": "error",
              "fix": "none"
            },
            "style": {
              "useConst": {
                "level": "warn",
                "fix": "unsafe"
              },
              "useTemplate": {
                "level": "warn",
                "fix": "safe"
              }
            }
          }
        }
      }
    }

    Contributed by @​Conaclos

  • Add option javascript.linter.enabled to control the linter for JavaScript (and its super languages) files. Contributed by @​ematipico

  • Add option json.linter.enabled to control the linter for JSON (and its super languages) files. Contributed by @​ematipico

  • Add option css.linter.enabled to control the linter for CSS (and its super languages) files. Contributed by @​ematipico

  • Add option css.formatter, to control the formatter


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

vercel bot commented Feb 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
fontesio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 5, 2024 5:35pm

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8c43dba to 78c8f2f Compare May 30, 2024 02:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 78c8f2f to de5b7b8 Compare May 30, 2024 06:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from de5b7b8 to 892653e Compare May 31, 2024 09:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 892653e to 77bd9ae Compare May 31, 2024 13:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 77bd9ae to 54520bc Compare June 1, 2024 19:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 54520bc to 5ec2849 Compare June 3, 2024 06:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5ec2849 to 5bfda9f Compare June 3, 2024 20:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5bfda9f to d55b86e Compare June 4, 2024 11:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d55b86e to 46cece9 Compare June 4, 2024 12:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 46cece9 to 0140e71 Compare June 4, 2024 15:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0140e71 to 715d26c Compare June 4, 2024 18:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 715d26c to 9e859f1 Compare June 4, 2024 22:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9e859f1 to 2ca808d Compare June 5, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants