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

Package	From	To
gh-workflow	0.8.1	0.9.0
posthog-rs	0.22.0	0.23.2
sysinfo	0.38.4	0.39.6
termimad	0.34.1	0.35.1
rmcp	1.8.0	3.1.2

Updates gh-workflow from 0.8.1 to 0.9.0

Commits

• 4073ed3 chore(deps): update rust crate serde_yml to 0.0.13 (#221)
• f5ac2ab chore(deps): update actions/checkout action to v7 (#224)
• 487f3bc feat(gh-workflow-tailcall): add forge-style release workflows
• b68b392 chore(deps): update rust crate syn to v3.0.3 (#233)
• cbec366 chore(deps): update rust crate serde_json to v1.0.151 (#232)
• c04e6b3 chore(deps): update rust crate syn to v3.0.2 (#231)
• d9a28b5 chore(deps): update rust crate syn to v3 (#230)
• 283ed76 chore(deps): update rust crate serde to v1.0.229 (#229)
• e4d5d6a chore(deps): update rust crate quote to v1.0.47 (#228)
• 68510ef chore(deps): update rust crate async-trait to v0.1.91 (#227)
• Additional commits viewable in compare view

Updates posthog-rs from 0.22.0 to 0.23.2

Release notes

Sourced from posthog-rs's releases.

0.23.2

Patch changes

• ea92c93 Surface feature flag payloads from local evaluation.

  The definitions manifest carries each flag's payloads, but locally evaluated flags always reported payload: None, so FeatureFlagEvaluations::get_flag_payload returned nothing for them. When flag_keys was fully covered locally there was also no /flags round trip left to recover the payload from. Local evaluation now resolves the payload for the matched value ("true" for a boolean match, the variant key for a multivariate one) and decodes it exactly like a /flags payload, so a flag returns the same payload whichever path evaluated it. As a result, $feature_flag_called events for locally evaluated flags now carry $feature_flag_payload, matching remote evaluation. — Thanks @​slshults!

• 962282c Stop malformed cohort definitions from aborting the process during local evaluation.

  Cohort resolution recursed through nested cohort references with nothing bounding the recursion, so a cohort that referenced itself, directly or through another cohort, recursed until the thread stack was exhausted. A Rust stack overflow aborts the process rather than panicking catchably, so a single bad definitions response could take down the calling server, and would again on restart as soon as the poller refetched. A long chain of distinct cohorts reached the same abort without any cycle at all, and because each cohort is a separate shallow entry in the manifest, such a chain also cleared serde_json's own nesting limit on the way in.

  Cohort resolution now tracks the cohorts on the active resolution path and the combined depth of cohort references and nested property groups. A repeated cohort is reported as a cycle, and total resolution depth is capped at 100. Either is reported as inconclusive, so the flag falls back to server-side evaluation rather than resolving to a wrong value. Referencing the same cohort twice down sibling branches still resolves normally, since IDs are released as the recursion unwinds. — Thanks @​slshults!

0.23.1

Patch changes

• cf8952a Fix local flag evaluation for projects that use cohorts.

  The /flags/definitions/?send_cohorts payload maps each cohort ID directly to its property group ({"type": "AND"|"OR", "values": [...]}), but Cohort required non-existent id/name/properties fields, so the whole LocalEvaluationResponse failed to deserialize and no flags loaded at all. Cohort now deserializes the real payload, and cohort matching recurses through nested AND/OR groups and cohort references instead of flattening them. — Thanks @​posthog[bot] for your first contribution 🎉!

0.23.0

Minor changes

• 015e5a3 Add an atomic trace_context capture option and a client-level trace-context provider so exception events can be linked to distributed traces without adding telemetry dependencies to the SDK. — Thanks @​hpouillot for your first contribution 🎉!

Changelog

Sourced from posthog-rs's changelog.

0.23.2 — 2026-08-10

Patch changes

• ea92c93 Surface feature flag payloads from local evaluation.

  The definitions manifest carries each flag's payloads, but locally evaluated flags always reported payload: None, so FeatureFlagEvaluations::get_flag_payload returned nothing for them. When flag_keys was fully covered locally there was also no /flags round trip left to recover the payload from. Local evaluation now resolves the payload for the matched value ("true" for a boolean match, the variant key for a multivariate one) and decodes it exactly like a /flags payload, so a flag returns the same payload whichever path evaluated it. As a result, $feature_flag_called events for locally evaluated flags now carry $feature_flag_payload, matching remote evaluation. — Thanks @​slshults!

• 962282c Stop malformed cohort definitions from aborting the process during local evaluation.

  Cohort resolution recursed through nested cohort references with nothing bounding the recursion, so a cohort that referenced itself, directly or through another cohort, recursed until the thread stack was exhausted. A Rust stack overflow aborts the process rather than panicking catchably, so a single bad definitions response could take down the calling server, and would again on restart as soon as the poller refetched. A long chain of distinct cohorts reached the same abort without any cycle at all, and because each cohort is a separate shallow entry in the manifest, such a chain also cleared serde_json's own nesting limit on the way in.

  Cohort resolution now tracks the cohorts on the active resolution path and the combined depth of cohort references and nested property groups. A repeated cohort is reported as a cycle, and total resolution depth is capped at 100. Either is reported as inconclusive, so the flag falls back to server-side evaluation rather than resolving to a wrong value. Referencing the same cohort twice down sibling branches still resolves normally, since IDs are released as the recursion unwinds. — Thanks @​slshults!

0.23.1 — 2026-08-10

Patch changes

• cf8952a Fix local flag evaluation for projects that use cohorts.

  The /flags/definitions/?send_cohorts payload maps each cohort ID directly to its property group ({"type": "AND"|"OR", "values": [...]}), but Cohort required non-existent id/name/properties fields, so the whole LocalEvaluationResponse failed to deserialize and no flags loaded at all. Cohort now deserializes the real payload, and cohort matching recurses through nested AND/OR groups and cohort references instead of flattening them. — Thanks @​posthog[bot] for your first contribution 🎉!

0.23.0 — 2026-08-07

Minor changes

• 015e5a3 Add an atomic trace_context capture option and a client-level trace-context provider so exception events can be linked to distributed traces without adding telemetry dependencies to the SDK. — Thanks @​hpouillot for your first contribution 🎉!

Commits

• fa1ba0a chore: Release v0.23.2 [skip ci]
• 962282c fix(flags): bound cohort recursion in local evaluation (#200)
• ea92c93 feat(flags): surface payloads from local flag evaluation (#199)
• bdaf852 chore(deps): bump httpmock from 0.7.0 to 0.8.3 (#198)
• 23bd119 chore: Release v0.23.1 [skip ci]
• cf8952a fix(flags): deserialize cohorts payload for local evaluation (#187)
• 8619ff1 chore(deps): bump github/codeql-action/analyze from 4.35.5 to 4.37.4 (#194)
• cf34383 chore(deps): bump brotli from 7.0.0 to 8.0.4 (#192)
• e41e6f1 chore(deps): bump planetscale/ghcommit-action from 0.2.20 to 0.2.22 (#190)
• 0192384 chore(deps): bump getsentry/action-github-app-token from 2.0.0 to 4.0.0 (#195)
• Additional commits viewable in compare view

Updates sysinfo from 0.38.4 to 0.39.6

Changelog

Sourced from sysinfo's changelog.

0.39.6

• NetBSD: Add support for disk I/O usage.
• NetBSD: Improve retrieval of disk information.

0.39.5

• macOS: Fix build for apple app store

0.39.4

• Unix: Fix soundness issue when retrieving user's groups.
• macOS: Add new macOS version name.
• macOS: Fix inaccurate open_files returned value.

0.39.3

• Unix: Fix retrieval of Network::mac_addr.
• Linux: Improve retrieval of process information if process terminates while doing so.

0.39.2

• Windows: Greatly improve performance of System::refresh_cpu_specifics when CPU usage is not requested.
• iOS: Fix compilation error when user feature is enabled.
• Linux: Correctly set thread information for processes.

0.39.1

• Linux: Fix wrong network numbers computation.

0.39.0

• Update minimum supported rust version to 1.95.
• Add new NetworkData::operational_state API.
• Add new Process::cgroup_limits API (only returning data on Linux).
• All supported systems other than Windows: Improve performance of Networks::refresh*.
• All supported systems other than Windows: Fix soundness issue when retrieving users.
• Linux: Take into account parent cgroup memory limits.
• Linux: Fix panic when retrieving process information on ESXi.
• FreeBSD: Use the name of dataset as name for zfs disks.

Commits

• 1bc6ed4 Update crate version to 0.39.6
• da9bea0 Update CHANGELOG for 0.39.6
• cefd877 Update src/unix/bsd/netbsd/system.rs
• 9d79f93 Fix NetBSD disk I/O and process I/O statistics
• 029025e Update crate version to 0.39.5
• 78205e7 Update CHANGELOG for 0.39.5
• 2a39746 Fix build for apple app store
• c07bb44 Update CHANGELOG for 0.39.4
• 559b07d Update crate version to 0.39.4
• 07e3177 Linux: Fix soundness issue when retrieving user groups
• Additional commits viewable in compare view

Updates termimad from 0.34.1 to 0.35.1

Changelog

Sourced from termimad's changelog.

v0.35.1 - 2026-07-11

• Fix a panic in some cases of tables with rows having more columns than the header row - Fix #77

v0.35.0 - 2026-07-10

• Support for ordered lists, and their depth dependent styling - Fix #75
• Unordered list items can also be created with - and + and not just *
• CompoundStyle, LineStyle, and StyledChar are now Copy

Commits

• See full diff in compare view

Updates rmcp from 1.8.0 to 3.1.2

Release notes

Sourced from rmcp's releases.

rmcp-macros-v3.1.2

Fixed

• emit cache hints from handler macros (#1120)

Other

• upgrade darling and syn (#1138)

rmcp-v3.1.2

Fixed

• (auth) map 401/403 challenges on the SSE GET stream (#1152)
• (sse) loop instead of recursing when skipping SSE events (#1146)
• (auth) preserve issuer trailing slash during discovery (#1145)

rmcp-macros-v3.1.1

Fixed

• emit cache hints from handler macros (#1120)

Other

• upgrade darling and syn (#1138)

rmcp-v3.1.1

Fixed

• emit cache hints from handler macros (#1120)
• expose MRTR state to tool handlers (#1104)
• disambiguate input-required results (#1103)

Other

• make async-trait optional (#1119)

rmcp-macros-v3.1.0

Added

• add strict stateless protocol metadata validation (#1091)

Other

• document the ping utility with examples (#1106)
• complete Tier 1 feature docs and finalize roadmap (#1101)
• (conformance) meeting requirements for tier 1 (#1087)

rmcp-v3.1.0

Added

... (truncated)

Commits

• 02c62ae chore: release v3.1.2 (#1148)
• c345078 fix(auth): map 401/403 challenges on the SSE GET stream (#1152)
• f8e6382 chore(deps): bump taiki-e/install-action from 2.85.7 to 2.85.8 (#1153)
• 8fb3e04 chore(deps): bump github/codeql-action from 4.37.4 to 4.37.6 (#1154)
• 3c8fb2a fix(sse): loop instead of recursing when skipping SSE events (#1146)
• e150d4f fix(auth): preserve issuer trailing slash during discovery (#1145)
• 9a3168a chore(deps): bump taiki-e/install-action from 2.85.6 to 2.85.7 (#1139)
• baac607 chore: release v3.1.1 (#1115)
• f57d585 chore: upgrade darling and syn (#1138)
• 07bcda2 fix: emit cache hints from handler macros (#1120)
• 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