Skip to content

chore(release): 1.3.5 - #192

Merged
andrei-hasna merged 1 commit into
mainfrom
release/emails-1.3.5
Jul 31, 2026
Merged

chore(release): 1.3.5#192
andrei-hasna merged 1 commit into
mainfrom
release/emails-1.3.5

Conversation

@andrei-hasna

@andrei-hasna andrei-hasna commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Patch release shipping the emails ui fix merged in #191 (squash 9c91d66, adversarial GO by Priscus).

@opentui/core is now external in the TUI runtime build, so it resolves its own version-matched native prebuilt from inside its own package tree instead of binding to a hoisted copy whose ABI predates createEventSink. Before the fix, emails ui could not start in any real terminal on 1.3.4.

package.json only, 1.3.4 → 1.3.5, matching the shape of the 1.3.4 release commit (51c7b86) — no changelog restructuring, so the ## [Unreleased] sha pin in src/workflow-contract.test.ts is unaffected.

Publish intent posted to #git-publishing (612684) before publishing, per the operating rules.

Task: f60d8993


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Ships the `emails ui` fix from #191: `@opentui/core` stays external so it
resolves its own version-matched native prebuilt instead of binding to a
hoisted copy whose ABI predates the symbol it calls.

Task: f60d8993

Agent: Augustus
@andrei-hasna
andrei-hasna merged commit 4940b0f into main Jul 31, 2026
4 checks passed
@andrei-hasna
andrei-hasna deleted the release/emails-1.3.5 branch July 31, 2026 07:49
andrei-hasna added a commit that referenced this pull request Aug 5, 2026
Cuts 1.3.7 so the merged label-scan CPU fix reaches installs.

main has carried the fix since 024ad84 (PR #198, task be9b3bb0) but stayed at
version 1.3.6, which is already the published npm version — so the fix reached
nobody. This bumps package.json and nothing else.

The fix bounds SelfHostedMailDataSource.listLabelSummaries(), which walked the
entire mailbox over HTTP on every 30s sidebar refresh with the walks stacking.
Measured source-vs-source through one pty harness: 68.8% -> 4.4% of a core,
climb eliminated, RSS flat. Mechanism control against a 340-page store:
340 requests / 118.2 MB before, 10 requests / 3.4 MB after.

CHANGELOG.md is deliberately untouched. Its [Unreleased] section holds work
already shipped in 1.3.3 through 1.3.6 — there are no changelog sections for
those versions, and the OpenTUI entry in it describes fixing a crash that 1.3.4
exhibited, which shipped in 1.3.5. Sectioning that block under 1.3.7 would
attribute four releases to this one. Leaving it also keeps the
unreleasedSectionSha256 tripwire in src/workflow-contract.test.ts valid without
re-pinning a section this release did not author. The drift is filed separately.

This matches the repo's observed practice: chore(release): 1.3.5 (#192) was
package.json only, 1 file changed.

Published manually by token because this repo has no automated publish path —
no release.yml and no tag-triggered workflow of any name; npm trusted
publishing binds to a file that does not exist (task c96977b5).

Agent: Silvanus
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant