Skip to content

chore(deps): update all non-major dependencies #77

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
Merged
mscolnick merged 1 commit into from
Apr 24, 2025
Merged

chore(deps): update all non-major dependencies #77

mscolnick merged 1 commit into from
Apr 24, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@biomejs/biome (source) ^1.9.3 -> ^1.9.4 age adoption passing confidence devDependencies patch
@types/node (source) 22.9.0 -> 22.14.1 age adoption passing confidence devDependencies minor
@types/ws (source) ^8.5.12 -> ^8.18.1 age adoption passing confidence devDependencies minor
@vscode/test-electron ^2.4.1 -> ^2.5.2 age adoption passing confidence devDependencies minor
node 18.x -> 18.20.8 age adoption passing confidence uses-with minor
openapi-fetch (source) ^0.9.7 -> ^0.13.5 age adoption passing confidence devDependencies minor
openapi-typescript (source) ^7.4.1 -> ^7.6.1 age adoption passing confidence devDependencies patch
pnpm (source) 10.4.1 -> 10.9.0 age adoption passing confidence packageManager minor
tsup (source) ^8.3.0 -> ^8.4.0 age adoption passing confidence devDependencies minor
vitest (source) ^3.0.2 -> ^3.1.2 age adoption passing confidence devDependencies minor
vscode ^1.95.0 -> ^1.99.3 age adoption passing confidence engines minor
ws ^8.17.0 -> ^8.18.1 age adoption passing confidence devDependencies patch

Release Notes

Microsoft/vscode-test (@​vscode/test-electron)

v2.5.2

Compare Source

  • Fix install issue on various platforms

v2.5.1

Compare Source

  • Allow downloading server versions
actions/node-versions (node)

v18.20.8: 18.20.8

Compare Source

Node.js 18.20.8

v18.20.7: 18.20.7

Compare Source

Node.js 18.20.7

v18.20.6: 18.20.6

Compare Source

Node.js 18.20.6

v18.20.5: 18.20.5

Compare Source

Node.js 18.20.5

v18.20.4: 18.20.4

Compare Source

Node.js 18.20.4

v18.20.3: 18.20.3

Compare Source

Node.js 18.20.3

v18.20.2: 18.20.2

Compare Source

Node.js 18.20.2

v18.20.1: 18.20.1

Compare Source

Node.js 18.20.1

v18.20.0: 18.20.0

Compare Source

Node.js 18.20.0

v18.19.1: 18.19.1

Compare Source

Node.js 18.19.1

v18.19.0: 18.19.0

Compare Source

Node.js 18.19.0

v18.18.2: 18.18.2

Compare Source

Node.js 18.18.2

v18.18.1: 18.18.1

Compare Source

Node.js 18.18.1

v18.18.0: 18.18.0

Compare Source

Node.js 18.18.0

v18.17.1: 18.17.1

Compare Source

Node.js 18.17.1

v18.17.0: 18.17.0

Compare Source

Node.js 18.17.0

v18.16.1: 18.16.1

Compare Source

Node.js 18.16.1

v18.16.0: 18.16.0

Compare Source

Node.js 18.16.0

v18.15.0: 18.15.0

Compare Source

Node.js 18.15.0

v18.14.2: 18.14.2

Compare Source

Node.js 18.14.2

v18.14.1: 18.14.1

Compare Source

Node.js 18.14.1

v18.14.0: 18.14.0

Compare Source

Node.js 18.14.0

v18.13.0: 18.13.0

Compare Source

Node.js 18.13.0

v18.12.1: 18.12.1

Compare Source

Node.js 18.12.1

v18.12.0: 18.12.0

Compare Source

Node.js 18.12.0

v18.11.0: 18.11.0

Compare Source

Node.js 18.11.0

v18.10.0: 18.10.0

Compare Source

Node.js 18.10.0

v18.9.1: 18.9.1

Compare Source

Node.js 18.9.1

v18.9.0: 18.9.0

Compare Source

Node.js 18.9.0

v18.8.0: 18.8.0

Compare Source

Node.js 18.8.0

v18.7.0: 18.7.0

Compare Source

Node.js 18.7.0

v18.6.0: 18.6.0

Compare Source

Node.js 18.6.0

v18.5.0: 18.5.0

Compare Source

Node.js 18.5.0

v18.4.0: 18.4.0

Compare Source

Node.js 18.4.0

v18.3.0: 18.3.0

Compare Source

Node.js 18.3.0

v18.2.0: 18.2.0

Compare Source

Node.js 18.2.0

v18.1.0: 18.1.0

Compare Source

Node.js 18.1.0

openapi-ts/openapi-typescript (openapi-fetch)

v0.13.5

Compare Source

Patch Changes

v0.13.4

Compare Source

Patch Changes

v0.13.3

Patch Changes

Refresh of 0.13.2; corrupted package

v0.13.2

Patch Changes

v0.13.1

Compare Source

Patch Changes

v0.13.0

Compare Source

Minor Changes
  • #​1968 267977e Thanks @​DjordyKoert! - 204 responses or response with a Content-Length of 0 will now return undefined instead of an empty object

v0.12.5

Compare Source

Patch Changes

v0.12.4

Compare Source

Patch Changes

v0.12.3

Compare Source

Patch Changes

v0.12.2

Compare Source

Patch Changes

v0.12.1

Compare Source

Patch Changes

v0.12.0

Compare Source

Minor Changes

v0.11.3

Compare Source

Patch Changes

v0.11.2

Compare Source

Patch Changes

v0.11.1

Compare Source

Patch Changes

v0.11.0

Compare Source

Minor Changes

-- ⚠️ Breaking Change #​1791 a956d5d Thanks @​gzm0! - Add support for client["/endpoint"].GET() style calls

v0.10.6

Compare Source

Patch Changes

v0.10.5

Compare Source

Patch Changes

v0.10.4

Compare Source

Patch Changes

v0.10.3

Compare Source

Patch Changes

v0.10.2

Compare Source

Patch Changes

v0.10.1

Compare Source

Patch Changes

v0.10.0

Compare Source

Minor Changes

  • ⚠️ Breaking Change: openapi-typescript@7 is needed to work. You’ll get type errors with openapi-typescript@6 and below.

  • ⚠️ Breaking Change: The Middleware API has changed to be an object rather than (request, options) or (response, options). See Middleware docs for updated API.

  • ⚠️ Breaking Change: The Content-Type header is no longer sent by default if a body payload is attached.

  • ⚠️ Breaking Change: The customFetch type now calls fetch(input: string, init: RequestInit) and the types have been updated, rather than fetch(input: Request) introduced in 0.9.0.

  • Added id to middleware handlers that create a unique ID per-fetch

pnpm/pnpm (pnpm)

v10.9.0

Compare Source

Minor Changes

  • Added support for installing JSR packages. You can now install JSR packages using the following syntax:

    pnpm add jsr:<pkg_name>

    or with a version range:

    pnpm add jsr:<pkg_name>@&#8203;<range>

    For example, running:

    pnpm add jsr:@&#8203;foo/bar

    will add the following entry to your package.json:

    {
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}

    When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:

    {
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}

    Related issue: #​8941.

    Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.

  • Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:

    neverBuiltDependencies: []

    dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:

    pnpm config set dangerouslyAllowAllBuilds true

    It can also be set when running a command:

    pnpm install --dangerously-allow-all-builds
Patch Changes
  • Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #​9424.
  • Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

v10.8.1

Compare Source

Patch Changes
  • Removed bright white highlighting, which didn't look good on some light themes #​9389.
  • If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #​9404.

v10.8.0

Compare Source

Minor Changes

  • Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

    module.exports = {
  hooks: {
    updateConfig: (config) => ({
      ...config,
      nodeLinker: "hoisted",
    }),
  },
};

  • Now you can use the pnpm add command with the --config flag to install new configurational dependencies #​9377.

Patch Changes
  • Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #​9169.
  • pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
  • pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #​9365.

v10.7.1: pnpm 10.7.1

Compare Source

Patch Changes

  • pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #​9355.
  • pnpm config get should read auth related settings via npm CLI #​9345.
  • Replace leading ~/ in a path in .npmrc with the home directory #​9217.

Platinum Sponsors

Bit Bit Syntax

Gold Sponsors

Discord u|screen
JetBrains Nx
CodeRabbit Route4Me
Workleap Stackblitz

v10.7.0

Compare Source

Minor Changes

  • pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

  • It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

  • Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

    For example:

    patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  [email protected]: patches/foo-3.patch

    The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

    [!WARNING]
    The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

    # pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  '[email protected]': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

    In most cases, however, it's sufficient to just define an exact version to override the range.

  • pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

  • Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

  • Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

    If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

    If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

    If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes
  • Remove dependency paths from audit output to prevent out-of-memory errors #​9280.

v10.6.5

Compare Source

v10.6.4: pnpm 10.6.4

Compare Source

Patch Changes

  • Fix pnpm dlx with --allow-build flag #​9263.
  • Invalid Node.js version in use-node-version should not cause pnpm itself to break #​9276.
  • The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #​9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

Platinum Sponsors

Bit Bit Syntax

Gold Sponsors

Discord u|screen
JetBrains Nx
CodeRabbit Route4Me
Workleap Stackblitz

v10.6.3

Compare Source

Patch Changes

  • pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #​9233. This fixes regression introduced via #​9211.

  • Add the missing node-options config to recursive run #​9180.

  • Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

    See details in #​9259.

v10.6.2

Compare Source

Patch Changes
  • pnpm self-update should always update the version in the packageManager field of package.json.
  • Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #​8971.
  • pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
  • Don't show info output when --loglevel=error is used.
  • peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

v10.6.1

Compare Source

Patch Changes
  • The pnpm CLI process should not stay hanging, when --silent reporting is used.
  • When --loglevel is set to error, don't show installation summary, execution time, and big tarball download progress.
  • Don't ignore pnpm.patchedDependencies from package.json #​9226.
  • When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.
  • When a package version cannot be found in the package metadata, print the registry from which the package was fetched.

v10.6.0

Compare Source

Minor Changes

  • pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #​9211.

    pnpm-workspace.yaml example:

    verifyDepsBeforeRun: install
optimisticRepeatInstall: true
publicHoistPattern:
  - "*types*"
  - "!@&#8203;types/react"

  • Projects using a file: dependency on a local tarball file (i.e. .tgz, .tar.gz, .tar) will see a performance improvement during installation. Previously, using a file: dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.

Patch Changes
  • pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
  • fast-glob replace with tinyglobby to reduce the size of the pnpm CLI dependencies #​9169.
  • pnpm deploy should not remove fields from the deployed package's package.json file #​9215.
  • pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
  • Fix pnpm deploy creating a package.json without the imports and license field #​9193.
  • pnpm update -i should list only packages that have newer versions #​9206.
  • Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #​9112

v10.5.2

[Compare Source](https://github.com/pnpm/pnpm/c

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (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 force-pushed the renovate/all-minor-patch branch 8 times, most recently from d711769 to 614b108 Compare March 1, 2025 10:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 112a83d to c574a7e Compare March 10, 2025 22:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 8085e23 to a0a1f98 Compare March 17, 2025 17:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 0af9275 to 49b3dbf Compare March 26, 2025 12:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3f6e961 to 712cd48 Compare March 31, 2025 11:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 2406985 to e0909f6 Compare April 7, 2025 23:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from a599be0 to b77122b Compare April 14, 2025 11:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b77122b to aead237 Compare April 16, 2025 18:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from aead237 to e82fdda Compare April 21, 2025 10:00
@mscolnick mscolnick merged commit 84fda8f into main Apr 24, 2025
1 of 3 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch April 24, 2025 17:38
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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mscolnick