Skip to content

chore(deps): update all dependencies (major) - #57

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-all-deps
Open

chore(deps): update all dependencies (major)#57
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-all-deps

Conversation

@renovate

@renovate renovate Bot commented Nov 8, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
Chickensoft.GameTools 2.1.14 → 3.1.37 age confidence nuget major
DotNext.Threading (source) 5.25.2 → 6.6.1 age confidence nuget major
SpacetimeDB.ClientSDK (source) 1.5.0 → 2.8.1 age confidence nuget major
SpacetimeDB.Runtime (source) 1.5.0 → 2.8.1 age confidence nuget major
actions/checkout v5 → v7 age confidence action major
actions/deploy-pages v4 → v5 age confidence action major
actions/setup-dotnet v5 → v6 age confidence action major
actions/upload-pages-artifact v4 → v5 age confidence action major
dotnet-sdk 9.0.306 → 10.0.400 age confidence dotnet-sdk major
peter-evans/create-pull-request v7 → v8 age confidence action major
streetsidesoftware/cspell-action v7 → v9 age confidence action major

Release Notes

dotnet/dotNext (DotNext.Threading)

v6.6.1

Compare Source

v6.6.0

Compare Source

v6.5.0

Compare Source

v6.4.1

Compare Source

v6.4.0

Compare Source

v6.3.0

Compare Source

v6.2.0

Compare Source

clockworklabs/SpacetimeDB (SpacetimeDB.Runtime)

v2.8.1

Features

spacetime mcp - bring your coding agent into SpacetimeDB

SpacetimeDB now ships a first-class bridge for local coding agents. The new spacetime mcp CLI subcommand launches an MCP (Model Context Protocol) server over stdio - exactly how local agents like Codex, Claude, and Cursor expect to connect - and bridges it to SpacetimeDB's HTTP-based MCP route. The /v1/mcp route itself now accepts the target database as a per-call tool argument with inherited auth, so there's no per-user database/identity configuration to set up: just point your agent at spacetime mcp and go.

This ships alongside a brand-new SpacetimeDB Codex plugin, bundling agent skills that teach your assistant SpacetimeDB concepts, the CLI, and idiomatic module/client development across Rust, C#, TypeScript, C++, Unity, and Unreal. Install it with:

codex plugin marketplace add clockworklabs/SpacetimeDB --sparse .agents --sparse codex-plugin
codex plugin add spacetimedb@spacetimedb-plugins

MCP server config (used automatically by the plugin):

{
  "mcpServers": {
    "spacetimedb": {
      "command": "spacetime",
      "args": ["mcp"]
    }
  }
}

(#​5582)

[Rust] Support default string values

Rust modules can now declare a default value for string columns using #[default(value)] with a &'static str, closing a gap versus other column-default types.

(#​5562)

Bug Fixes

Fix deadlock in subscription removal (v1 websocket)

remove_single_subscription was acquiring the subscription lock before the tx lock, violating the required lock-ordering convention and causing a deadlock. This path is exclusive to the v1 websocket protocol.

(#​5666)

Fix rows of exactly 1024 bytes getting ignored in C#

Errno.EXHAUSTED from row_iter_bsatn_advance was incorrectly treated as "no bytes written, iterator done." It is fixed to match the actual contract: EXHAUSTED means zero or more bytes were written and the iterator is now done. Rows whose BSATN encoding is exactly 1024 bytes were previously dropped.

(#​5621)

Fix readUInt8Array buffer aliasing in the TypeScript SDK

Reading an array<u8> column returned a Uint8Array view over the row iterator's reused scan buffer instead of an owned copy, so a decoded value could silently reflect a later scan's bytes. readUInt8Array now returns an owned copy.

(#​5491)

Handle WebSocket decompression failures in the TypeScript SDK

WebsocketDecompressAdapter previously left a decompress rejection (observed on WebKit/iOS gzip frames) as an unhandled promise rejection, silently dropping the frame and stalling the connection. Decompress failures are now caught, logged, and close the socket so existing reconnect handling takes over.

(#​5668)

Fix default column value bugs across languages

New cross-language smoketests for column defaults uncovered and fixed several default-value bugs.

(#​5618)

Fix replication follower resync tracking

FollowerActor::sync_logs failed to update its local last-synced offset after a reset, found via local DST testing.

Unity SDK

Support disabled Domain Reloading

Added ResetStaticFields reset methods to Log, SpacetimeDBNetworkManager, RemoteTableHandleBase, and DbConnectionBase, automatically invoked on subsystem init. This prevents stale singleton instances, cached serializers, and test state from carrying over between Play Mode sessions in Unity projects that disable Domain Reloading.

(#​5554)

Internal Cleanup

C# exported callback IDs changed from uint to int

Internal cleanup of the C# bindings: exported callback IDs are now int instead of uint, which is ABI-neutral at the Wasm i32 level and more idiomatic for C#'s int-indexed collections.

(#​5529)

What's Changed

  • Create Codex Plugin (adds spacetime mcp CLI subcommand) in #​5582
  • [Rust] Allow to supply a default string value in #​5562
  • Deadlock fix: scope down subscription lock in remove_single_subscription in #​5666
  • Fix rows of exactly 1024 bytes getting ignored in C# in #​5621
  • Fix: readUInt8Array must copy, not view the reused scan buffer in #​5491
  • TypeScript SDK: handle decompress failures in WebsocketDecompressAdapter in #​5668
  • Smoketests for default values (and fix bugs) in #​5618
  • Implement ResetStaticFields method for Unity instance cleanup in #​5554
  • Update #​2149 to post .NET 10 in #​5529

Full Changelog: v2.8.0...v2.8.1

v2.8.0

Features

TypeScript submodule support for SpacetimeDB modules

TypeScript modules can now import and mount other modules under a namespace. The runtime supports namespaced reducer/procedure dispatch and HTTP handler delegation; the client codegen exports namespace-aware table, reducer, and procedure handles and a query builder for submodule tables and views. The CLI now supports namespaced spacetime call and spacetime sql. Auto-migration is supported for submodule tables, views, and indexes. The C++ and C# bindings have been updated with autogenerated RawSubmoduleV10 types.

Compatibility note: ModuleDef now includes a submodule field. Modules that do not use submodules can still be published to older servers, but modules that use submodules require a v2.8.0+ server.

(#​5486)

Bug Fixes

Fix TypeScript composite btree range scans

TypeScript module indexes now correctly handle filter() and delete() methods when the final argument is a Range on a composite key. Previously, range bounds were sliced from the start of the key instead of after the prefix, producing incorrect results for composite range scans.

(#​5479)

Reliability & Observability

Track scheduled function delay

The server now emits a warning and records a Prometheus metric when a scheduled function starts more than 50 ms after its expected start time.

(#​5592)

Reduce noisy server logs

Routine client connection lifecycle, SQL query, JWT payload lookup, PostgreSQL socket processing, migration planning, and reducer-returned error logs are now logged at quieter levels or written only to the module log. Actionable logs remain visible.

(#​5320)

What’s Changed

  • Add TypeScript submodule support for SpacetimeDB modules in #​5486
  • Fix TS composite btree range scans in #​5479
  • Track scheduled function delay in #​5592
  • Reduce noisy server logs in #​5320

Full Changelog: v2.7.1-hotfix1...v2.8.0

v2.7.1

Bug Fixes

Safer sequence migrations

Adding a sequence to an existing integer column now correctly checks the full sequence range, including the maximum representable value. Migrations with existing conflicting values fail during the precheck rather than proceeding to a later unique-constraint violation.

(#​5561)

Preserve column defaults in V10 schemas

V10 schema serialization now retains declared column default values. This fixes the V10 database schema endpoint and extract-schema, so schema diff, compatibility, code generation, and migration tooling can observe defaults.

(#​5508)

Fix scheduled-reducer interval drift

Scheduled reducers and procedures now use the reducer's own timestamp parameter to compute the next interval, instead of Timestamp::now(). This prevents long-running scheduled reducers from drifting over repeated runs.

(#​5574)

Restore JWT/JWKS dependencies

The removal of the spacetimedb-jsonwebtoken and spacetimedb-jwks dependencies has been reverted due to Keats/jsonwebtoken#510. This restores the previous authentication behavior.

(#​5578)

TypeScript SDK reconnects on refocus and network return

The TypeScript SDK now listens for visibilitychange, focus, online, and pageshow events in the browser. When a tab returns to the foreground or the network comes back, stalled reconnect backoffs are reset and dead sockets are torn down and rebuilt automatically.

(#​5525)

Fix task leak on module init

A leaked metric-tracking task is now dropped when module initialization fails, particularly during replay errors. A new module_host_init_attempts counter is also recorded on every init attempt for per-database alerting.

(#​5601)

Reliability & Observability

Reducer errors log database identity and reducer name

When a reducer returns an error, the log line now includes the database identity and the reducer name, making it easier to correlate errors with upstream connection or proxy issues.

(#​5473)

Release & Packaging

Fix npm release artifact handling

The release workflow now handles the npm package more robustly, fixing two potential issues during release artifact upload.

(#​5593)

Networking & Infrastructure

Enable HTTP/2

SpacetimeDB now enables HTTP/2 on its ingress paths, improving connection multiplexing and reducing latency for clients and internal services.

Cache CORS preflight responses

CORS preflight responses are now cached, reducing redundant preflight round-trips for browser-based clients.

Documentation

Convex migration guide

The documentation now includes a guide for migrating Convex applications to SpacetimeDB, covering schema design, reducers, views, procedures, HTTP handlers, scheduling, authentication, and client subscriptions.

(#​5536)

What's Changed

  • Fix sequence migration prechecks in #​5561
  • Preserve column defaults in V10 schemas in #​5508
  • Fix scheduled-reducer interval drift in #​5574
  • Restore spacetimedb-jsonwebtoken and spacetimedb-jwks dependencies in #​5578
  • TypeScript SDK reconnects on refocus and network return in #​5525
  • Fix task leak on module init in #​5601
  • Fix npm release artifact handling in #​5593
  • Enable HTTP/2
  • Cache CORS preflight responses
  • Log database identity and reducer name on reducer errors in #​5473
  • Add the Convex migration guide in #​5536

Full Changelog: v2.7.0-hotfix3...v2.7.1

v2.7.0

v2.6.1

v2.6.1 is a patch release with two bug fixes and a CLI improvement.

Breaking Changes

TypeScript: Generated optional fields now use optional key syntax

⚠️ Small breaking change for some TypeScript users. Generated TypeScript types for Option<T> fields have changed from required keys with an undefined value to truly optional keys:

// Before (v2.6.0 and earlier)
{ foo: string | undefined; }

// After (v2.6.1)
{ foo?: string | undefined; }

If your TypeScript code explicitly passes undefined for optional reducer or procedure arguments, or relies on { foo: T | undefined } being a required key, you may need to update your call sites. This will require no action from almost all TypeScript users and it addresses a bug in the implementation of 2.0, so we've chosen to make this small breaking change.

(#​4940)

Bug Fixes

Fix TypeScript optional row keys

Generated optional fields now use optional key syntax. See Breaking Changes above.

(#​4940)

Fix Identity and ConnectionId regression in Procedures

A regression introduced in 2.4 caused ctx.sender and ctx.connection_id to always be empty inside procedure contexts. This has been corrected — callers' identity and connection ID are now properly propagated again.

(#​5323)

CLI Improvements

spacetime init --template now shows available templates

Running spacetime init --template without an argument now prints the list of available templates and a link to the website, rather than failing silently.

(#​5264)

What's Changed

Full Changelog: v2.6.0...v2.6.1

v2.6.0

2.6.0 adds Primary Key support for Views in Rust, TypeScript, and C#, improves event table automigrations, includes CLI binary distribution improvements, and brings various performance enhancements and bug fixes.

Features

Primary Key support for Views (Rust, TypeScript, and C#)

Procedural views now support primary keys in Rust, TypeScript, and C#

Note: C++ support for primary keys in views will be added in a future release.

  • Rust: Declare primary keys in the #[view] macro:

    #[spacetimedb::view(accessor = my_players, public, primary_key = id)]
pub fn my_players(ctx: &spacetimedb::ViewContext) -> Vec<Player> {
    ctx.db.players().owner().filter(ctx.sender()).collect()
}

    (#​5111)

  • TypeScript: Declare primary keys at the column/row level:

    const Player = t.row('Player', {
  id: t.u64().primaryKey(),
  owner: t.identity().index('btree'),
  name: t.string(),
});

export const my_players = spacetimedb.view(
  { public: true },
  t.array(players.rowType),
  ctx => Array.from(ctx.db.players.owner.filter(ctx.sender))
);

    (#​5111)

  • C#: Following Rust and TypeScript support in previous releases, C# modules can now declare primary keys on procedural views:

    [SpacetimeDB.View(primaryKey: nameof(Player.Id))]
public static List<Player> MyPlayers(ViewContext ctx) => ...

    (#​5246)

Performance & Correctness

  • Commitlog configuration knobs: Added max_segment_size, write_buffer_size, and preallocate_segments configuration options to config.toml for the commitlog. The default write_buffer_size has been increased from 8KiB to 128KiB to optimize high-throughput workloads.
    (#​5074)

Bug Fixes

  • Timestamp primary keys in C#: Timestamps can now be used as primary keys in C# modules, making C# consistent with the other module languages.
    (#​5262)

What's Changed

Full Changelog: v2.5.0...v2.6.0

v2.5.0

2.5.0 graduates procedures to stable availability, improves billing metric accuracy, and includes CLI usability fixes.

Features
Procedures are now stable (Ungated from unstable)

Procedures-scheduled, transaction-capable server-side functions-and the outgoing HTTP client (ctx.http) are now available without opting into unstable features (#​5164).

  • Rust: The #[spacetimedb::procedure] macro, ProcedureContext, with_tx/try_with_tx, and scheduled procedures now work without features = ["unstable"].
  • C#: [Experimental("STDB_UNSTABLE")] removed from ProcedureContext.WithTx/TryWithTx.
  • C++: Procedure ABI, transaction execution, and outgoing HTTP client are now available without SPACETIMEDB_UNSTABLE_FEATURES.

HTTP handlers/webhooks, views, and RLS (client_visibility_filter) remain gated behind unstable.

Primary key support for procedural views (C#)

Following Rust and TypeScript support in v2.4.1, C# modules can now declare primary keys on procedural views, enabling clients to receive OnUpdate events when subscribed to them (#​5246).

Layout-altering automigrations for event tables

Event tables now support a broader set of schema- and layout-altering automigrations, including column removal, reordering, and type changes that would be rejected for regular tables (#​5269). This enables more flexible schema evolution for event-only tables without requiring manual migration.

Performance & Correctness
  • Deterministic row insertion with BTreeSet storage (#​5071): Non-full pages are now stored in a BTreeSet sorted by available var-len granules rather than an unsorted Vec. This fixes accidentally-quadratic behavior during bulk inserts and ensures deterministic row insertion locations across datastore restarts
Bug Fixes
  • wasm_memory_bytes metric accuracy (#​5131): The metric now correctly reports memory for all Wasmtime instances (cooperatively updated via increment/decrement) and no longer includes V8 instances. Billing impact: billing code should now charge for the sum of wasm_memory_bytes + v8_used_heap_size_bytes. Expect recorded usage per database to increase as we now account for all instances, not just one.
  • Template version constraints (#​5228): All templates now consistently use major.minor version constraints. Previously, inconsistent version constraints could cause the CLI to initialize templates expecting versions that did not exist.
  • CLI publish --delete-data config fallback (#​5256): Removes the forced positional database name requirement, allowing spacetime.json to provide the database name.
  • CLI call with hex Identity arguments (#​5254): The call command now accepts hex strings for Identity parameters without requiring full JSON tuple syntax.

What's Changed

New Contributors

Full Changelog: clockworklabs/SpacetimeDB@v2.4.1...v2.5.0

v2.4.1

We are releasing two small patches on top of 2.4.0:

(#​5111) Add primary key support for procedural views to rust and ts modules

Adds support for primary keys to procedural views in rust and typescript modules. Now clients can receive update events when subscribed to such views.

(#​5145) Fix index schema from st tables.
This fixes #​4701.

More to come soon!

Full Changelog: clockworklabs/SpacetimeDB@v2.4.0...v2.4.1

v2.4.0

2.4.0 brings a headline new capability for Rust modules HTTP handlers alongside meaningful improvements to runtime performance, durability correctness, and server-side observability. The changelog is focused but every entry is production-relevant.

Features

HTTP handlers in modules

This is currently an unstable feature and will need to be enabled to have be available.

  • Rust users can enable unstable features in their Cargo.toml:
[dependencies]
spacetimedb = { version = "1.*", features = ["unstable"] }
  • C# users can enable unstable features by adding #pragma warning disable STDB_UNSTABLE at the top of your file.
  • C++ users can enable unstable features by adding #define SPACETIMEDB_UNSTABLE_FEATURES before including the SpacetimeDB header.

Modules can now define custom HTTP routes and serve arbitrary HTTP requests directly from module code (Rust: #​4636, Typescript: #​4980, C#: #​5024,C++: #​5023).

Using a Rust as an example, annotate a function with #[spacetimedb::http::handler] to create a handler, then wire it into your module's routing table with #[spacetimedb::http::router].

#[spacetimedb::http::handler]
fn insert(ctx: &mut HandlerContext, request: Request) -> Response {
    let body: Vec<u8> = request.into_body().into_bytes().into();
    let id = ctx.with_tx(|tx| tx.db.data().insert(Data { id: 0, body }).id);
    Response::new(Body::from_bytes(format!("{id}")))
}

#[spacetimedb::http::router]
fn router() -> Router {
    Router::new().post("/insert", insert).get("/retrieve", retrieve)
}

#​5024 adds the C# handler/router API [SpacetimeDB.HttpHandler], [SpacetimeDB.HttpRouter]
#​5023 adds the C++ handler/router API SPACETIMEDB_HTTP_HANDLER(), SPACETIMEDB_HTTP_ROUTER()

All user-defined routes are exposed under /v1/database/:name_or_identity/route/{*path}. Handlers have access to a HandlerContext that can open a database transaction, giving you full read/write access to your tables.

This opens the door to webhook integrations, REST-style APIs for non-realtime clients, and any other HTTP-driven interaction you want to build on top of your SpacetimeDB module.

Faster WASM reducer execution

Reducers now run on a dedicated synchronous WASM runtime backed by a single OS thread, instead of sharing the async runtime that procedures use (#​5095). Because reducers never yield, the old async scaffolding was pure overhead. The synchronous path removes that cost from the hot path for every reducer invocation.

Bug Fixes

  • Durability: silent data loss on resume fixed. The commitlog could silently corrupt a segment on restart if trailing bytes shorter than a commit header were left behind. A subsequent append would render the segment corrupt, and anything written after those trailing bytes would become unreachable after the next restart. The segment is now truncated to its validated size before writes resume (#​5116).
  • V8 heap metrics now cover procedure workers. Previously V8HeapMetrics were tracked only for reducer workers, leaving memory usage by JavaScript procedure workers invisible. Procedure worker heap usage is now aggregated and reported alongside the reducer worker metrics (#​5122).
  • Commitlog decode errors include context. Errors encountered while decoding commits now carry additional context, making it substantially easier to diagnose corrupted or truncated log segments in production (#​5129).
  • Reverted energy/execution-time conversion in V8 host. A regression introduced in v2.3.0 in how execution time was converted to energy units for JavaScript modules was reverted (#​4927).

What's Changed

Full Changelog: clockworklabs/SpacetimeDB@v2.3.0...v2.4.0

v2.3.0

This release brings first-party Godot support and major WebSocket performance improvements. We've also landed significant pipeline optimizations, commitlog enhancements, and expanded our framework coverage.

Features

First-party Godot SDK and Blackholio Tutorial

SpacetimeDB now officially supports Godot with a complete C# SDK integration. The new Blackholio tutorial walks through building a multiplayer asteroids-style game, demonstrating best practices for entity replication, player input handling, and game state management in Godot (#​4920).

Faster WebSocket Transport with Batched Responses

The WebSocket layer now pipelines and batches responses using the v3 protocol, significantly reducing per-message overhead under high load. Combined with pipelined JavaScript module operations (#​4962), WASM module operations (#​4973), and a fully pipelined WebSocket send path (#​5051), this delivers substantially improved throughput for real-time applications.

HTTP/2 Backend Support

The SpacetimeDB server now supports HTTP/2, enabling more efficient client connections with multiplexed streams and header compression (#​5027).

Vue useProcedure Hook

Following the React pattern, Vue developers now have a first-class useProcedure composable for calling SpacetimeDB procedures with full TypeScript support (#​4999).

Unity 6 WebGL Compatibility

C# modules and clients now support Unity 6's WebGL runtime, automatically selecting between getWasmTableEntry and dynCall as appropriate for the Unity version (#​4961).

Commitlog Performance and Operations

The durability layer gained several improvements:

  • Configurable commitlog compression knobs for operational tuning (#​5074)
  • Compression deferred when under write load to prioritize throughput (#​4974)
  • Non-blocking compression that doesn't hold locks (#​4981)
  • Proper handling of empty tail segments on resumption (#​4863)
Rust DbContext Generics

Rust modules can now be generic over DbContext, enabling code reuse between client and server contexts while maintaining type safety (#​4707).

API Changes

  • Deprecated: ReducerContext::identity is deprecated in favor of database_identity to clarify that this represents the module's identity, not the caller's (#​4843)

Bug Fixes

  • Fixed a segfault in the V8 JavaScript runtime that could crash the server (#​4986)
  • Fixed connection lifecycle callbacks not firing correctly in all disconnection scenarios (#​4935)
  • Fixed panics during unsubscribe operations (#​4938)
  • Fixed view auto-migration when using canonical names (#​4985)
  • Eliminated unnecessary msync calls on the entire offset index file, improving write performance (#​5018)
  • Fixed directory fsync issues on Windows snapshots (#​4939)
  • Fixed auth error details leaking in debug output (#​5000)
  • Prepared statements are now properly rolled back on transaction failure (#​4979)

Infrastructure

  • Client binaries are now distributed from AWS instead of DigitalOcean for improved reliability (#​5077)
  • Internal: cargo ci dlls renamed to cargo regen csharp dlls (#​4972)

What's Changed

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 enabled auto-merge (squash) November 8, 2025 09:26
@renovate renovate Bot changed the title chore(deps): update streetsidesoftware/cspell-action action to v8 chore(deps): update all dependencies (major) Nov 12, 2025
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 6 times, most recently from 1984f09 to 332875f Compare November 19, 2025 02:53
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 4 times, most recently from 88b5dcc to 18b8cbc Compare November 27, 2025 09:40
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 2 times, most recently from d73c132 to d765d65 Compare December 3, 2025 06:51
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 2 times, most recently from d81b31f to 87688b7 Compare December 10, 2025 16:44
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 3 times, most recently from e437d39 to 8d1a82d Compare January 15, 2026 09:39
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch from 8d1a82d to 6aff418 Compare January 26, 2026 20:52
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 3 times, most recently from b24c94f to f2dd039 Compare February 17, 2026 21:36
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 2 times, most recently from 810f4d6 to c7c7dc5 Compare February 26, 2026 21:35
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 5 times, most recently from 812d657 to 036be45 Compare March 11, 2026 13:21
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch from b3d01b1 to b850c35 Compare April 22, 2026 04:57
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 2 times, most recently from b17796e to cd9c89f Compare May 7, 2026 20:39
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 4 times, most recently from 53fe83e to e507bde Compare May 13, 2026 20:54
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 3 times, most recently from fb9c4fa to d8d8672 Compare May 21, 2026 14:04
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 3 times, most recently from 97a7e92 to 4f79663 Compare June 2, 2026 18:44
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 5 times, most recently from 72674d6 to 85b8c83 Compare June 16, 2026 19:06
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 5 times, most recently from 4f1e89b to 4fb2e54 Compare June 22, 2026 12:58
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch from 4fb2e54 to 9fcf57c Compare July 2, 2026 02:47
@renovate
renovate Bot force-pushed the renovate/major-all-deps branch 5 times, most recently from b651a9a to fa6a417 Compare July 16, 2026 06:14
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants