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 major (major) #120

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
flowbite (source) ^2.4.1 -> ^3.0.0 age adoption passing confidence
tailwindcss (source) ^3.4.4 -> ^4.0.0 age adoption passing confidence
vitest (source) 2.1.8 -> 3.0.5 age adoption passing confidence
vitest (source) ^2.0.0 -> ^3.0.0 age adoption passing confidence

Release Notes

themesberg/flowbite (flowbite)

v3.1.1

Compare Source

  • fixed CSS variables markup in plugin

v3.1.0

Compare Source

  • use CSS variables instead of hex codes in plugin
  • remove setting dark mode via class strategy in plugin

v3.0.0

Compare Source

  • upgrade to Tailwind v4
  • refactor and adapt the Flowbite plugin and UI components to the new deprecated changes from Tailwind v4
tailwindlabs/tailwindcss (tailwindcss)

v4.0.3

Compare Source

Fixed
  • Fix incorrect removal of @import url(); (#​16144)

v4.0.2

Compare Source

Fixed
  • Only generate positive grid-cols-* and grid-rows-* utilities (#​16020)
  • Ensure escaped theme variables are handled correctly (#​16064)
  • Ensure we process Tailwind CSS features when only using @reference or @variant (#​16057)
  • Refactor gradient implementation to work around prettier/prettier#17058 (#​16072)
  • Vite: Ensure hot-reloading works with SolidStart setups (#​16052)
  • Vite: Fix a crash when starting the development server in SolidStart setups (#​16052)
  • Vite: Don't rebase URLs that appear to be aliases (#​16078)
  • Vite: Transform <style> blocks in HTML files (#​16069)
  • Prevent camel-casing CSS custom properties added by JavaScript plugins (#​16103)
  • Do not emit @keyframes in @theme reference (#​16120)
  • Discard invalid declarations when parsing CSS (#​16093)
  • Do not emit empty CSS rules and at-rules (#​16121)
  • Handle @variant when at the top-level of a stylesheet (#​16129)

v4.0.1

Compare Source

Added
  • Include :open pseudo-class in existing open variant (#​15349)
Fixed
  • Remove invalid min-w/h-none utilities (#​15845)
  • Discard CSS variable shorthand utilities that don't use valid CSS variables (#​15738)
  • Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#​15921)
  • Ensure font-size utilities with unknown modifier don't generate CSS (#​15921)
  • Don’t suggest font weight utilities more than once (#​15857)
  • Suggest container query variants (#​15857)
  • Disable bare value suggestions when not using the --spacing variable (#​15857)
  • Ensure suggested classes are properly sorted (#​15857)
  • Don’t look at .gitignore files outside initialized repos (#​15941)
  • Find utilities when using the Svelte class shorthand syntax across multiple lines (#​15974)
  • Find utilities when using the Angular class shorthand syntax (#​15974)
  • Find utilities when using functions inside arrays (#​15974)
  • Ensure that @tailwindcss/browser does not pollute the global namespace (#​15978)
  • Ensure that tailwind-merge is not scanned when using the Vite plugin (#​16005)
  • Ensure CSS theme variables are available within shadow roots (#​15975)
  • Fix crash when project lives in the / directory (#​15988)
  • Ensure custom variants have a non-empty selector list (#​16009)
  • Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#​15927)
  • Upgrade: Migrate leading-[1] to leading-none (#​16004)
  • Upgrade: Do not migrate arbitrary leading utilities to bare values (#​16004)

v4.0.0

Compare Source

Added

Start using Tailwind CSS v4.0 today by installing it in a new project, or playing with it directly in the browser on Tailwind Play.

For existing projects, we've published a comprehensive upgrade guide and built an automated upgrade tool to get you on the latest version as quickly and painlessly as possible.

For a deep-dive into everything that's new, check out the announcement post.

vitest-dev/vitest (vitest)

v3.0.5

Compare Source

🚀 Features
🐞 Bug Fixes
View changes on GitHub

v3.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.1.9

Compare Source

   🚨 Bre

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

Copy link

cloudflare-workers-and-pages bot commented Jan 16, 2025

Deploying server-radar with  Cloudflare Pages  Cloudflare Pages

Latest commit: 22a230b
Status:🚫  Build failed.

View logs

Copy link
Contributor Author

renovate bot commented Jan 16, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @cloudflare/vitest-pool-workers@0.5.32
npm error Found: vitest@3.0.5
npm error node_modules/vitest
npm error   dev vitest@"^3.0.0" from the root project
npm error   dev vitest@"3.0.5" from email-queue-worker@0.0.0
npm error   workers/email-queue-worker
npm error     email-queue-worker@0.0.0
npm error     node_modules/email-queue-worker
npm error       workspace workers/email-queue-worker from the root project
npm error   1 more (rate-limiter)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"2.0.x - 2.1.x" from @cloudflare/vitest-pool-workers@0.5.32
npm error node_modules/@cloudflare/vitest-pool-workers
npm error   dev @cloudflare/vitest-pool-workers@"^0.5.2" from email-queue-worker@0.0.0
npm error   workers/email-queue-worker
npm error     email-queue-worker@0.0.0
npm error     node_modules/email-queue-worker
npm error       workspace workers/email-queue-worker from the root project
npm error   dev @cloudflare/vitest-pool-workers@"^0.5.2" from rate-limiter@0.0.0
npm error   workers/rate-limiter
npm error     rate-limiter@0.0.0
npm error     node_modules/rate-limiter
npm error       workspace workers/rate-limiter from the root project
npm error
npm error Conflicting peer dependency: vitest@2.1.9
npm error node_modules/vitest
npm error   peer vitest@"2.0.x - 2.1.x" from @cloudflare/vitest-pool-workers@0.5.32
npm error   node_modules/@cloudflare/vitest-pool-workers
npm error     dev @cloudflare/vitest-pool-workers@"^0.5.2" from email-queue-worker@0.0.0
npm error     workers/email-queue-worker
npm error       email-queue-worker@0.0.0
npm error       node_modules/email-queue-worker
npm error         workspace workers/email-queue-worker from the root project
npm error     dev @cloudflare/vitest-pool-workers@"^0.5.2" from rate-limiter@0.0.0
npm error     workers/rate-limiter
npm error       rate-limiter@0.0.0
npm error       node_modules/rate-limiter
npm error         workspace workers/rate-limiter from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-02-03T17_30_52_594Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-03T17_30_52_594Z-debug-0.log

File name: workers/rate-limiter/package-lock.json
npm warn config ignoring workspace config at /tmp/renovate/repos/github/elsbrock/hetzner-radar/workers/rate-limiter/.npmrc
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @cloudflare/vitest-pool-workers@0.5.32
npm error Found: vitest@3.0.5
npm error node_modules/vitest
npm error   dev vitest@"^3.0.0" from the root project
npm error   dev vitest@"3.0.5" from email-queue-worker@0.0.0
npm error   workers/email-queue-worker
npm error     email-queue-worker@0.0.0
npm error     node_modules/email-queue-worker
npm error       workspace workers/email-queue-worker from the root project
npm error   1 more (rate-limiter)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"2.0.x - 2.1.x" from @cloudflare/vitest-pool-workers@0.5.32
npm error node_modules/@cloudflare/vitest-pool-workers
npm error   dev @cloudflare/vitest-pool-workers@"^0.5.2" from email-queue-worker@0.0.0
npm error   workers/email-queue-worker
npm error     email-queue-worker@0.0.0
npm error     node_modules/email-queue-worker
npm error       workspace workers/email-queue-worker from the root project
npm error   dev @cloudflare/vitest-pool-workers@"^0.5.2" from rate-limiter@0.0.0
npm error   workers/rate-limiter
npm error     rate-limiter@0.0.0
npm error     node_modules/rate-limiter
npm error       workspace workers/rate-limiter from the root project
npm error
npm error Conflicting peer dependency: vitest@2.1.9
npm error node_modules/vitest
npm error   peer vitest@"2.0.x - 2.1.x" from @cloudflare/vitest-pool-workers@0.5.32
npm error   node_modules/@cloudflare/vitest-pool-workers
npm error     dev @cloudflare/vitest-pool-workers@"^0.5.2" from email-queue-worker@0.0.0
npm error     workers/email-queue-worker
npm error       email-queue-worker@0.0.0
npm error       node_modules/email-queue-worker
npm error         workspace workers/email-queue-worker from the root project
npm error     dev @cloudflare/vitest-pool-workers@"^0.5.2" from rate-limiter@0.0.0
npm error     workers/rate-limiter
npm error       rate-limiter@0.0.0
npm error       node_modules/rate-limiter
npm error         workspace workers/rate-limiter from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-02-03T17_30_57_243Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-03T17_30_57_243Z-debug-0.log

File name: workers/email-queue-worker/package-lock.json
npm warn config ignoring workspace config at /tmp/renovate/repos/github/elsbrock/hetzner-radar/workers/email-queue-worker/.npmrc
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @cloudflare/vitest-pool-workers@0.5.32
npm error Found: vitest@3.0.5
npm error node_modules/vitest
npm error   dev vitest@"^3.0.0" from the root project
npm error   dev vitest@"3.0.5" from email-queue-worker@0.0.0
npm error   workers/email-queue-worker
npm error     email-queue-worker@0.0.0
npm error     node_modules/email-queue-worker
npm error       workspace workers/email-queue-worker from the root project
npm error   1 more (rate-limiter)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"2.0.x - 2.1.x" from @cloudflare/vitest-pool-workers@0.5.32
npm error node_modules/@cloudflare/vitest-pool-workers
npm error   dev @cloudflare/vitest-pool-workers@"^0.5.2" from email-queue-worker@0.0.0
npm error   workers/email-queue-worker
npm error     email-queue-worker@0.0.0
npm error     node_modules/email-queue-worker
npm error       workspace workers/email-queue-worker from the root project
npm error   dev @cloudflare/vitest-pool-workers@"^0.5.2" from rate-limiter@0.0.0
npm error   workers/rate-limiter
npm error     rate-limiter@0.0.0
npm error     node_modules/rate-limiter
npm error       workspace workers/rate-limiter from the root project
npm error
npm error Conflicting peer dependency: vitest@2.1.9
npm error node_modules/vitest
npm error   peer vitest@"2.0.x - 2.1.x" from @cloudflare/vitest-pool-workers@0.5.32
npm error   node_modules/@cloudflare/vitest-pool-workers
npm error     dev @cloudflare/vitest-pool-workers@"^0.5.2" from email-queue-worker@0.0.0
npm error     workers/email-queue-worker
npm error       email-queue-worker@0.0.0
npm error       node_modules/email-queue-worker
npm error         workspace workers/email-queue-worker from the root project
npm error     dev @cloudflare/vitest-pool-workers@"^0.5.2" from rate-limiter@0.0.0
npm error     workers/rate-limiter
npm error       rate-limiter@0.0.0
npm error       node_modules/rate-limiter
npm error         workspace workers/rate-limiter from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-02-03T17_31_00_579Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-03T17_31_00_579Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-major branch 4 times, most recently from 7d07a72 to 7ff644e Compare January 23, 2025 01:24
@renovate renovate bot changed the title chore(deps): update dependency vitest to v3 chore(deps): update major (major) Jan 23, 2025
@renovate renovate bot force-pushed the renovate/major-major branch 3 times, most recently from 1dc11a9 to 1eaad26 Compare January 30, 2025 12:28
@renovate renovate bot force-pushed the renovate/major-major branch 2 times, most recently from 7dfeb3e to 538b834 Compare February 2, 2025 18:01
@renovate renovate bot force-pushed the renovate/major-major branch from 538b834 to 22a230b Compare February 3, 2025 17:31
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.

1 participant