Skip to content

chore(deps): bump the production-dependencies group across 2 directories with 6 updates - #944

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-20fad4ae0f
Open

chore(deps): bump the production-dependencies group across 2 directories with 6 updates#944
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-20fad4ae0f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 25, 2026

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 5 updates in the / directory:

Package From To
diff 8.0.4 9.0.0
eta 4.5.1 4.6.0
figlet 1.11.0 1.11.4
inversify 8.1.0 8.2.3
typescript 5.9.3 7.0.2

Bumps the production-dependencies group with 1 update in the /tests/test-react-project directory: react.

Updates diff from 8.0.4 to 9.0.0

Changelog

Sourced from diff's changelog.

9.0.0

(All changes part of PR #672.)

  • ES5 support is dropped. parsePatch now uses TextDecoder and Uint8Array, which are not available in ES5, and TypeScript is now compiled with the "es6" target. From now on, I intend to freely use any features that are deemed "Widely available" by Baseline. Users who need ES5 support should stick to version 8.

  • C-style quoted strings in filename headers are now properly supported.

    When the name of either the old or new file in a patch contains "special characters", both GNU diff and Git quote the filename in the patch's headers and escape special characters using the same escape sequences that are used in string literals in C, including octal escapes for all non-ASCII characters. Previously, jsdiff had very little support for this; parsePatch would remove the quotes, and unescape any escaped backslashes, but would not unescape other escape sequences. formatPatch, meanwhile, did not quote or escape special characters at all.

    Now, parsePatch parses all the possible escape sequences that GNU diff (or Git) ever output, and formatPatch quotes and escapes filenames containing special characters in the same way GNU diff does.

  • formatPatch now omits file headers when oldFileName or newFileName in the provided patch object are undefined, regardless of the headerOptions parameter. (Previously, it would treat the absence of oldFileName or newFileName as indicating the filename was the word "undefined" and emit headers --- undefined / +++ undefined.)

  • formatPatch no longer outputs trailing tab characters at the end of ---/+++ headers.

    Previously, if formatPatch was passed a patch object to serialize that had empty strings for the oldHeader or newHeader property, it would include a trailing tab character after the filename in the --- and/or +++ file header. Now, this scenario is treated the same as when oldHeader/newHeader is undefined - i.e. the trailing tab is omitted.

  • formatPatch no longer mutates its input when serializing a patch containing a hunk where either the old or new content contained zero lines. (Such a hunk occurs only when the hunk has no context lines and represents a pure insertion or pure deletion, which for instance will occur whenever one of the two files being diffed is completely empty.) Previously formatPatch would provide the correct output but also mutate the oldLines or newLines property on the hunk, changing the meaning of the underlying patch.

  • Git-style patches are now supported by parsePatch, formatPatch, and reversePatch.

    Patches output by git diff can include some features that are unlike those output by GNU diff, and therefore not handled by an ordinary unified diff format parser. An ordinary diff simply describes the differences between the content of two files, but Git diffs can also indicate, via "extended headers", the creation or deletion of (potentially empty) files, indicate that a file was renamed, and contain information about file mode changes. Furthermore, when these changes appear in a diff in the absence of a content change (e.g. when an empty file is created, or a file is renamed without content changes), the patch will contain no associated ---/+++ file headers nor any hunks.

    jsdiff previously did not support parsing Git's extended headers, nor hunkless patches. Now parsePatch parses some of the extended headers, parses hunkless Git patches, and can determine filenames (e.g. from the extended headers) when parsing a patch that includes no --- or +++ file headers. The additional information conveyed by the extended headers we support is recorded on new fields on the result object returned by parsePatch. See isGit and subsequent properties in the docs in the README.md file.

    formatPatch now outputs extended headers based on these new Git-specific properties, and reversePatch respects them as far as possible (with one unavoidable caveat noted in the README.md file).

  • Unpaired file headers now cause parsePatch to throw.

    It remains acceptable to have a patch with no file headers whatsoever (e.g. one that begins with a @@ hunk header on the very first line), but a patch with only a --- header or only a +++ header is now considered an error.

  • parsePatch is now more tolerant of "trailing garbage"

    That is: after a patch, or between files/indexes in a patch, it is now acceptable to have arbitrary lines of "garbage" (so long as they unambiguously have no syntactic meaning - e.g. trailing garbage that leads with a +, -, or and thus is interpretable as part of a hunk still triggers a throw).

    This means we no longer reject patches output by tools that include extra data in "garbage" lines not understood by generic unified diff parsers. (For example, SVN patches can include "Property changes on:" lines that generic unified diff parsers should discard as garbage; jsdiff previously threw errors when encountering them.)

    This change brings jsdiff's behaviour more in line with GNU patch, which is highly permissive of "garbage".

  • The oldFileName and newFileName fields of StructuredPatch are now typed as string | undefined instead of string. This type change reflects the (pre-existing) reality that parsePatch can produce patches without filenames (e.g. when parsing a patch that simply contains hunks with no file headers).

Commits

Updates eta from 4.5.1 to 4.6.0

Changelog

Sourced from eta's changelog.

4.6.0 (2026-04-25)

Features

  • add block and blockAsync template helpers (#367) (083954b)
  • add capture and captureAsync template helpers (#365) (2350544)
  • add support for custom tag types (5105744)
Commits
  • 95982e5 chore(main): release 4.6.0 (#366)
  • 5105744 feat: add support for custom tag types
  • acff516 docs: mention blocks in README feature list
  • 083954b feat: add block and blockAsync template helpers (#367)
  • 2350544 feat: add capture and captureAsync template helpers (#365)
  • See full diff in compare view

Updates figlet from 1.11.0 to 1.11.4

Release notes

Sourced from figlet's releases.

1.11.4

1.11.3

Bug fix for invalid input that can lead to infinite loop.

Commits

Updates inversify from 8.1.0 to 8.2.3

Release notes

Sourced from inversify's releases.

inversify@8.2.3

Patch Changes

  • Updated dependencies
    • @​inversifyjs/core@​15.0.1
    • @​inversifyjs/container@​3.1.3

inversify@8.2.2

Patch Changes

  • Updated dependencies
    • @​inversifyjs/core@​15.0.0
    • @​inversifyjs/container@​3.1.2

inversify@8.2.1

Patch Changes

  • Fixed resolved value binding resolution to respect the jitless container option, avoiding Function constructor usage in CSP-restricted environments.
  • Updated dependencies
    • @​inversifyjs/core@​14.0.0
    • @​inversifyjs/container@​3.1.1

inversify@8.2.0

Minor Changes

  • Updated ContainerOptions with optional jitless (default true).

Patch Changes

  • Updated resolution flow with better inlined constructor calls.
  • Updated instance resolution flow to rely on inlined functions also in property injected services.
  • Updated resolution algorithm to rely on jit options to avoid CSP related issues.
  • Updated dependencies
    • @​inversifyjs/container@​3.1.0
    • @​inversifyjs/core@​13.0.0

inversify@8.1.3

Patch Changes

  • Improved instance transient scoped resolution performance forcing inlined v8 constructor calls.
  • Updated dependencies
    • @​inversifyjs/core@​12.0.1
    • @​inversifyjs/container@​3.0.1

inversify@8.1.2

Patch Changes

  • Deep redirection bindings are now properly refreshed in the plan cache when relevant bindings are added or removed
  • Updated dependencies
    • @​inversifyjs/container@​3.0.0

... (truncated)

Commits
  • 5ba2e20 Merge pull request #2023 from inversify/changeset-release/main
  • 1123fa9 chore: bump package versions
  • be063f1 Merge pull request #2022 from inversify/fix/resolution-on-jit-for-big-arity
  • 68ebd78 test: improve assertions
  • 063632c fix: jit resolution
  • eefb744 Merge pull request #2021 from inversify/perf/improve-dynamic-value-resolution
  • c494a54 chore: update benchmark scenarios with async flows
  • 8608291 chore: add container benchmark scenario
  • 9a858d9 perf: update DynamicValueBinding
  • 6057964 chore: update vitest config to exclude fixtures from coverage
  • Additional commits viewable in compare view

Updates typescript from 5.9.3 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0 Beta

For release notes, check out the release announcement.

Downloads are available on:

Commits
Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.


Updates react from 19.2.4 to 19.2.8

Release notes

Sourced from react's releases.

19.2.8 (July 21st, 2026)

React Server Components

19.2.7 (June 1st, 2026)

React Server Components

19.2.6 (May 6th, 2026)

React Server Components

19.2.5 (April 8th, 2026)

React Server Components

Changelog

Sourced from react's changelog.

19.2.7 (June 1, 2026)

React Server Components

19.2.6 (May 6, 2026)

React Server Components

19.2.5 (March 18, 2026)

React Server Components

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react since your current version.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jul 25, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Hi, thank you for creating your PR, we will check it out very soon

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/production-dependencies-20fad4ae0f branch from 35ca5a7 to a696163 Compare July 31, 2026 04:11
…ies with 6 updates

Bumps the production-dependencies group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [diff](https://github.com/kpdecker/jsdiff) | `8.0.4` | `9.0.0` |
| [eta](https://github.com/bgub/eta) | `4.5.1` | `4.6.0` |
| [figlet](https://github.com/patorjk/figlet.js) | `1.11.0` | `1.11.4` |
| [inversify](https://github.com/inversify/monorepo) | `8.1.0` | `8.2.3` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.9.3` | `7.0.2` |

Bumps the production-dependencies group with 1 update in the /__tests__/test-react-project directory: [react](https://github.com/react/react/tree/HEAD/packages/react).


Updates `diff` from 8.0.4 to 9.0.0
- [Changelog](https://github.com/kpdecker/jsdiff/blob/master/release-notes.md)
- [Commits](kpdecker/jsdiff@8.0.4...v9.0.0)

Updates `eta` from 4.5.1 to 4.6.0
- [Release notes](https://github.com/bgub/eta/releases)
- [Changelog](https://github.com/bgub/eta/blob/main/CHANGELOG.md)
- [Commits](bgub/eta@v4.5.1...v4.6.0)

Updates `figlet` from 1.11.0 to 1.11.4
- [Release notes](https://github.com/patorjk/figlet.js/releases)
- [Commits](patorjk/figlet.js@v1.11.0...v1.11.4)

Updates `inversify` from 8.1.0 to 8.2.3
- [Release notes](https://github.com/inversify/monorepo/releases)
- [Changelog](https://github.com/inversify/monorepo/blob/main/docs/release.md)
- [Commits](https://github.com/inversify/monorepo/compare/inversify@8.1.0...inversify@8.2.3)

Updates `typescript` from 5.9.3 to 7.0.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](https://github.com/microsoft/TypeScript/commits)

Updates `react` from 19.2.4 to 19.2.8
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.2.8/packages/react)

---
updated-dependencies:
- dependency-name: diff
  dependency-version: 9.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
- dependency-name: eta
  dependency-version: 4.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: figlet
  dependency-version: 1.11.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: inversify
  dependency-version: 8.2.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: react
  dependency-version: 19.2.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/production-dependencies-20fad4ae0f branch from a696163 to 1d2f2e3 Compare August 7, 2026 04:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants