Skip to content

release: promote v0.1.44-beta.6 - #332

Closed
Obed0101 wants to merge 109 commits into
mainfrom
dev
Closed

Obed0101 wants to merge 109 commits into
mainfrom
dev

Conversation

@Obed0101

Copy link
Copy Markdown
Contributor

Summary

Promote the verified dev candidate to main for the v0.1.44-beta.6 prerelease. The candidate includes the beta.5 dependency/security fixes, terminal cancellation and loop completion recovery, queued prompt visibility, and the TUI transcript follow fix for viewport/Shell-output reflows.

Type

  • Bug fix
  • Feature
  • Documentation
  • Refactor
  • Release/package maintenance
  • Security hardening

Verification

Screenshots or Recordings

Not applicable to this release promotion; the user-facing TUI behavior has native PTY evidence in PR #331.

Checklist

  • I kept this promotion focused.
  • The candidate has a beta changelog entry.
  • Prior required PR checks passed.
  • No secrets or private runtime data are included.
  • Release artifact and installer checks remain required in the release workflow.

Obed0101 added 30 commits June 12, 2026 20:41
Adds public community files, issue and PR templates, release/installer docs, package/community/wiki docs, CodeQL workflow, and release note config.
Adds the guarded release workflow, pinned supply-chain automation, release documentation, and release-blocking OSV gate.
* docs: add public community and release guides

Promotes community files, issue templates, release and installer docs, wiki docs, package docs, labels guidance, release notes config, and CodeQL workflow to main.

* ci: publish release supply-chain hardening

Adds guarded release infrastructure, pinned automation, supply-chain docs, and release-blocking OSV gate.

* ci: fix release workflow dispatch

Moves release cache env away from unavailable runner context so manual dispatch can parse.

* ci: harden release dry runs

* ci: unblock release asset dry run (#60)

* ci: avoid dynamic installs during release build (#61)

* ci: stamp release binaries with version (#62)

* fix(tui): clarify agent mode controls

Clarify TUI agent controls, add upcoming changelog notes, and include release workflow changes in generated changelogs.

* feat(tui): add context usage modal

* ci: update actions for node24 runners (#67)

* docs: expand MendCode customization guide (#70)

* docs: show mascot only in README header (#72)

* docs: remove README mascot header (#73)

* chore: sync dev into main (#78)

* docs: add public community and release guides

Adds public community files, issue and PR templates, release/installer docs, package/community/wiki docs, CodeQL workflow, and release note config.

* ci: harden release supply chain gates

Adds the guarded release workflow, pinned supply-chain automation, release documentation, and release-blocking OSV gate.

* docs: expand MendCode customization guide (#69)

* docs: show mascot only in README header (#71)

* docs: remove README mascot header (#74)

* fix: show MendCode version on welcome

* fix: align MendCode version and CLI name (#76)
* fix: backport opencode terminal sdk improvements

* docs: prepare v0.1.3 release notes
* docs: tighten MendCode promotion branch policy

* fix: prepare v0.1.4 compaction and prompt fixes
* fix: backport opencode runtime updates

* docs: add v0.1.5 changelog
Obed0101 and others added 28 commits August 20, 2026 19:51
* fix: size short reasoning blocks

* fix: keep permission selection stable during hover rechecks

* fix: remove unused session transcript clearance

* docs: complete v0.1.34 release notes
Prepare MendCode v0.1.37 with bounded Loop/Workflow recovery and TUI reliability fixes.
Centralize source paths, reorganize docs navigation, and expand Mermaid fixtures by default with regression coverage.
Harden session completion, cancellation, reconnect recovery, global data layout migration, installers, plugin configuration, and Effect HTTP API parity for v0.1.40.

Includes and expands the original installer contribution from #296.

Co-authored-by: Gabriel Guerra <gfranklings@gmail.com>
Co-authored-by: jraleman <jraleman@bendiburg.com>
* fix: refresh release dependency security pins

* fix: refresh toml security pin
* fix: refresh release dependency security pins

* fix: refresh toml security pin

* fix: use reproducible pnpm release installs

* ci: allow known incomplete npm license metadata
* release: prepare v0.1.39

* fix: harden session delivery and runtime reliability

* fix: preserve queued prompt delivery during interrupt

* release: prepare v0.1.43
…ity (#319)

* feat: prepare updater recovery and opt-in continuity integration

* ci: exercise runtime and recovery contracts on Linux

* fix: normalize bundled auth plugins and escape run arguments

* ci: isolate test processes and their temporary databases

* release: prepare v0.1.44-beta.1

* ci: expose Windows installer errors with a verified fixture

* fix: keep Windows installer compatible with PowerShell 5.1

* fix: pass a null backup path for atomic Windows status updates

* fix: verify Windows installer hashes without module autoloading
…hestration (#323)

* feat: add backend Smart Approval policy and review controls

* feat: add context profiles, tool discovery and confined Code Mode

* docs: prepare v0.1.44-beta.3 release notes

* fix: update Drizzle identifier escaping before beta publication
Integrate the development checkpoint and document its experimental limits. CI passed for runtime/recovery, CodeQL, repository guards, dependency review and deep security scanners. Release acceptance remains separate.
Update qs to patched 6.16.0 within the existing release-age policy and remove the expired exceptions. Runtime, dependency, repository and security checks pass.
Align fixed release dependencies and provider types so the beta candidate passes the OSV gate and typecheck.
Unblock terminal loop completion and keep queued prompt controls aligned with visible user input.
@Obed0101

Copy link
Copy Markdown
Contributor Author

Closed without merge: this promotion PR has a real dev/main merge conflict (109 commits, 891 files). The prerelease workflow is intentionally dispatched from main while selecting the immutable verified dev SHA for beta candidates, so this conflict is not resolved by rewriting or force-merging history.

@Obed0101 Obed0101 closed this Sep 10, 2026
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