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

chore(deps): update dev dependencies #489

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

chore(deps): update dev dependencies #489

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 31, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@commitlint/cli (source) 19.6.1 -> 19.7.1 age adoption passing confidence
@commitlint/config-conventional (source) 19.6.0 -> 19.7.1 age adoption passing confidence
@eslint/compat 1.2.5 -> 1.2.6 age adoption passing confidence
@eslint/js (source) 9.18.0 -> 9.20.0 age adoption passing confidence
@playwright/test (source) 1.49.1 -> 1.50.1 age adoption passing confidence
commitlint (source) 19.6.1 -> 19.7.1 age adoption passing confidence
eslint (source) 9.18.0 -> 9.20.1 age adoption passing confidence
eslint-config-next (source) 15.1.5 -> 15.1.7 age adoption passing confidence
postcss (source) 8.5.1 -> 8.5.2 age adoption passing confidence
prettier (source) 3.4.2 -> 3.5.1 age adoption passing confidence
prettier-plugin-tailwindcss 0.6.10 -> 0.6.11 age adoption passing confidence
prisma (source) 6.2.1 -> 6.3.1 age adoption passing confidence
remark-gfm 4.0.0 -> 4.0.1 age adoption passing confidence
tailwindcss (source) 3.4.17 -> 4.0.6 age adoption passing confidence
typescript-eslint (source) 8.21.0 -> 8.24.1 age adoption passing confidence

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v19.7.1

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.7.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

eslint/rewrite (@​eslint/compat)

v1.2.6

Compare Source

eslint/eslint (@​eslint/js)

v9.20.0

Compare Source

Features

  • e89a54a feat: change behavior of inactive flags (#​19386) (Milos Djermanovic)

Bug Fixes

  • 91d4d9f fix: Bring types in sync with @​eslint/core (#​19157) (Nicholas C. Zakas)
  • fa25c7a fix: Emit warning when empty config file is used (#​19399) (Nicholas C. Zakas)
  • 31a9fd0 fix: Clearer error message for wrong plugin format (#​19380) (Nicholas C. Zakas)
  • 61d99e3 fix: Better error message for unserializable parser (#​19384) (Nicholas C. Zakas)
  • db1b9a6 fix: Ensure module scope is checked for references in consistent-this (#​19383) (Nicholas C. Zakas)
  • 8bcd820 fix: arrow-body-style crash with single-token body (#​19379) (Milos Djermanovic)

Documentation

  • b7012c8 docs: rewrite examples with var using let and const (#​19407) (Mueez Javaid Hashmi)
  • 6406376 docs: Update README (GitHub Actions Bot)
  • 350f2b9 docs: rewrite some examples with var using let and const (#​19404) (Mueez Javaid Hashmi)
  • 93c325a docs: rewrite examples with var using let and const (#​19398) (Mueez Javaid Hashmi)
  • 56ff404 docs: replace var with let or const in rules docs (#​19396) (Daniel Harbrueger)
  • 4053226 docs: change sourceType in no-eval examples (#​19393) (Milos Djermanovic)
  • 1324af0 docs: replace var with let and const in rules docs (#​19392) (Daniel Harbrueger)
  • 8b87e00 docs: replace var with const and let in rules (#​19389) (Tanuj Kanti)
  • 758c66b docs: Explain what frozen rules mean (#​19382) (Nicholas C. Zakas)
  • 0ef8bb8 docs: additional checks for rule examples (#​19358) (Milos Djermanovic)
  • 58ab2f6 docs: fix order of installation steps in getting started (#​19326) (Tanuj Kanti)

Chores

v9.19.0

Compare Source

Features

  • 1637b8e feat: add --report-unused-inline-configs (#​19201) (Josh Goldberg ✨)

Bug Fixes

  • aae6717 fix: sync rule type header comments automatically (#​19276) (Francesco Trotta)

Documentation

  • cfea9ab docs: Clarify overrideConfig option (#​19370) (Nicholas C. Zakas)
  • 2b84f66 docs: Update README (#​19362) (Nicholas C. Zakas)
  • 044f93c docs: clarify frozen rule description (#​19351) (Pavel)
  • 797ee7c docs: fix Bluesky links (#​19368) (Milos Djermanovic)
  • 81a9c0e docs: Update README (GitHub Actions Bot)
  • 093fb3d docs: replace var with let and const in rule examples (#​19365) (Tanuj Kanti)
  • 417de32 docs: replace var with const in rule examples (#​19352) (jj)
  • 17f2aae docs: update getting-started config to match default generated config (#​19308) (0xDev)
  • 8a0a5a8 docs: better global ignores instruction (#​19297) (Jacopo Marrone)
  • 6671a2c docs: Update README (GitHub Actions Bot)
  • e39d3f2 docs: fix divider for rule category (#​19264) (Tanuj Kanti)
  • e0cf53f docs: fix search result box position for small screens (#​19328) (Tanuj Kanti)
  • f92a680 docs: replace var with let or const in rule examples (#​19331) (Ravi Teja Kolla)
  • b04b84b docs: revert accidental changes in TS config files docs (#​19336) (Francesco Trotta)

Chores

microsoft/playwright (@​playwright/test)

v1.50.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/34483 - [Feature]: single aria snapshot for different engines/browsershttps://github.com/microsoft/playwright/issues/344977 - [Bug]: Firefox not handling keepalive: true fetch requesthttps://github.com/microsoft/playwright/issues/3450404 - [Bug]: update snapshots not creating good difhttps://github.com/microsoft/playwright/issues/34507507 - [Bug]: snapshotPathTemplate doesnt work when multiple projehttps://github.com/microsoft/playwright/issues/344624462 - [Bug]: updateSnapshots "changed" throws an error

Browser Versions

  • Chromium 133.0.6943.16
  • Mozilla Firefox 134.0
  • WebKit 18.2

This version was also tested against the following stable channels:

  • Google Chrome 132
  • Microsoft Edge 132

v1.50.0

Compare Source

Test runner

  • New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

    test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

  • New method test.step.skip() to disable execution of a test step.

    test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

  • Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.

  • Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.

  • Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.

  • New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.

    npx playwright test --update-snapshots=changed --update-source-method=3way

  • Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.

  • Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.

  • New option pathTemplate for toHaveScreenshot and toMatchAriaSnapshot assertions in the testConfig.expect configuration.

UI updates

  • Updated default HTML reporter to improve display of attachments.
  • New button for picking elements to produce aria snapshots.
  • Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
  • Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
  • Call and Network panels now display additional time information.

Breaking

Browser Versions

  • Chromium 133.0.6943.16
  • Mozilla Firefox 134.0
  • WebKit 18.2

This version was also tested against the following stable channels:

  • Google Chrome 132
  • Microsoft Edge 132
conventional-changelog/commitlint (commitlint)

v19.7.1

Compare Source

Note: Version bump only for package commitlint

vercel/next.js (eslint-config-next)

v15.1.7

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • fix: work around setTimeout memory leak, improve wrappers (#​75727)
  • add additional x-middleware-set-cookie filtering (#​75869)
  • fix: ensure lint worker errors aren't silenced (#​75766)
Credits

Huge thanks to @​lubieowoce and @​ztanner for helping!

v15.1.6

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • fix: don't memory-leak promises passed to waitUntil (#​75041)
  • backport: fix prerender issue with intercepting routes + generateStaticParams (#​75170)
Credits

Huge thanks to @​lubieowoce and @​ztanner for helping!

postcss/postcss (postcss)

v8.5.2

Compare Source

prettier/prettier (prettier)

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

tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.6.11

Compare Source

  • Support TypeScript configs and plugins when using v4 (#​342)
prisma/prisma (prisma)

v6.3.1

Compare Source

This patch releases introduces improvements to the prisma init output when invoked to with the --db option.

Run npx prisma@latest init --db to get an instant Prisma Postgres database.

v6.3.0

Compare Source

Today, we are excited to share the 6.3.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

Highlights
A brand new Prisma Studio

In this release we've included several great improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our release blog post, but here's a short list:

Prisma Studio is back in the Console

Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in the Prisma Console and is available for all PostgreSQL and MySQL databases.

A new model viewer

Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place.

image

A new editing experience

If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once.

image

Clean up at the click of a button

When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start.

image

Add limit to updateMany() and deleteMany()

Previously, limit has not existed as a valid option in top level updateMany() and deleteMany() queries. In 6.3.0 limit is now available in these queries, bringing their features more in line with other query types.

You can use limit like the following:

await prisma.user.deleteMany({
  where: { column: 'value' },
  limit: 100,
});

This will limit the number of deleted users to 100 at maximum.

Sort generator fields deterministically

In previous version of Prisma ORM, the fields inside of a generator block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull could lead to re-ordering of fields.

In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull after you upgrade, but it will remain consistent afterwards.

Replace NOT IN with NOT EXISTS for PostgreSQL relation filters

In previous versions of Prisma ORM, when using the none or some relation filters, the SQL queries generated used NOT IN. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN with EXISTS in order to improve query performance.

A special thank you

We'd like to extend our heartfelt thanks to @​loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #​19249 and #​17303. Their insights and partnership have been invaluable in improving our product.

If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.

Fixes and improvements
Prisma Client
Prisma
Credits

Huge thanks to @​WhyAsh5114 for their contributions to this release!

remarkjs/remark-gfm (remark-gfm)

v4.0.1

Compare Source

Types
  • 4af823a Refactor to use interface for exposed types
  • 3a57a5b Add declaration maps
  • 76559f9 Refactor to use @imports
Docs

Full Changelog: remarkjs/remark-gfm@4.0.0...4.0.1

tailwindlabs/tailwindcss (tailwindcss)

v4.0.6

Compare Source

Fixed
  • Revert change to no longer include theme variables that aren't used in compiled CSS (#​16403)
  • 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)

v4.0.4

Compare Source

Fixed
  • Fix a crash when setting JS theme values to null (#​16210)
  • Ensure escaped underscores in CSS variables in arbitrary values are properly unescaped (#​16206)
  • Ensure that the containers JS theme key is added to the --container-* namespace (#​16169)
  • Ensure theme @keyframes are generated even if an --animation-* variable spans multiple lines (#​16237)
  • Vite: Skip parsing stylesheets with the ?commonjs-proxy flag (#​16238)
  • Fix order-first and order-last for Firefox (#​16266)
  • Fix support for older instruction sets on Linux x64 builds of the standalone CLI (#​16244)
  • Ensure NODE_PATH is respected when resolving JavaScript and CSS files (#​16274)
  • Ensure Node addons are packaged correctly with FreeBSD builds (#​16277)
  • Fix an issue where @variant inside a referenced stylesheet could cause a stack overflow (#​16300)

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.

typescript-eslint/typescript-eslint (typescript-eslint)

v8.24.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.24.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.23.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.22.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@vercel Vercel
Copy link

vercel bot commented Jan 31, 2025 •
edited
Loading

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

Name Status Preview Comments Updated (UTC)
translo ❌ Failed (Inspect) Jan 31, 2025 9:27pm

@renovate renovate bot changed the title chore(deps): update dependency tailwindcss to v4 chore(deps): update dev dependencies Feb 1, 2025
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
Renovate::Dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants