Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 20, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@eslint/js (source) ^9.22.0 -> ^9.24.0 age adoption passing confidence
@lucide/svelte (source) ^0.483.0 -> ^0.487.0 age adoption passing confidence
@shikijs/langs (source) ^3.2.1 -> ^3.2.2 age adoption passing confidence
@shikijs/rehype (source) ^3.2.1 -> ^3.2.2 age adoption passing confidence
@shikijs/themes (source) ^3.2.1 -> ^3.2.2 age adoption passing confidence
@sveltejs/adapter-vercel (source) ^5.6.3 -> ^5.7.0 age adoption passing confidence
@sveltejs/kit (source) ^2.20.1 -> ^2.20.5 age adoption passing confidence
@tailwindcss/vite (source) ^4.0.14 -> ^4.1.3 age adoption passing confidence
@types/node (source) ^22.13.13 -> ^22.14.0 age adoption passing confidence
@types/semver (source) ^7.5.8 -> ^7.7.0 age adoption passing confidence
@upstash/redis ^1.34.6 -> ^1.34.7 age adoption passing confidence
bits-ui ^1.3.13 -> ^1.3.19 age adoption passing confidence
eslint (source) ^9.22.0 -> ^9.24.0 age adoption passing confidence
eslint-config-prettier ^10.1.1 -> ^10.1.2 age adoption passing confidence
eslint-plugin-svelte (source) ^3.3.2 -> ^3.5.1 age adoption passing confidence
octokit ^4.1.2 -> ^4.1.3 age adoption passing confidence
pnpm (source) 10.6.5 -> 10.8.0 age adoption passing confidence
posthog-js ^1.235.4 -> ^1.235.5 age adoption passing confidence
shiki (source) ^3.2.1 -> ^3.2.2 age adoption passing confidence
svelte (source) ^5.23.2 -> ^5.25.12 age adoption passing confidence
tailwind-merge ^3.0.2 -> ^3.2.0 age adoption passing confidence
tailwindcss (source) ^4.0.14 -> ^4.1.3 age adoption passing confidence
tw-animate-css ^1.2.4 -> ^1.2.5 age adoption passing confidence
typescript (source) ^5.8.2 -> ^5.8.3 age adoption passing confidence
typescript-eslint (source) ^8.26.1 -> ^8.29.1 age adoption passing confidence
vite (source) ^6.2.2 -> ^6.2.6 age adoption passing confidence

Release Notes

eslint/eslint (@​eslint/js)

v9.24.0

Compare Source

v9.23.0

Compare Source

lucide-icons/lucide (@​lucide/svelte)

v0.487.0: Version 0.487.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.486.0...0.487.0

v0.486.0: Version 0.486.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.485.0...0.486.0

v0.485.0: Version 0.485.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.484.0...0.485.0

v0.484.0: Version 0.484.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.483.0...0.484.0

shikijs/shiki (@​shikijs/langs)

v3.2.2

Compare Source

   🚀 Features
    View changes on GitHub
sveltejs/kit (@​sveltejs/adapter-vercel)

v5.7.0

Compare Source

Minor Changes
  • feat: create symlink functions for each route, for better observability (#​13679)
Patch Changes
sveltejs/kit (@​sveltejs/kit)

v2.20.5

Compare Source

Patch Changes
  • allow HandleServerError hook to access getRequestEvent (#​13666)

  • fix: prevent Rollup warnings for undefined hooks (#​13687)

v2.20.4

Compare Source

Patch Changes
  • chore: remove internal class-replacement hack that isn't needed anymore (#​13664)

v2.20.3

Compare Source

Patch Changes
  • fix: only call afterNavigate once on app start when SSR is disabled (#​13593)

v2.20.2

Compare Source

Patch Changes
  • fix: allow non-prerendered API endpoint calls during reroute when prerendering (#​13616)
tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.1.3

Compare Source

Fixed
  • Show warning when using unsupported bare value data type in --value(…) (#​17464)
  • PostCSS: Ensure changes to the input CSS file don't generate stale output when using Turbopack (#​17554)
  • Ensure classes are detected in Ruby's %w syntax in Slim templates (#​17557)

v4.1.2

Compare Source

Fixed
  • Don't rely on the presence of @layer base to polyfill @property (#​17506)
  • Support setting multiple inset shadows as arbitrary values (#​17523)
  • Fix drop-shadow-* utilities that are defined with multiple shadows (#​17515)
  • PostCSS: Fix race condition when two changes are queued concurrently (#​17514)
  • PostCSS: Ensure files containing @tailwind utilities are processed (#​17514)
  • Ensure the color-mix(…) polyfill creates fallbacks even when using colors that cannot be statically analyzed (#​17513)
  • Fix slow incremental builds with @tailwindcss/vite and @tailwindcss/postscss (especially on Windows) (#​17511)
  • Vite: Fix missing CSS file in Qwik setups (#​17533)

v4.1.1

Compare Source

Fixed
  • Disable padding in @source inline(…) brace expansion (#​17491)
  • Inject polyfills after @import and body-less @layer (#​17493)
  • Ensure @tailwindcss/cli does not contain an import for jiti (#​17502)

v4.1.0

Compare Source

Added
  • Add details-content variant (#​15319)
  • Add inverted-colors variant (#​11693)
  • Add noscript variant (#​11929, #​17431)
  • Add items-baseline-last and self-baseline-last utilities (#​13888, #​17476)
  • Add pointer-none, pointer-coarse, and pointer-fine variants (#​16946)
  • Add any-pointer-none, any-pointer-coarse, and any-pointer-fine variants (#​16941)
  • Add safe alignment utilities (#​14607)
  • Add user-valid and user-invalid variants (#​12370)
  • Add wrap-anywhere, wrap-break-word, and wrap-normal utilities (#​12128)
  • Add @source inline(…) and @source not inline(…) (#​17147)
  • Add @source not "…" (#​17255)
  • Add text-shadow-* utilities (#​17389)
  • Add mask-* utilities (#​17134)
  • Add bg-{position,size}-* utilities for arbitrary values (#​17432)
  • Add shadow-*/<alpha>, inset-shadow-*/<alpha>, drop-shadow-*/<alpha>, and text-shadow-*/<alpha> utilities to control shadow opacity (#​17398, #​17434)
  • Add drop-shadow-<color> utilities (#​17434)
  • Improve compatibility with older versions of Safari and Firefox (#​17435)
Fixed
  • Follow symlinks when resolving @source directives (#​17391)
  • Don't scan ignored files for classes when changing an ignored file triggers a rebuild using @tailwindcss/cli (#​17255)
  • Support negated content rules in legacy JavaScript configuration (#​17255)
  • Interpret syntax like @("@&#8203;")md:… as @md:… in Razor files (#​17427)
  • Disallow top-level braces, top-level semicolons, and unbalanced parentheses and brackets in arbitrary values (#​17361)
  • Ensure the --theme(…) function still resolves to the CSS variables when using legacy JS plugins (#​17458)
  • Detect used theme variables in CSS module files (#​17433, #​17467)
Changed
  • Ignore node_modules by default (can be overridden by @source … rules) (#​17255)
  • @source rules that include file extensions or point inside node_modules/ folders no longer consider your .gitignore rules (#​17255)
  • Deprecate bg-{left,right}-{top,bottom} in favor of bg-{top,bottom}-{left,right} utilities (#​17378)
  • Deprecate object-{left,right}-{top,bottom} in favor of object-{top,bottom}-{left,right} utilities (#​17437)

v4.0.17

Compare Source

Fixed
  • Fix an issue causing the CLI to hang when processing Ruby files (#​17383)

v4.0.16

Compare Source

Added
  • Add support for literal values in --value('…') and --modifier('…') (#​17304)
Fixed
  • Fix class extraction followed by ( in Pug (#​17320)
  • Ensure @keyframes for theme animations are emitted if they are referenced following a comma (#​17352)
  • Vite: Ensure that updates to an imported CSS file are properly propagated after updating source files (#​17347)
  • Pre process Slim templates embedded in Ruby files (#​17336)
  • Error when input and output files resolve to the same file when using the CLI (#​17311)
  • Add missing suggestions when --spacing(--value(integer, number)) is used (#​17308)
  • Add ::-webkit-details-marker pseudo to marker variant (#​17362)

v4.0.15

Compare Source

upstash/upstash-redis (@​upstash/redis)

v1.34.7

Compare Source

What's Changed

Features:

Fixes:

Full Changelog: upstash/redis-js@v1.34.6...v1.34.7

huntabyte/bits-ui (bits-ui)

v1.3.19

Compare Source

Patch Changes
  • fix(Calendar): ensure time set outside persists when new day is selected (#​1359)

  • fix(Command): ensure filtered is always defined, even if not filtering (#​1363)

  • fix(Calendar): ensure default value is not a string (#​1362)

v1.3.18

Compare Source

Patch Changes
  • fix: bug with date formatting in date-value attribute (#​1347)

v1.3.17

Compare Source

Patch Changes
  • fix(Pagination): ensure range.start starts at 1 instead of 0 (#​1354)

  • fix(Avatar): fix invalid display style being applied to fallback (#​1352)

v1.3.16

Compare Source

Patch Changes
  • fix(Slider): Prevent Thumb from exceeding track bounds (#​1338)

v1.3.15

Compare Source

Patch Changes
  • fix(Select): enable space support in typeahead logic (#​1335)

  • fix(Command): command sort only once per tick (#​1321)

v1.3.14

Compare Source

Patch Changes
  • fix(Menubar): Add onOpenChange prop to <Menubar.Menu/> (#​1324)
eslint/eslint (eslint)

v9.24.0

Compare Source

v9.23.0

Compare Source

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.2

Compare Source

Patch Changes
sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v3.5.1

Compare Source

Patch Changes

v3.5.0

Compare Source

Minor Changes
Patch Changes

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Minor Changes
  • #​1165 2b7e164 Thanks @​43081j! - Adds a suggestion to the require-store-callbacks-use-set-param rule to automatically rename or add function parameters.

  • #​1163 d9b8604 Thanks @​43081j! - Adds a suggestion to the derived-has-same-inputs-outputs rule which renames the outputs.

  • #​1164 29b1315 Thanks @​43081j! - Added a suggestion for no-at-debug-tags rule which removes the tags

Patch Changes

v3.3.3

Compare Source

Patch Changes
octokit/octokit.js (octokit)

v4.1.3

Compare Source

Bug Fixes
pnpm/pnpm (pnpm)

v10.8.0

Compare Source

Minor Changes
  • Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

    module.exports = {
      hooks: {
        updateConfig: (config) => ({
          ...config,
          nodeLinker: "hoisted",
        }),
      },
    };
  • Now you can use the pnpm add command with the --config flag to install new configurational dependencies #​9377.

Patch Changes
  • Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #​9169.
  • pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
  • pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #​9365.

v10.7.1: pnpm 10.7.1

Compare Source

Patch Changes

  • pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #​9355.
  • pnpm config get should read auth related settings via npm CLI #​9345.
  • Replace leading ~/ in a path in .npmrc with the home directory #​9217.

Platinum Sponsors

Bit Bit Syntax

Gold Sponsors

Discord u|screen
JetBrains Nx
CodeRabbit Route4Me
Workleap Stackblitz

v10.7.0

Compare Source

Minor Changes
  • pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

  • It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

  • Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

    For example:

    patchedDependencies:
      foo: patches/foo-1.patch
      foo@^2.0.0: patches/foo-2.patch
      [email protected]: patches/foo-3.patch

    The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

    [!WARNING]
    The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

    # pnpm-workspace.yaml
    patchedDependencies:
      # the specialized sub range
      '[email protected]': patches/foo.2.2.0-2.8.0.patch
      # the more general patch, excluding the sub range above
      'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

    In most cases, however, it's sufficient to just define an exact version to override the range.

  • pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

  • Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported bu


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Mar 20, 2025

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

Name Status Preview Comments Updated (UTC)
svelte-changelog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 11, 2025 11:04am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 20, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@WarningImHack3r WarningImHack3r merged commit be54547 into main Apr 11, 2025
5 checks passed
@WarningImHack3r WarningImHack3r deleted the renovate/npm branch April 11, 2025 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants