Skip to content

⬆ Bump the bun-packages group with 8 updates - #236

Merged
savannahostrowski merged 2 commits into
mainfrom
dependabot/bun/bun-packages-5eda58c467
Oct 1, 2026
Merged

savannahostrowski merged 2 commits into
mainfrom
dependabot/bun/bun-packages-5eda58c467

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the bun-packages group with 8 updates:

Package From To
p-map 7.0.6 7.0.8
posthog-node 5.51.2 5.53.0
web-tree-sitter 0.26.13 0.27.0
@biomejs/biome 2.5.10 2.5.14
@types/bun 1.4.0 1.4.2
@vscode/vsce 3.9.2 4.0.0
lint-staged 17.3.0 17.5.1
ovsx 1.1.1 1.2.0

Updates p-map from 7.0.6 to 7.0.8

Release notes

Sourced from p-map's releases.

v7.0.8

  • Fix pMapIterable calling next() on an exhausted source iterator 70479bf
  • Fix pMap hanging on a source that blocks in next() after it is exhausted 7c5cee7
  • Fix pMap preferring the sync iterator when the input has both 669fdc6
  • Fix pMapIterable calling the mapper for input that arrives after iteration stopped fca6099
  • Fix: Don't call return() on an exhausted source iterator in pMapIterable a97778a
  • Fix pMap not closing the source iterator when it rejects c82bd07
  • Fix pMapIterable not closing the source iterator when iteration stops early e7c2ecb
  • Fix pMap settling early when the source iterator throws with stopOnError: false 9c48f07
  • Fix pMapIterable continuing to pull input after the consumer stops iterating 6194e49

sindresorhus/p-map@v7.0.7...v7.0.8

v7.0.7

  • Fix unhandled rejection when an abandoned pMapIterable worker's next() rejects 354e035

sindresorhus/p-map@v7.0.6...v7.0.7

Commits
  • bc8380d 7.0.8
  • 70479bf Fix pMapIterable calling next() on an exhausted source iterator
  • 7c5cee7 Fix pMap hanging on a source that blocks in next() after it is exhausted
  • 669fdc6 Fix pMap preferring the sync iterator when the input has both
  • fca6099 Fix pMapIterable calling the mapper for input that arrives after iteration ...
  • a97778a Don't call return() on an exhausted source iterator in pMapIterable
  • c82bd07 Fix pMap not closing the source iterator when it rejects
  • e7c2ecb Fix pMapIterable not closing the source iterator when iteration stops early
  • 9c48f07 Fix pMap settling early when the source iterator throws with `stopOnError: ...
  • 6194e49 Fix pMapIterable continuing to pull input after the consumer stops iterating
  • Additional commits viewable in compare view

Updates posthog-node from 5.51.2 to 5.53.0

Release notes

Sourced from posthog-node's releases.

posthog-node@5.53.0

5.53.0

Minor Changes

  • #5050 31dd1ad Thanks @​posthog! - Read a feature flag's evaluation runtime with getFeatureFlagEvaluationRuntime(key) and getFeatureFlagKeysByEvaluationRuntime(runtime) (2026-09-23)

posthog-node@5.52.6

5.52.6

Patch Changes

  • #5078 f4704ac Thanks @​rubychilds! - Honor filters.holdout during local feature flag evaluation. A user in an experiment holdout now receives the holdout-<id> variant instead of being bucketed into a regular variant, matching how the server evaluates the same flag. The holdout is resolved before the release conditions, so a held-out user never reaches the flag's targeting — including when those conditions would have excluded them, so isFeatureEnabled can return true where it previously returned false. Experiments with an active holdout will see variant assignment change for the held-out share of traffic on upgrade, bringing locally evaluated assignments in line with server-evaluated ones. (2026-09-23)
  • Updated dependencies [f4704ac]:
    • @​posthog/core@​1.55.2

posthog-node@5.52.5

5.52.5

Patch Changes

  • #5018 9cd8ebd Thanks @​turnipdabeets! - Stop dropping long spans that end: maxSpanAgeMs now evicts spans only once maxLiveSpans is reached, so a span that runs past the age limit and then ends is exported, and its children are no longer orphaned. (2026-09-21)

  • #4800 aad7464 Thanks @​marandaneto! - Respect the definitions response's property_matching_version during local feature flag evaluation. Version 2 uses explicit boolean/string equality and per-member array matching, while missing or other versions retain service legacy matching (including empty-array truthiness). Preserve the version in Node definition caches and Convex persisted definitions, and propagate it through person, group, cohort and dependency evaluation without mixing snapshots during reloads. Existing numeric ambiguity fallback and SemVer parsing policies are unchanged. (2026-09-21)

  • Updated dependencies [9cd8ebd, aad7464]:

    • @​posthog/core@​1.55.1

posthog-node@5.52.4

5.52.4

Patch Changes

  • #4885 39a8980 Thanks @​decknamec! - Server-side feature flags now resolve in posthog-node and posthog-edge even when a proxy rewrites the request's User-Agent. Flags restricted to the client runtime now resolve to undefined in these SDKs, where a rewritten User-Agent previously let them through. (2026-09-15)
  • Updated dependencies [39a8980]:
    • @​posthog/core@​1.54.2

posthog-node@5.52.3

5.52.3

Patch Changes

  • #4941 07c1045 Thanks @​marandaneto! - Capture causes and AggregateError members with relationship metadata and individual stacks, limiting output to 50 entries and 1,000 member inspections. (2026-09-15)
  • Updated dependencies [07c1045]:
    • @​posthog/core@​1.54.1
Changelog

Sourced from posthog-node's changelog.

5.53.0

Minor Changes

  • #5050 31dd1ad Thanks @​posthog! - Read a feature flag's evaluation runtime with getFeatureFlagEvaluationRuntime(key) and getFeatureFlagKeysByEvaluationRuntime(runtime) (2026-09-23)

5.52.6

Patch Changes

  • #5078 f4704ac Thanks @​rubychilds! - Honor filters.holdout during local feature flag evaluation. A user in an experiment holdout now receives the holdout-<id> variant instead of being bucketed into a regular variant, matching how the server evaluates the same flag. The holdout is resolved before the release conditions, so a held-out user never reaches the flag's targeting — including when those conditions would have excluded them, so isFeatureEnabled can return true where it previously returned false. Experiments with an active holdout will see variant assignment change for the held-out share of traffic on upgrade, bringing locally evaluated assignments in line with server-evaluated ones. (2026-09-23)
  • Updated dependencies [f4704ac]:
    • @​posthog/core@​1.55.2

5.52.5

Patch Changes

  • #5018 9cd8ebd Thanks @​turnipdabeets! - Stop dropping long spans that end: maxSpanAgeMs now evicts spans only once maxLiveSpans is reached, so a span that runs past the age limit and then ends is exported, and its children are no longer orphaned. (2026-09-21)

  • #4800 aad7464 Thanks @​marandaneto! - Respect the definitions response's property_matching_version during local feature flag evaluation. Version 2 uses explicit boolean/string equality and per-member array matching, while missing or other versions retain service legacy matching (including empty-array truthiness). Preserve the version in Node definition caches and Convex persisted definitions, and propagate it through person, group, cohort and dependency evaluation without mixing snapshots during reloads. Existing numeric ambiguity fallback and SemVer parsing policies are unchanged. (2026-09-21)

  • Updated dependencies [9cd8ebd, aad7464]:

    • @​posthog/core@​1.55.1

5.52.4

Patch Changes

  • #4885 39a8980 Thanks @​decknamec! - Server-side feature flags now resolve in posthog-node and posthog-edge even when a proxy rewrites the request's User-Agent. Flags restricted to the client runtime now resolve to undefined in these SDKs, where a rewritten User-Agent previously let them through. (2026-09-15)
  • Updated dependencies [39a8980]:
    • @​posthog/core@​1.54.2

5.52.3

Patch Changes

  • #4941 07c1045 Thanks @​marandaneto! - Capture causes and AggregateError members with relationship metadata and individual stacks, limiting output to 50 entries and 1,000 member inspections. (2026-09-15)
  • Updated dependencies [07c1045]:
    • @​posthog/core@​1.54.1

5.52.2

Patch Changes

... (truncated)

Commits
  • 7b3121f chore: update versions and lockfile [version bump]
  • 31dd1ad feat(node): expose a flag's evaluation runtime through the SDK (#5050)
  • 0c5557a chore: update versions and lockfile [version bump]
  • f4704ac fix: honor filters.holdout in local flag evaluation (#5078)
  • 3e72e7b chore: update versions and lockfile [version bump]
  • aad7464 fix(flags): honor versioned local property matching (#4800)
  • dea3a53 chore: update versions and lockfile [version bump]
  • 5cfec8b feat(react-native): support partial survey responses and persistent resume (#...
  • e65d81f build: adopt stable native TypeScript with targeted legacy fallbacks (#4984)
  • d14b608 chore: add semantic type checks for every SDK (#4985)
  • Additional commits viewable in compare view

Updates web-tree-sitter from 0.26.13 to 0.27.0

Release notes

Sourced from web-tree-sitter's releases.

v0.27.0

What's Changed

... (truncated)

Commits
  • 8933cb7 docs(web): add WASM version compatibility section
  • 8263917 docs: specify Emscripten version constraints for web binding builds
  • 129d8cd build(deps): bump eslint
  • 0be5f89 fix(web): map Node-only specifiers to false via browser field
  • 95eaaa2 build(deps): bump the npm group across 1 directory with 3 updates
  • dff1fd8 build(deps): bump esbuild and vite in /lib/binding_web
  • 7be497a fix(web)!: report null when lookahead iterator is not positioned
  • 6ea9a7c build(deps): bump the npm group across 1 directory with 4 updates
  • fecce45 build(deps): bump @​types/node
  • 4deef2d build(deps): bump eslint
  • Additional commits viewable in compare view

Updates @biomejs/biome from 2.5.10 to 2.5.14

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.5.14

2.5.14

Patch Changes

  • #9022 0d49e24 Thanks @​dyc3! - Added the nursery rule noReturnInFinally. This rule disallows return statements in Promise.prototype.finally() callbacks, including inside nested blocks and conditional branches. Returns in nested functions are ignored by the rule.

    // Invalid: return in finally callback
    Promise.resolve(1).finally(() => { return 2 })
    // Valid: no return in finally callback
    Promise.resolve(1).finally(() => { console.log(2) })

    Returning a value from a Promise.prototype.finally() callback does not replace the original promise's fulfillment value, which can be confusing. Returned promises and thenables are awaited, and their rejection rejects the resulting promise.

  • #11754 71eaa0d Thanks @​griff-rees! - Added the nursery rule noSvelteAtDebugTags, which disallows Svelte's {@debug} tag.

    <!-- Invalid: leftover debugging tag -->
    {@debug user}

    The {@debug} tag is a debugging aid and should be removed once you no longer need it, as it should not remain in production code. The rule provides a safe fix that removes the tag.

  • #11725 5eb5f09 Thanks @​m1handr! - Added the nursery rule useValidTestTitle, which enforces valid titles for unit test cases and suites.

  • #11735 9bd70c7 Thanks @​ematipico! - Fixed #8471: source.fixAll.biome ignored formatter.formatWithErrors. It now applies safe fixes without formatting files that have parse errors when the option is disabled.

  • #11715 f05a3c3 Thanks @​ematipico! - Fixed #7771: Grit plugins that use sequential no longer panic when Biome processes files.

  • #11766 c2542c6 Thanks @​dyc3! - Fixed validation of readonly and accessor modifiers: combining them in either order now reports that they cannot be used together.

  • #11461 22e9966 Thanks @​FoundDream! - Fixed #11423: Multiline template interpolations now preserve the indentation of their closing brace when the source indentation is not a multiple of tabWidth.

     const value = `
          ${
            condition
              ? "yes"
              : "no"
    -}
    +     }
     `;
  • #11766 c2542c6 Thanks @​dyc3! - Fixed #11763: TypeScript class members using override accessor, such as override accessor value = 1, now parse correctly. The reversed order, accessor override, now reports that override must precede accessor.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.5.14

Patch Changes

  • #9022 0d49e24 Thanks @​dyc3! - Added the nursery rule noReturnInFinally. This rule disallows return statements in Promise.prototype.finally() callbacks, including inside nested blocks and conditional branches. Returns in nested functions are ignored by the rule.

    // Invalid: return in finally callback
    Promise.resolve(1).finally(() => { return 2 })
    // Valid: no return in finally callback
    Promise.resolve(1).finally(() => { console.log(2) })

    Returning a value from a Promise.prototype.finally() callback does not replace the original promise's fulfillment value, which can be confusing. Returned promises and thenables are awaited, and their rejection rejects the resulting promise.

  • #11754 71eaa0d Thanks @​griff-rees! - Added the nursery rule noSvelteAtDebugTags, which disallows Svelte's {@debug} tag.

    <!-- Invalid: leftover debugging tag -->
    {@debug user}

    The {@debug} tag is a debugging aid and should be removed once you no longer need it, as it should not remain in production code. The rule provides a safe fix that removes the tag.

  • #11725 5eb5f09 Thanks @​m1handr! - Added the nursery rule useValidTestTitle, which enforces valid titles for unit test cases and suites.

  • #11735 9bd70c7 Thanks @​ematipico! - Fixed #8471: source.fixAll.biome ignored formatter.formatWithErrors. It now applies safe fixes without formatting files that have parse errors when the option is disabled.

  • #11715 f05a3c3 Thanks @​ematipico! - Fixed #7771: Grit plugins that use sequential no longer panic when Biome processes files.

  • #11766 c2542c6 Thanks @​dyc3! - Fixed validation of readonly and accessor modifiers: combining them in either order now reports that they cannot be used together.

  • #11461 22e9966 Thanks @​FoundDream! - Fixed #11423: Multiline template interpolations now preserve the indentation of their closing brace when the source indentation is not a multiple of tabWidth.

     const value = `
          ${
            condition
              ? "yes"
              : "no"
    -}
    +     }
     `;
  • #11766 c2542c6 Thanks @​dyc3! - Fixed #11763: TypeScript class members using override accessor, such as override accessor value = 1, now parse correctly. The reversed order, accessor override, now reports that override must precede accessor.

  • #11790 17d0ff0 Thanks @​ematipico! - Fixed #10248: noUselessFragments now allows fragments with props in Astro files, such as <Fragment slot="name">{text}</Fragment> inside template expressions.

... (truncated)

Commits

Updates @types/bun from 1.4.0 to 1.4.2

Commits

Updates @vscode/vsce from 3.9.2 to 4.0.0

Release notes

Sourced from @​vscode/vsce's releases.

v4.0.0

Changes:

  • #1329: Offer prompted migration of legacy PAT credentials
  • #1325: Remove leven dependency
  • #1324: Replace form-data with Node streams
  • #1326: Fix MSAL declaration build failure
  • #1323: Relock deps and mirror to package.json
  • #1314: Replace chalk with Node styling
  • #1312: Remove parse-semver dependency
  • #1313: Reduce secretlint dependency tree
  • #1315: chore(deps): bump the github-actions group with 2 updates
  • #1306: Pin GitHub Actions to full-length commit SHAs
  • #1309: Replace glob with tinyglobby
  • #1308: Raise Node.js baseline to 22
  • #1305: Update and replace many dependencies
  • #1298: chore(deps): bump js-yaml from 4.2.0 to 4.3.1
  • #1297: Hide OIDC option from publish help
  • #1296: Remove redundant secretlint dependency
  • #1295: chore(deps): bump fast-uri from 3.1.4 to 3.1.5
  • #1294: chore(deps): bump brace-expansion
  • #1293: chore(deps): bump fast-uri from 3.1.2 to 3.1.4
  • #1292: chore(deps): bump linkify-it from 5.0.1 to 5.0.2
  • #1291: auth: support OIDC trusted publishing
  • #1289: chore(deps): bump js-yaml and @​textlint/linter-formatter
  • #1288: chore(deps): bump form-data from 4.0.4 to 4.0.6
  • #1287: chore(deps): bump markdown-it from 14.1.1 to 14.2.0
  • #1284: chore(deps): bump tmp from 0.2.6 to 0.2.7

This list of changes was auto generated.

v3.9.3-12

Changes:

  • #1329: Offer prompted migration of legacy PAT credentials
  • #1325: Remove leven dependency
  • #1324: Replace form-data with Node streams
  • #1326: Fix MSAL declaration build failure
  • #1323: Relock deps and mirror to package.json
  • #1314: Replace chalk with Node styling
  • #1312: Remove parse-semver dependency

This list of changes was auto generated.

... (truncated)

Commits
  • 9f25124 Merge pull request #1329 from microsoft/benibenj/migrate-legacy-pat-storage
  • 7d84e92 Offer prompted migration of legacy PAT credentials
  • 75cae44 Merge pull request #1325 from jakebailey/remove-leven
  • ae9f2b7 Merge pull request #1324 from jakebailey/remove-form-data
  • fa08d59 Capture both output streams in the CLI tests
  • 3fb79d8 Fix multipart stream lifecycle issues
  • bee68cf Extract command suggestion helper and test it
  • b40452e Merge pull request #1326 from microsoft/benibenj/agents/validate-package-lock...
  • d2cd4d4 Keep PR CI workflow unchanged
  • fa0fdf7 Fix MSAL declaration build failure
  • Additional commits viewable in compare view

Updates lint-staged from 17.3.0 to 17.5.1

Release notes

Sourced from lint-staged's releases.

v17.5.1

Patch Changes

  • #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

    A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

v17.5.0

Minor Changes

  • #1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.

Patch Changes

  • #1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.

  • #1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.

  • #1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

v17.4.1

17.4.1

Patch Changes

  • #1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.

17.4.0

Minor Changes

  • #1836 90ec282 - Added a new defineConfig helper for type-checking the lint-staged configuration:

    // lint-staged.config.ts
    import { defineConfig } from 'lint-staged/config'
    export default defineConfig({
    '*.js': ['prettier --check', 'eslint'],
    })

  • #1832 510a27c - Added a new flag --all to make lint-staged include all files tracked by Git, instead of only staged.

    By default lint-staged only runs tasks on files that include staged changes (hence the name). Use this flag to include all files tracked in Git version control (standard exclusions apply). Using this flag implies the --no-stash flag, disabling the automatic backup, and the --allow-empty flag so that lint-staged doesn't fail when there are no changes after running. This makes it easier to run npx lint-staged --all on a clean state, for example in CI.

Patch Changes

  • #1838 69bec99 - The behavior of the automatic backup stash has been improved when running lint-staged in multiple worktrees in parallel. You should still avoid running multiple instances of lint-staged in parallel in the same tree, because some of the Git operations are locking and might lead to data loss.

... (truncated)

Changelog

Sourced from lint-staged's changelog.

17.5.1

Patch Changes

  • #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

    A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

17.5.0

Minor Changes

  • #1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.

Patch Changes

  • #1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.

  • #1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.

  • #1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

17.4.1

Patch Changes

  • #1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.

17.4.0

Minor Changes

  • #1836 90ec282 - Added a new defineConfig helper for type-checking the lint-staged configuration:

    // lint-staged.config.ts
    import { defineConfig } from 'lint-staged/config'
    export default defineConfig({
    '*.js': ['prettier --check', 'eslint'],
    })

  • #1832 510a27c - Added a new flag --all to make lint-staged include all files tracked by Git, instead of only staged.

    By default lint-staged only runs tasks on files that include staged changes (hence the name). Use this flag to include all files tracked in Git version control (standard exclusions apply). Using this flag implies the --no-stash flag, disabling the automatic backup, and the --allow-empty flag so that lint-staged doesn't fail when there are no changes after running. This makes it easier to run npx lint-staged --all on a clean state, for example in CI.

Patch Changes

... (truncated)

Commits
  • f8b1ab1 Merge pull request #1853 from lint-staged/changeset-release/main
  • 3b54961 chore(changeset): release
  • 09317ff Merge pull request #1852 from lint-staged/fix-ambient-declaration
  • bfcca94 fix: change defineConfig signature from const to a function

Bumps the bun-packages group with 8 updates:

| Package | From | To |
| --- | --- | --- |
| [p-map](https://github.com/sindresorhus/p-map) | `7.0.6` | `7.0.8` |
| [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) | `5.51.2` | `5.53.0` |
| [web-tree-sitter](https://github.com/tree-sitter/tree-sitter/tree/HEAD/lib/binding_web) | `0.26.13` | `0.27.0` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.5.10` | `2.5.14` |
| [@types/bun](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/bun) | `1.4.0` | `1.4.2` |
| [@vscode/vsce](https://github.com/Microsoft/vsce) | `3.9.2` | `4.0.0` |
| [lint-staged](https://github.com/lint-staged/lint-staged) | `17.3.0` | `17.5.1` |
| [ovsx](https://github.com/eclipse-openvsx/openvsx/tree/HEAD/cli) | `1.1.1` | `1.2.0` |


Updates `p-map` from 7.0.6 to 7.0.8
- [Release notes](https://github.com/sindresorhus/p-map/releases)
- [Commits](sindresorhus/p-map@v7.0.6...v7.0.8)

Updates `posthog-node` from 5.51.2 to 5.53.0
- [Release notes](https://github.com/PostHog/posthog-js/releases)
- [Changelog](https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md)
- [Commits](https://github.com/PostHog/posthog-js/commits/posthog-node@5.53.0/packages/node)

Updates `web-tree-sitter` from 0.26.13 to 0.27.0
- [Release notes](https://github.com/tree-sitter/tree-sitter/releases)
- [Commits](https://github.com/tree-sitter/tree-sitter/commits/v0.27.0/lib/binding_web)

Updates `@biomejs/biome` from 2.5.10 to 2.5.14
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.5.14/packages/@biomejs/biome)

Updates `@types/bun` from 1.4.0 to 1.4.2
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/bun)

Updates `@vscode/vsce` from 3.9.2 to 4.0.0
- [Release notes](https://github.com/Microsoft/vsce/releases)
- [Commits](microsoft/vscode-vsce@v3.9.2...v4.0.0)

Updates `lint-staged` from 17.3.0 to 17.5.1
- [Release notes](https://github.com/lint-staged/lint-staged/releases)
- [Changelog](https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md)
- [Commits](lint-staged/lint-staged@v17.3.0...v17.5.1)

Updates `ovsx` from 1.1.1 to 1.2.0
- [Release notes](https://github.com/eclipse-openvsx/openvsx/releases)
- [Changelog](https://github.com/eclipse-openvsx/openvsx/blob/main/cli/CHANGELOG.md)
- [Commits](https://github.com/eclipse-openvsx/openvsx/commits/v1.2.0/cli)

---
updated-dependencies:
- dependency-name: p-map
  dependency-version: 7.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun-packages
- dependency-name: posthog-node
  dependency-version: 5.53.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: bun-packages
- dependency-name: web-tree-sitter
  dependency-version: 0.27.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: bun-packages
- dependency-name: "@biomejs/biome"
  dependency-version: 2.5.14
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: bun-packages
- dependency-name: "@types/bun"
  dependency-version: 1.4.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: bun-packages
- dependency-name: "@vscode/vsce"
  dependency-version: 4.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: bun-packages
- dependency-name: lint-staged
  dependency-version: 17.5.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: bun-packages
- dependency-name: ovsx
  dependency-version: 1.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: bun-packages
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 1, 2026
@savannahostrowski savannahostrowski added the internal Internal changes label Oct 1, 2026
@savannahostrowski
savannahostrowski merged commit 6c145d4 into main Oct 1, 2026
8 of 9 checks passed
@savannahostrowski
savannahostrowski deleted the dependabot/bun/bun-packages-5eda58c467 branch October 1, 2026 16:41
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 internal Internal changes javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant