Skip to content

chore(release): 0.1.41 - #154

Merged
M3gA-Mind merged 1 commit into
tinyhumansai:mainfrom
M3gA-Mind:chore/release-0.1.41
Oct 24, 2026
Merged

M3gA-Mind merged 1 commit into
tinyhumansai:mainfrom
M3gA-Mind:chore/release-0.1.41

Conversation

@M3gA-Mind

Copy link
Copy Markdown
Collaborator

Summary

Bumps the workspace version from 0.1.40 to 0.1.41 for the release that carries #150 (legacy migration source collections declared for host storage grants). The diff is only the workspace version in Cargo.toml and the four tinychannels* version lines in Cargo.lock.

Why it's needed: openhuman builds tinychannels' storage grant from tinychannels_bus::storage::collections(). Before #150, the module's migrations ensured 14 undeclared legacy collections, the host refused them (schema-is-host-only), and the module faulted on its first storage use, which stopped every channel it serves (openhuman TELEGRAM-0433).

Release steps (morning; nothing is tagged by this PR)

  1. Merge this PR, then wait for main CI to be green at the exact merge commit, with main HEAD == that commit and the Cargo version == 0.1.41.
  2. Push a signed annotated tag v0.1.41 at that commit, once (tag push only).
  3. Verify the module-release run: an immutable release with 18 assets (17 archives + checksum.toml), and checksum.toml digests equal to the GitHub asset digests 17/17.
  4. openhuman follow-up re-pin, after #8327 (0.1.40) merges:
    • the tinychannels records in crates/openhuman-core/src/modules/registry/records_extra.rs (17 archive names + sha256 from checksum.toml);
    • the vendor/tinychannels gitlink → the v0.1.41 tag commit.
      Proof: the embed channel_agents test (channels,storage-sqlite) and the telegram example pass.

Test plan

  • GitHub CI (module-ci) green on this PR

Bumps the workspace version for the release that carries tinyhumansai#150 (legacy
migration sources declared for host storage grants).
@tinysweeper

tinysweeper Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Tiny Sweeper review

Reviewed head: 377e7f326d2e43d01c9673635cf3b3d2ac7eb1e9

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

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore(release): 0.1.41. Release PR for version 0.1.41: it bumps the workspace package version from 0.1.40 to 0.1.41 before packaging, so that the release can carry the storage-collection fix from #150 that stopped channels failing on host storage grants (openhuman TELEGRAM-0433). The description states that the diff only touches the workspace version in `Cargo.toml` and the four `tinychannels*` version lines in `Cargo.lock`. Nothing is tagged here; tagging is a separate, manual step after merge. The latest-push delta is unavailable, so the delta is not described.

Unreviewed paths

  • Cargo.lock

Review snapshot

Change surface Files Review signal Count
Production 0 Active findings 0
Tests 0 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.

Features

  • Modified — Workspace version bump to 0.1.41: The release version is moved to 0.1.41 in `Cargo.toml` so that the release can be tagged and packaged. The manifest comment documents this as the only workspace version to update before packaging. This has no effect on code behaviour. (Cargo.toml, Cargo.toml tinybus = { path = "vendor/tinybus/crates/tinybus" })

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
  • Lane summary: The change bumps only the workspace version from 0.1.40 to 0.1.41, which the manifest comment describes as the sole version source updated before packaging. No behavioural change, no findings. _The code index is behind this pull request (indexed at `c41936424bfb`), so retrieved context may be out of date._

security

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: The security lane is Answered with no findings. The change introduces no dependency, permission, network, or code changes, and changing the version before tagging follows the repository's documented practice.
  • Lane summary: The diff is a single workspace version bump from 0.1.40 to 0.1.41 in the root Cargo.toml, matching the repository's documented practice of changing Cargo package versions through a reviewed PR before tagging. No dependency, permission, network, or code changes are introduced, so there is nothing security-relevant to report. _The code index is behind this pull request (indexed at `c41936424bfb`), so retrieved context may be out of date._

tests

  • Conclusion: Neutral
  • Scope reviewed: all assigned evidence
  • Lane summary: No behavioural change: nothing outside documentation, configuration and tests.

commits

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: The commits lane is Answered with no findings. It reports no sensitive content in committed files.
  • Lane summary: No sensitive content in committed files. _The code index is behind this pull request (indexed at `c41936424bfb`), so retrieved context may be out of date._

description

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: The description lane is Answered with no findings. It states that the diff matches the description: the workspace version in Cargo.toml moves from 0.1.40 to 0.1.41, and the description accurately covers the release steps.
  • Lane summary: The diff is exactly what the description says: the workspace version in Cargo.toml moves from 0.1.40 to 0.1.41, and the description accurately covers the release steps and the reason for the bump. My lookups only confirmed the four tinychannels* Cargo.lock entries already read 0.1.41 rather than showing the diff's lock lines, which is outside what I was shown and not a defect I can attribute to this change. No findings. _The code index is behind this pull request (indexed at `c41936424bfb`), so retrieved context may be out of date._
Evidence and run details
  • Models: ladder/vectors-oai3, deepseek-v4.1-flash
  • Spend: $0.000096
  • Tokens: 65666 input · 1514 output · 15360 cached · 33 embedding
  • Updated: 2026-10-23T23:57:29Z
Head State Pass summary
377e7f326d2e ready for maintainer review 0 active finding(s), 0 resolved finding(s) (at 2026-10-23T23:57:29Z)

tinysweeper 0.1.2

@coderabbitai

coderabbitai Bot commented Oct 23, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ 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: 4b6d468a-2724-43e9-9445-d5bdf6723fc2
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@tinysweeper tinysweeper Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0001

@tinysweeper tinysweeper Bot added the priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect. label Oct 23, 2026
@M3gA-Mind
M3gA-Mind merged commit 055b52b into tinyhumansai:main Oct 24, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant