Skip to content

chore(deps): Bump the dependencies group across 1 directory with 5 updates#52

Merged
GoodbyePlanet merged 2 commits into
mainfrom
dependabot/uv/dependencies-6f6c80d40f
Jun 19, 2026
Merged

chore(deps): Bump the dependencies group across 1 directory with 5 updates#52
GoodbyePlanet merged 2 commits into
mainfrom
dependabot/uv/dependencies-6f6c80d40f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 18, 2026

Copy link
Copy Markdown
Contributor

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

Package From To
mcp 1.27.1 1.28.0
tree-sitter-swift 0.7.2 0.7.3
tree-sitter-language-pack 1.6.2 1.9.0
pytest 9.0.3 9.1.0
pytest-asyncio 1.3.0 1.4.0

Updates mcp from 1.27.1 to 1.28.0

Release notes

Sourced from mcp's releases.

v1.28.0

Deprecations

Two API surfaces now emit DeprecationWarning ahead of their removal in v2. Nothing is removed in 1.x, and the warnings fire only when the deprecated API is called - importing the modules stays silent.

  • WebSocket transport - mcp.client.websocket.websocket_client and mcp.server.websocket.websocket_servermodelcontextprotocol/typescript-sdk#1783
  • Experimental tasks API - ClientSession.experimental, Server.experimental, ServerSession.experimental, and the experimental_task_handlers= kwarg on ClientSession. Tasks (SEP-1686) were removed from the MCP specification and are expected to return as a separate MCP extension.

If your test suite runs with filterwarnings = ["error"] and exercises these paths, add a scoped ignore such as ignore:The experimental tasks API is deprecated:DeprecationWarning or ignore:The WebSocket .* transport is deprecated:DeprecationWarning.

See #2828 for full details.

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/python-sdk@v1.27.2...v1.28.0

v1.27.2

What's Changed

Full Changelog: modelcontextprotocol/python-sdk@v1.27.1...v1.27.2

Commits
  • 32d3290 [v1.x] Pass a list to parametrize in test_docs_examples (pytest 9.1.0 compat)...
  • 0dca751 [v1.x] Deflake the child process cleanup tests (#2839)
  • 52258a9 [v1.x] Add a v2 status banner to the README (#2835)
  • b8f4917 [v1.x] Deprecate the WebSocket transport and the experimental tasks entry poi...
  • 2309e5e fix: omit null optional fields from task result payloads (#2809)
  • 494eb11 [v1.x] Support Python 3.14 (#2769)
  • 6213787 [v1.x] Scope experimental tasks to the session that created them (#2720)
  • ce267b6 [v1.x] Bind transport sessions to the authenticated principal (#2719)
  • 1abcca2 [v1.x] Add subject and claims to AccessToken (#2690)
  • 9773a3f [v1.x] ci: deploy docs to py.sdk.modelcontextprotocol.io via Pages artifact (...
  • See full diff in compare view

Updates tree-sitter-swift from 0.7.2 to 0.7.3

Release notes

Sourced from tree-sitter-swift's releases.

0.7.3

NOTE: Download tree-sitter-swift.tar.gz for the complete source code.

What's Changed

Full Changelog: alex-pinkus/tree-sitter-swift@0.7.2...0.7.3

Commits
  • b8b22bf Update for 0.7.3 release
  • 55645a8 Updating top repository version
  • 24585e2 Merge pull request #583 from danfaer/feat/directives-in-type-bodies
  • 24db106 Merge main into feat/directives-in-type-bodies
  • a923ac6 Support bracket-qualified nested type access in type position
  • 03e31ae Support parenthesized nonisolated modifier: nonisolated(unsafe)/(nonsending)
  • 1de03f1 Allow #if/#elseif/#else/#endif directives inside type bodies
  • 3d38a39 Updating top repository version
  • 30f3056 Fix parsing of double-optional types (Type??) in lambda parameters
  • ed1196c Add do throws(E) do-catch syntax -- SE-0413
  • Additional commits viewable in compare view

Updates tree-sitter-language-pack from 1.6.2 to 1.9.0

Release notes

Sourced from tree-sitter-language-pack's releases.

v1.9.0

What's Changed

New Contributors

Full Changelog: xberg-io/tree-sitter-language-pack@v0.17.10...v1.9.0

v1.9.0-rc.55

What's Changed

Full Changelog: xberg-io/tree-sitter-language-pack@v1.9.0-rc.35...v1.9.0-rc.55

v1.9.0-rc.54

Release candidate for v1.9.0.

Fixed

  • java: NativeLib loader RID aligned to go_java_platform() naming (macos-arm64, linux-aarch64, windows-x86_64); fixes UnsatisfiedLinkError on macOS arm64 clients.
  • elixir: rustler NIF Cargo.toml now emits [features] default = ["config", "download", "serde"] forwarding to the core crate; fixes :nif_not_loaded on every Native.download/*, cache_dir/0, clean_cache/0, init/0, configure/1, downloaded_languages/0 call.
  • node: vitest testTimeout raised 30 s → 60 s; clears smoke_devicetree + smoke_ocamllex first-load timeouts.
  • e2e/c: download_ffi.sh honours ALEF_FFI_LOCAL_DIR env override to skip the GH release download; ci-e2e.yaml/test-c-ffi now reuses the build-ffi artifact, breaking the 404 race on new releases.

Changed

  • Bumped alef pin 0.25.20 → 0.25.24.

See CHANGELOG.md for details.

v1.9.0-rc.53

What's Changed

Full Changelog: xberg-io/tree-sitter-language-pack@v1.9.0-rc.35...v1.9.0-rc.53

v1.9.0-rc.52

[1.9.0-rc.52] - 2026-06-16

Changed

... (truncated)

Changelog

Sourced from tree-sitter-language-pack's changelog.

[1.9.0] - 2026-06-18

Changed

  • Bumped alef pin 0.25.28 → 0.25.38 and regenerated all bindings. Picks up alef 0.25.29–0.25.38: enum associated (static factory) methods surfaced across backends, the swift opaque no-op shim so $_free is synthesised for handle types with no visible methods (e.g. Language), swift streaming-owner already_declared re-declaration, java marshal_optional_bytes template registration, and java @Nullable type-use placement on qualified types.
  • Upgraded all dependencies to their latest versions (cross-major). Ran task upgrade across every language workspace; lock files regenerated and committed.
  • Repo hygiene. Ignore the machine-local packages/kotlin-android/.gradle/ cache and the .basemind/ index (untracking the accidentally-committed Gradle cache files), and exclude the deterministic .ai-rulez/.generated-manifest.json from the oxfmt pre-commit hook so it no longer fights the ai-rulez-generate hook.

Fixed

  • Java: dropped throwing UnsupportedOperationException stubs for Self-returning DTO/enum methods. There is no JNI/FFM symbol for DTO methods yet, so the throwing stubs compiled but misled callers and broke any path that reached them. The Java backend now skips these methods until marshaling lands.
  • Java: restored the true default for boxed @Nullable Boolean #[serde(default)] record fields. A non-optional #[serde(default)] bool = true field is boxed to @Nullable Boolean, so JSON that omitted it deserialised to null and the accessor returned null instead of true.

[1.9.0-rc.55] - 2026-06-17

Changed

  • Bumped alef pin 0.25.24 → 0.25.28. Regenerated all bindings via task alef:generate. Picks up alef 0.25.25–0.25.28: scaffold excluded_default_features for dart/swift wrappers, publish/vendor retry on crates.io registry-index propagation lag, e2e/codegen wasm [crates.e2e.env] block, e2e/codegen php PIE invocation syntax for v1.4.5, backends/swift RustBridgeC import + Vec skip on already-declared types, docs heading demotion, e2e/codegen typescript SsrfPolicy.denyPrivate=false for WASM e2e, backends/ffi shared extractor → FFI same-name fn dedup, and backends/dart FRB primitive bridge return-value type cast restoration (.map(|v| v as i64) regression that blocked rc.55 regen).

Fixed

  • Elixir Hex install OTP 27.2 TLS key_usage_mismatch against builds.hex.pm. Switched test-elixir jobs in ci.yaml and ci-e2e.yaml to kreuzberg-dev/actions/setup-elixir@v1 wrapper which routes through cdn.hex.pm to bypass OTP 27.2 TLS cert-chain rejection against builds.hex.pm.
  • ci.yaml test- jobs 404 race on parsers.json.* Mirrored ci-e2e.yaml's build-e2e-bundles job into ci.yaml and added TREE_SITTER_LANGUAGE_PACK_MANIFEST_URL manifest wiring to all test-* jobs (test-python, test-node, test-wasm, test-go, test-java, test-csharp, test-ruby, test-php, test-elixir, test-c-ffi). Pre-publish, the workspace version has no GitHub Release yet, so the runtime's network fetch of parsers.json would 404; bundling parsers locally and exporting the manifest URL avoids the race.

[1.9.0-rc.54] - 2026-06-17

Changed

  • Bumped alef pin 0.25.20 → 0.25.24. Regenerated all bindings via task alef:generate. Picks up alef 0.25.21–0.25.24: dart e2e setEnv robustness, swift already_declared opaque-handle class triples, java PMD/palantir-java-format compliance, C FFI e2e download_ffi.sh derives FFI_PKG_NAME from lib_name (was hardcoded), kotlin-android per-file ktfmt invocation, plus the rc.53 → rc.54 structural fixes below.

Fixed

  • Java loader RID alignment (rc.53 regression). NativeLib.resolveNativesRid() previously emitted osx-aarch64/linux-aarch64 (a JNA/LWJGL-style convention) while the published JAR's natives/<rid>/… directory is named via go_java_platform() (macos-arm64, linux-aarch64, windows-x86_64). Result: every macOS-arm64 client failed with UnsatisfiedLinkError because natives/osx-aarch64/libts_pack_core_ffi.dylib does not exist (it's at natives/macos-arm64/). Loader template now matches go_java_platform() naming.
  • Elixir download NIFs unregistered in precompiled binary (rc.53 regression). The rustler NIF crate Cargo.toml had no [features] table — only a [lints.rust] check-cfg reference to download. Default precompiled CI builds therefore stripped the download/cache/init/configure NIFs from the cdylib, producing :nif_not_loaded errors on every TreeSitterLanguagePack.Native.download/*, cache_dir/0, clean_cache/0, init/0, configure/1, downloaded_languages/0 call (10/450 errors at rc.53). Template now emits canonical [features] default = ["config", "download", "serde"] block forwarding to the core crate, mirroring the magnus fix from alef 0.25.19.
  • Node vitest first-load timeouts. smoke_devicetree and smoke_ocamllex exceeded the default 30 s test timeout on first load. Raised testTimeout to 60 s, hookTimeout to 120 s.
  • C FFI E2E 404 race in ci-e2e.yaml. e2e/c/download_ffi.sh pinned the FFI tarball URL to the current workspace version; on main pushes before the matching tag was created, the curl 404'd because the GitHub Release for that version didn't exist yet. Script now honours ALEF_FFI_LOCAL_DIR env override to skip the network fetch and consume pre-staged headers/libs. ci-e2e.yaml/test-c-ffi is now needs: build-ffi and stages the locally-built artifact via the override.

[1.9.0-rc.53] - 2026-06-16

Changed

  • Bumped alef pin 0.25.18 → 0.25.20. Regenerated all bindings via task alef:generate. Picks up:
    • 0.25.19 — magnus binding Cargo.toml [features] block (fixes rc.52 Ruby gem build under -D warnings), elixir NIF Cargo.toml [lints.rust] ordering (fixes CI Check version sync), ruby Rakefile yard-coverage hook, FFI opaque-pointer call-site .clone() for service-API codegen, binding_excluded field fallthrough that preserves bespoke core Default::default() semantics, csharp e2e csproj arm64 RID branching.
    • 0.25.20 — dart loader absolutize defensive improvement, zig opaque method error decoding (_first_error_error_with_message), language_pages.rs modularization under 1000-LOC cap.

Fixed

  • Ruby gem publish (rc.52 regression). All four Build Ruby gem matrix jobs failed at rc.52 — the magnus binding's Cargo.toml lacked the [features] table forwarding download to the core crate, so 18× #[cfg(feature = "download")] arms triggered error: unexpected cfg condition value: download under -D warnings. The skipped Publish Ruby gems step meant rc.52 never reached rubygems.org (test-apps:ruby failed with Could not find gem 'tree_sitter_language_pack ~> 1.9.0.pre.rc.52'). Picked up via alef 0.25.19.
  • CI Check version sync red on main. The elixir NIF Cargo.toml emitted [lints.rust] before [dependencies]; consumers' prek run --all-files runs cargo-sort which reorders the block to the file end, producing a perpetual diff. The CI version-sync step does NOT run cargo-sort, so it reported "Versions are out of sync" on every release tag. Picked up via alef 0.25.19.
  • Dart publish pipeline native staging (rc.52 regression). The assemble-dart-package job in .github/workflows/publish.yaml used download-artifact@v8 with merge-multiple: true, flattening every dart-native-<rid> artifact's contents directly under dart-natives/. The subsequent RID inference (basename "$(dirname "$f")") then resolved to the literal string dart-natives for every file, causing all four native libraries to be skipped with Warning: unrecognized rid 'dart-natives'. The published rc.52 pub.dev tarball contained no lib/src/native/<rid>/ directory; the FRB loader fell through to the default relative-path dlopen which macOS hardened-runtime rejected with "relative path not allowed in hardened program". Fix: drop merge-multiple: true so each artifact extracts to its own dart-natives/dart-native-<rid>/ directory, and derive the RID by stripping the dart-native- prefix from the artifact directory name.

... (truncated)

Commits
  • ec7a240 chore(swift): update Package.swift with checksum for v1.9.0
  • 394ff2e chore(release): v1.9.0
  • 32950b6 chore: ignore kotlin-android Gradle cache and basemind index
  • 1f0208b chore: add basemind plugin config
  • 2e92399 chore(release): v1.9.0-rc.55
  • 0c5c546 fix(ci): route test-elixir Hex install through wrapper action to bypass build...
  • 113f291 fix(ci): mirror ci-e2e.yaml manifest staging into ci.yaml to avoid 404 race o...
  • 532a2a1 chore(release): v1.9.0-rc.54
  • 89be694 docs(api): regenerate api-*.md with LanguageRegistry example
  • 6fd24d0 chore(release): v1.9.0-rc.53
  • Additional commits viewable in compare view

Updates pytest from 9.0.3 to 9.1.0

Release notes

Sourced from pytest's releases.

9.1.0

pytest 9.1.0 (2026-06-13)

Removals and backward incompatible breaking changes

  • #14533: When using --doctest-modules, autouse fixtures with module, package or session scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

    If this is undesirable, move the fixture definition to a conftest.py file if possible.

    Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as pytest.Module and once as a DoctestModule (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the DoctestModule collects a fixture, it is now visible to it only, and not to the Module. This means that both need to register the fixtures independently.

Deprecations (removal in next major release)

  • #10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without @classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use @classmethod decorator instead -- by yastcher.

    See 10819 and 14011.

  • #12882: Calling request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue> during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

    See dynamic-fixture-request-during-teardown for details.

  • #13409: Using non-~collections.abc.Collection iterables (such as generators, iterators, or custom iterable objects) for the argvalues parameter in @pytest.mark.parametrize <pytest.mark.parametrize ref> and metafunc.parametrize <pytest.Metafunc.parametrize> is now deprecated.

    These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running pytest.main() multiple times, using class-level parametrize decorators, or collecting tests multiple times.

    See parametrize-iterators for details and suggestions.

  • #13946: The private config.inicfg attribute is now deprecated. Use config.getini() <pytest.Config.getini> to access configuration values instead.

    See config-inicfg for more details.

  • #14004: Passing baseid to ~pytest.FixtureDef or nodeid strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

    Use the node parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used nodeid=None, pass node=session instead.

    This will be removed in pytest 10.

  • #14335: The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See hook-markers for more details.

  • #14434: The --pastebin option is now deprecated.

... (truncated)

Commits
  • b2522cf Prepare release version 9.1.0
  • 368d2fc [refactor] Tighten SetComparisonFunction to Iterator[str] (#14587)
  • ff77cd8 [refactor] Make base assertion comparisons return an iterator instead of a li...
  • 0d8491a build(deps): Bump actions/stale from 10.2.0 to 10.3.0
  • 4a809d9 Merge pull request #14568 from pytest-dev/register-fixture
  • 5dfa385 Fix recursion traceback test to cover all styles (#14582)
  • f52ff0c Add pytest.register_fixture
  • a8ac094 Merge pull request #14567 from pytest-dev/more-visibility-deprecate
  • e5620cd [pre-commit.ci] pre-commit autoupdate (#14577)
  • 2ce9c6d Merge pull request #14540 from minbang930/fix-14533-doctest-module-fixtures
  • Additional commits viewable in compare view

Updates pytest-asyncio from 1.3.0 to 1.4.0

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio v1.4.0

1.4.0 - 2026-05-26

Deprecated

  • Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#1419)

Added

  • Added the pytest_asyncio_loop_factories hook to parametrize asyncio tests with custom event loop factories.

    The hook returns a mapping of factory names to loop factories, and pytest.mark.asyncio(loop_factories=[...]) selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.

    Synchronous @pytest_asyncio.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#1164)

Changed

  • Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#1298)
  • Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising a DeprecationWarning. (#1394)
  • Updated minimum supported pytest version to v8.4.0. (#1397)

Fixed

  • Fixed a ResourceWarning: unclosed event loop warning that could occur when a synchronous test called asyncio.run() or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (#724)

Notes for Downstream Packagers

  • Added dependency on sphinx-tabs >= 3.5 to organize documentation examples into tabs. (#1395)

pytest-asyncio v1.4.0a2

1.4.0a2 - 2026-05-02

Deprecated

  • Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#1419)

Added

  • Added the pytest_asyncio_loop_factories hook to parametrize asyncio tests with custom event loop factories.

    The hook returns a mapping of factory names to loop factories, and pytest.mark.asyncio(loop_factories=[...]) selects a subset of configured factories per test. When a single factory is configured, test names are unchanged on pytest 8.4+.

    Synchronous @pytest_asyncio.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#1164)

Changed

  • Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#1298)
  • Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising a DeprecationWarning. (#1394)

... (truncated)

Commits
  • 6e14cd2 chore: Prepare release of v1.4.0.
  • 4b900fb Build(deps): Bump codecov/codecov-action from 6.0.0 to 6.0.1
  • ab9f632 Build(deps): Bump zipp from 3.23.1 to 4.1.0
  • a56fc77 Build(deps): Bump hypothesis from 6.152.6 to 6.152.8
  • e8bae9b Build(deps): Bump requests from 2.34.0 to 2.34.2
  • fc43340 Build(deps): Bump idna from 3.14 to 3.15
  • 762eaf5 Build(deps): Bump jaraco-functools from 4.4.0 to 4.5.0
  • b62e222 Build(deps): Bump click from 8.3.3 to 8.4.0
  • 9190447 Build(deps): Bump pydantic from 2.13.3 to 2.13.4
  • 82a393c ci: Remove unnecessary debug output.
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…dates

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

| Package | From | To |
| --- | --- | --- |
| [mcp](https://github.com/modelcontextprotocol/python-sdk) | `1.27.1` | `1.28.0` |
| [tree-sitter-swift](https://github.com/alex-pinkus/tree-sitter-swift) | `0.7.2` | `0.7.3` |
| [tree-sitter-language-pack](https://github.com/kreuzberg-dev/tree-sitter-language-pack) | `1.6.2` | `1.9.0` |
| [pytest](https://github.com/pytest-dev/pytest) | `9.0.3` | `9.1.0` |
| [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | `1.3.0` | `1.4.0` |



Updates `mcp` from 1.27.1 to 1.28.0
- [Release notes](https://github.com/modelcontextprotocol/python-sdk/releases)
- [Changelog](https://github.com/modelcontextprotocol/python-sdk/blob/main/RELEASE.md)
- [Commits](modelcontextprotocol/python-sdk@v1.27.1...v1.28.0)

Updates `tree-sitter-swift` from 0.7.2 to 0.7.3
- [Release notes](https://github.com/alex-pinkus/tree-sitter-swift/releases)
- [Commits](alex-pinkus/tree-sitter-swift@0.7.2...0.7.3)

Updates `tree-sitter-language-pack` from 1.6.2 to 1.9.0
- [Release notes](https://github.com/kreuzberg-dev/tree-sitter-language-pack/releases)
- [Changelog](https://github.com/kreuzberg-dev/tree-sitter-language-pack/blob/main/CHANGELOG.md)
- [Commits](xberg-io/tree-sitter-language-pack@v1.6.2...v1.9.0)

Updates `pytest` from 9.0.3 to 9.1.0
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@9.0.3...9.1.0)

Updates `pytest-asyncio` from 1.3.0 to 1.4.0
- [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases)
- [Commits](pytest-dev/pytest-asyncio@v1.3.0...v1.4.0)

---
updated-dependencies:
- dependency-name: mcp
  dependency-version: 1.28.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: tree-sitter-swift
  dependency-version: 0.7.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: tree-sitter-language-pack
  dependency-version: 1.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: pytest
  dependency-version: 9.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: pytest-asyncio
  dependency-version: 1.4.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Jun 18, 2026
1.9.0 drops its explicit tree-sitter dependency and bundles a newer
core whose parse() rejects bytes, breaking the Dart and R parsers
(TypeError: 'bytes' object is not an instance of 'str'). Keep it at
>=1.5.0,<1.6.3 for now; the upgrade will be handled in a separate PR.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@GoodbyePlanet GoodbyePlanet merged commit 30b57e5 into main Jun 19, 2026
2 checks passed
@GoodbyePlanet GoodbyePlanet deleted the dependabot/uv/dependencies-6f6c80d40f branch June 19, 2026 07:09
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 python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant