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

⬆️ deps: Update dependencies (non-major) #111

Merged
merged 2 commits into from
Feb 22, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 17, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tailwindcss/vite (source) 4.0.4 -> 4.0.8 age adoption passing confidence
@types/node (source) 22.13.1 -> 22.13.5 age adoption passing confidence
pnpm (source) 10.3.0 -> 10.4.1 age adoption passing confidence
prettier (source) 3.4.2 -> 3.5.2 age adoption passing confidence
tailwindcss (source) 4.0.4 -> 4.0.8 age adoption passing confidence
tsx (source) 4.19.2 -> 4.19.3 age adoption passing confidence

Release Notes

tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.0.8

Compare Source

Added
  • Allow @import with theme(…) options for stylesheets that contain more than just @theme rules (#​16514)
Fixed
  • Don't add !important to CSS variable declarations when using the important modifier (#​16668)
  • Vite: Ignore files and directories specified in your .gitignore file when using automatic source detection(#​16631)
  • Vite: Don't rely on the module graph for detecting candidates to ensure setups with multiple Vite builds work as expected (#​16631)
  • Vite: Ensure Astro production builds always contain classes used in client-only components (#​16631)
  • Vite: Always scan raw file contents for utility classes before any other transforms have been applied to ensure utility classes are scanned without any additional escaping (#​16631)
  • Ensure utilities with more declarations are always sorted before utilities with fewer declarations when utilities only define CSS variables (#​16715)
  • Only include translate-z-px utilities once in compiled CSS (#​16718)
Changed

v4.0.7

Compare Source

Fixed
  • Export tailwindcss/lib/util/flattenColorPalette.js for backward compatibility (#​16411)
  • Fix sorting of numeric utility suggestions when they have different magnitudes (#​16414)
  • Show suggestions for fractions in IntelliSense (#​16353)
  • Don’t replace _ in suggested theme keys (#​16433)
  • Ensure --default-outline-width can be used to change the outline-width value of the outline utility (#​16469)
  • Ensure drop shadow utilities don't inherit unexpectedly (#​16471)
  • Export config and plugin types from tailwindcss/plugin for backward compatibility (#​16505)
  • Ensure JavaScript plugins that emit nested rules referencing the utility name work as expected (#​16539)
  • Statically link Visual Studio redistributables in @tailwindcss/oxide Windows builds (#​16602)
  • Ensure that Next.js splat routes are scanned for classes (#​16457)
  • Pin exact version of tailwindcss in @tailwindcss/* packages (#​16623)
  • Upgrade: Report errors when updating dependencies (#​16504)
  • Upgrade: Ensure a darkMode JS config setting with block syntax converts to use @slot (#​16507)
  • Upgrade: Ensure the latest version of tailwindcss and @tailwindcss/postcss are installed when upgrading (#​16620)

v4.0.6

Compare Source

Fixed
  • Revert change to no longer include theme variables that aren't used in compiled CSS (#​16403)
Fixed
  • Upgrade: Don't migrate blur to blur-sm when used with Next.js <Image placeholder="blur" /> (#​16405)

v4.0.5

Compare Source

Added
  • Add @theme static option for always including theme variables in compiled CSS (#​16211)
Fixed
  • Remove rogue console.log from @tailwindcss/vite (#​16307)
Changed
  • Don't include theme variables that aren't used in compiled CSS (#​16211)
pnpm/pnpm (pnpm)

v10.4.1

Compare Source

Patch Changes
  • Throws an error when the value provided by the --allow-build option overlaps with the pnpm.ignoredBuildDependencies list #​9105.
  • Print pnpm's version after the execution time at the end of the console output.
  • Print warning about ignored builds of dependencies on repeat install #​9106.
  • Setting init-package-manager should work.

v10.4.0

Compare Source

Minor Changes
  • pnpm approve-builds --global works now for allowing dependencies of globally installed packages to run postinstall scripts.

  • The pnpm add command now supports a new flag, --allow-build, which allows building the specified dependencies. For instance, if you want to install a package called bundle that has esbuild as a dependency and want to allow esbuild to run postinstall scripts, you can run:

    pnpm --allow-build=esbuild add bundle
    

    This will run esbuild's postinstall script and also add it to the pnpm.onlyBuiltDependencies field of package.json. So, esbuild will always be allowed to run its scripts in the future.

    Related PR: #​9086.

  • The pnpm init command adds a packageManager field with the current version of pnpm CLI #​9069. To disable this behaviour, set the init-package-manager setting to false.

Patch Changes
  • pnpm approve-builds should work after two consecutive pnpm install runs #​9083.
  • Fix instruction for updating pnpm with corepack #​9101.
  • The pnpm version specified by packageManager cannot start with v.
prettier/prettier (prettier)

v3.5.2

Compare Source

diff

Remove module-sync condition (#​17156 by @​fisker)

In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.

v3.5.1

Compare Source

diff

Fix CLI crash when cache for old version exists (#​17100 by @​sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#​17101 by @​remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

v3.5.0

Compare Source

diff

🔗 Release Notes

privatenumber/tsx (tsx)

v4.19.3

Compare Source


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot enabled auto-merge February 17, 2025 01:51
Copy link

netlify bot commented Feb 17, 2025

Deploy Preview for pfccblog ready!

Name Link
🔨 Latest commit b0772aa
🔍 Latest deploy log https://app.netlify.com/sites/pfccblog/deploys/67ba2c0cc189cc000886c019
😎 Deploy Preview https://deploy-preview-111--pfccblog.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch 5 times, most recently from 60190ed to 4cbb291 Compare February 21, 2025 22:10
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 4cbb291 to 8b61c65 Compare February 22, 2025 06:47
@renovate renovate bot added this pull request to the merge queue Feb 22, 2025
Merged via the queue into main with commit 508e343 Feb 22, 2025
6 checks passed
@renovate renovate bot deleted the renovate/dependencies-(non-major) branch February 22, 2025 20:00
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.

1 participant