[senamakel]

Release v0.3.6 from main (chosen over v0.1.7 so the version stays above the existing v0.3.5). Bumps workspace and internal pins to 0.3.6 and updates Cargo.lock. Note: v0.3.x history lives on epic/8056-modules-wiring; this release carries main's content.

[tinysweeper]

Tiny Sweeper review

Reviewed head: 48ca032491de3f291049add95e993ccda751d7c1

Verdict: Ready for maintainer review · Priority: none
Coverage: Reviewed 2 of 3 files; not reviewed: Cargo.lock.
Pull request purpose (title): chore: bump workspac…

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore: bump workspace version to 0.3.6. Purpose (title): chore: bump workspace version to 0.3.6. This release chore raises the workspace version and internal crate pins from 0.1.6 to 0.3.6 and adjusts an existing module test fixture so its required version range follows the crate's own major/minor, keeping the test valid across the bump. No errors were found. The latest-push delta is unavailable.

Unreviewed paths

• Cargo.lock

Review snapshot

Change surface	Files	Review signal	Count
Production	0	Active findings	0
Tests	1	Noted findings	0
Documentation	0	Resolved findings	0
Configuration	1	Pending checks/questions	0

Completeness: Complete
Test assessment: No supported feature-to-test mapping was available; this does not mean tests are absent or passed.

What changed

The workspace version moves from 0.1.6 to 0.3.6 and the three internal pins (tinybus, tinybus-macros, tinybus-module) are updated to `=0.3.6`, keeping them aligned; Cargo.lock is updated accordingly. In the module host requirement test fixture, the hard-coded range [0.1.0, 0.2.0) is replaced with a range derived from the crate's own CARGO_PKG_VERSION_MAJOR/MINOR, producing a half-open range [major.minor.0, major.(minor+1).0) that matches VersionRange::accepts and still contains the fixture's advertised 0.3.6. The critique lane notes one edge case: on a major version bump, minor+1 as the upper bound no longer sits within the same caret line as the fixture version.

Features

• Modified — Workspace version bump to 0.3.6: Raises the workspace package version and keeps the three internal path dependencies pinned with `=` to the same version, so the release version is consistent; crate manifests pick it up via version.workspace = true. (Cargo.toml exclude = ["examples"])
• Internal refactor — Test fixture version range derives from crate version: The required version range in the module test fixture now follows CARGO_PKG_VERSION_MAJOR/MINOR via a half-open range, so a crate version bump keeps the fixture's advertised version inside the accepted range instead of breaking the test. (crates/tinybus/src/module/host_required_tests.rs async fn a_real_required_artifact_is_refused_then_admitted_and_serves_confidenti)

Tests

No supported feature-to-test mapping was produced. Test execution is not inferred.

Findings

No active actionable findings.

Before merge

None.

Agent review details

critique

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The critique lane is Answered and reports the derived range keeps the fixture version inside the half-open range matching VersionRange::accepts; it flags only that a major version bump would make minor+1 sit outside the same caret line.
• Lane summary: The change derives the required version range from the crate's own CARGO_PKG_VERSION_MAJOR/MINOR so the fixture module's advertised version stays inside the half-open range (min inclusive, max exclusive), which matches VersionRange::accepts. The one edge case worth flagging is a major version bump, where the minor+1 upper bound no longer sits within the same caret line the fixture's version belongs to.

security

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The security lane is Answered and found no defects: the change is test-only, the minor+1 arithmetic cannot overflow for realistic versions, and no security-relevant path is touched.
• Lane summary: The change is test-only: it replaces a hard-coded version range in a module-requirements fixture with the crate's own major/minor, which keeps the test valid across version bumps. The arithmetic `crate_minor + 1` cannot overflow for any realistic crates.io version, and no security-relevant path is touched.

tests

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The tests lane is Answered and reports no defects: the fixture change keeps the existing test valid across the version bump, and no new test is owed.
• Lane summary: This is a version bump plus a test-fixture adjustment that derives the required version range from CARGO_PKG_VERSION_MAJOR/MINOR so the existing module test does not break on the 0.1→0.3 bump. No new runtime behaviour is introduced, so no new test is owed; the existing test still exercises the requirement check. No defects found.

commits

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The commits lane is Answered and reports no sensitive content in committed files.
• Lane summary: No sensitive content in committed files.

description

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The description lane is Answered and reports the diff scope (workspace version bump to 0.3.6 plus test adjustment) matches the title and body, yielding [0.3.0, 0.4.0) for the fixture.
• Lane summary: The test fixture change makes the required version range follow the crate version via CARGO_PKG_VERSION_MAJOR/MINOR, using a half-open VersionRange, so a 0.3.6 bump yields [0.3.0, 0.4.0), which correctly contains the fixture's advertised 0.3.6. The description's scope (workspace version bump to 0.3.6 plus test adjustment) matches the diff; no defects found.

Evidence and run details

• Models: ladder/vectors-oai3, deepseek-v4.1-flash
• Spend: $0.000203
• Tokens: 107370 input · 3027 output · 0 cached · 90 embedding
• Updated: 2026-10-26T05:42:43Z

Head	State	Pass summary
8f5383c2dfa3	ready for maintainer review	0 active finding(s), 0 resolved finding(s) (at 2026-10-26T05:27:11Z)
48ca032491de	ready for maintainer review	0 active finding(s), 0 resolved finding(s) (at 2026-10-26T05:42:43Z)

[coderabbitai]

Warning

Review limit reached

• Run on-demand review

_{This review includes 2 billable files and costs up to $0.50.}

Or wait 29 minutes for your next included review.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: b558c60f-8717-49ea-86c2-b30e90795200

Commits

Reviewing files that changed from the base of the PR and between 7197cc2 and 48ca032.

Files ignored due to path filters: 1

• Cargo.lock is excluded by !**/*.lock

Files selected for processing: 2

• Cargo.toml
• crates/tinybus/src/module/host_required_tests.rs

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-26T05:26:57.556456Z	8f5383c	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[tinysweeper]

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0001