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 all non-major dependencies #197

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 3, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) ^2.27.8 -> ^2.27.9 age adoption passing confidence
@eslint/js (source) ^9.10.0 -> ^9.12.0 age adoption passing confidence
@vitest/coverage-v8 (source) ^2.0.5 -> ^2.1.2 age adoption passing confidence
esbuild ^0.23.1 -> ^0.24.0 age adoption passing confidence
eslint (source) ^9.10.0 -> ^9.12.0 age adoption passing confidence
eslint-plugin-n ^17.10.2 -> ^17.11.1 age adoption passing confidence
get-tsconfig ^4.8.0 -> ^4.8.1 age adoption passing confidence
husky ^9.1.5 -> ^9.1.6 age adoption passing confidence
npm-run-all2 ^6.2.2 -> ^6.2.3 age adoption passing confidence
pnpm (source) 9.10.0 -> 9.12.1 age adoption passing confidence
publint (source) ^0.2.10 -> ^0.2.11 age adoption passing confidence
typescript (source) ^5.6.2 -> ^5.6.3 age adoption passing confidence
vitest (source) ^2.0.5 -> ^2.1.2 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.9

Compare Source

Patch Changes
eslint/eslint (@​eslint/js)

v9.12.0

Compare Source

Features

Bug Fixes

Documentation

  • ecbd522 docs: Mention code explorer (#​18978) (Nicholas C. Zakas)
  • 7ea4ecc docs: Clarifying the Use of Meta Objects (#​18697) (Amaresh S M)
  • d3e4b2e docs: Clarify how to exclude .js files (#​18976) (Milos Djermanovic)
  • 57232ff docs: Mention plugin-kit in language docs (#​18973) (Nicholas C. Zakas)
  • b80ed00 docs: Update README (GitHub Actions Bot)
  • cb69ab3 docs: Update README (GitHub Actions Bot)
  • 7fb0d95 docs: Update README (GitHub Actions Bot)
  • 493348a docs: Update README (GitHub Actions Bot)
  • 87a582c docs: fix typo in id-match rule (#​18944) (Jay)

Chores

v9.11.1

Compare Source

Bug Fixes

  • 20fd916 fix: add @eslint/core, @types/estree, & @types/json-schema deps (#​18938) (Nitin Kumar)
  • 2738322 fix: add missing types for require-atomic-updates rule (#​18937) (Kristóf Poduszló)
  • d71ff30 fix: add missing types for object-shorthand rule (#​18935) (Kristóf Poduszló)
  • 561cadc fix: add missing types for no-unsafe-negation rule (#​18932) (Kristóf Poduszló)
  • 8843656 fix: add missing types for no-underscore-dangle rule (#​18931) (Kristóf Poduszló)
  • 92cde5c fix: add missing types for no-shadow rule (#​18930) (Kristóf Poduszló)
  • b3cbe11 fix: add missing types for no-sequences rule (#​18929) (Kristóf Poduszló)
  • 976f77f fix: add missing types for no-unused-expressions rule (#​18933) (Kristóf Poduszló)

Documentation

  • 3eff709 docs: replace deprecated Linter.FlatConfig type with Linter.Config (#​18941) (Carlos Meira)

Chores

v9.11.0

Compare Source

vitest-dev/vitest (@​vitest/coverage-v8)

v2.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild (esbuild)

v0.24.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#​3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#​3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#​3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#​3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#​3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.11.1

Compare Source

🩹 Fixes

v17.11.0

Compare Source

🌟 Features
🩹 Fixes
  • no-missing-import: Ignore node builtins in package.json imports (#​346) (148e47e)
  • no-missing-import: Resolve tsconfig paths relative to the tsconfig (#​343) (6cd7954)
📚 Documentation
  • Explain the transitive dependency case for no-extraneous-* (#​347) (8c0a2cc)

v17.10.3

Compare Source

🩹 Fixes
  • Use our data set to work out if a module is a node module (#​338) (6a1b2c5)
📚 Documentation
privatenumber/get-tsconfig (get-tsconfig)

v4.8.1

Compare Source

Bug Fixes
  • support configDir for other compilerOptions fields (#​84) (7e58ea3)
typicode/husky (husky)

v9.1.6

Compare Source

bcomnes/npm-run-all2 (npm-run-all2)

v6.2.3

Compare Source

Commits
  • Merge pull request #​151 from bcomnes/fix-pnpm-agian c43fa2b
  • Avoid passing config fields as flags for pnpm dc2d7da
pnpm/pnpm (pnpm)

v9.12.1: pnpm 9.12.1

Compare Source

Patch Changes

  • pnpm update --latest should not update the automatically installed peer dependencies #​6657.
  • pnpm publish should be able to publish from a local tarball #​7950.
  • The pnpx command should work correctly on Windows, when pnpm is installed via the standalone installation script #​8608.
  • Prevent EBUSY errors caused by creating symlinks in parallel dlx processes #​8604.
  • Fix maximum call stack size exceeded error related to circular workspace dependencies #​8599.

Platinum Sponsors

Gold Sponsors


Configuration

📅 Schedule: Branch creation - "before 5am on the 3rd day of the month" (UTC), 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.

@renovate renovate bot added the dependencies label Oct 3, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from f99e0a0 to 176f97a Compare October 9, 2024 10:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 176f97a to a8a4390 Compare October 9, 2024 13:05
@dominikg dominikg merged commit 108a07e into main Oct 10, 2024
7 checks passed
@dominikg dominikg deleted the renovate/all-minor-patch branch October 10, 2024 03:59
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