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.

Sign up for GitHub

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

Jump to bottom

Bump the tailwindcss group with 2 updates #484

Merged
merged 1 commit into from
Feb 22, 2025
Merged

Bump the tailwindcss group with 2 updates #484

merged 1 commit into from
Feb 22, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 22, 2025

Bumps the tailwindcss group with 2 updates: @tailwindcss/vite and tailwindcss.

Updates @tailwindcss/vite from 4.0.6 to 4.0.8

Release notes

Sourced from @​tailwindcss/vite's releases.

v4.0.8

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

  • Don't include theme variables that aren't used in compiled CSS (#16211, #16676)

v4.0.7

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)
Changelog

Sourced from @​tailwindcss/vite's changelog.

[4.0.8] - 2025-02-21

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

  • Don't include theme variables that aren't used in compiled CSS (#16211, #16676)

[4.0.7] - 2025-02-18

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)
Commits

Updates tailwindcss from 4.0.6 to 4.0.8

Release notes

Sourced from tailwindcss's releases.

v4.0.8

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

  • Don't include theme variables that aren't used in compiled CSS (#16211, #16676)

v4.0.7

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)
Changelog

Sourced from tailwindcss's changelog.

[4.0.8] - 2025-02-21

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

  • Don't include theme variables that aren't used in compiled CSS (#16211, #16676)

[4.0.7] - 2025-02-18

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)
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

@dependabot
Bump the tailwindcss group with 2 updates
5737f5c 
Bumps the tailwindcss group with 2 updates: [@tailwindcss/vite](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-vite) and [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss).


Updates `@tailwindcss/vite` from 4.0.6 to 4.0.8
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.0.8/packages/@tailwindcss-vite)

Updates `tailwindcss` from 4.0.6 to 4.0.8
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.0.8/packages/tailwindcss)

---
updated-dependencies:
- dependency-name: "@tailwindcss/vite"
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: tailwindcss
- dependency-name: tailwindcss
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: tailwindcss
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Feb 22, 2025
@acelaya acelaya merged commit b5f1c97 into main Feb 22, 2025
1 check passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/tailwindcss-10654f3a00 branch February 22, 2025 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@acelaya