Skip to content

chore(release): pending release v0.49.0#720

Open
fro-bot[bot] wants to merge 5 commits into
releasefrom
next
Open

chore(release): pending release v0.49.0#720
fro-bot[bot] wants to merge 5 commits into
releasefrom
next

Conversation

@fro-bot
Copy link
Copy Markdown
Contributor

@fro-bot fro-bot Bot commented Jun 1, 2026

Pending Release: v0.49.0

This PR tracks changes pending release. Released on the next auto-release cycle (Sunday/Wednesday) or via manual dispatch.

Merge this PR to trigger a release. Releases also run automatically on Sunday/Wednesday at 20:00 UTC, or via manual workflow dispatch.

Commits Since Last Release


Auto-generated by the release pipeline. Updated: 2026-06-01 11:06 UTC

fro-bot and others added 2 commits May 31, 2026 17:18
The first /fro-bot add-project on a fresh gateway aborted in pre-flight: a valid
S3 NoSuchKey 404 (the binding key legitimately absent) was misclassified as a
fatal store error, deadlocking first use. The object-store adapter extracted the
SDK error code and HTTP status but discarded them, leaving isNotFound() to match
on message text that misses AWS's 'The specified key does not exist.'

Preserve errorCode and httpStatusCode through the adapter error and classify
not-found by structured code (NoSuchKey / 404) first, falling back to a widened
message regex for S3-compatible stores whose wording differs.

Fixes #713
#723)

fix(prompt): require Fro Bot to submit a review event matching its verdict

PR reviews previously delivered a PASS verdict as a comment-only review,
which never satisfies branch protection's required approval. Map the verdict
to the GitHub review event explicitly: PASS -> approve, CONDITIONAL/REJECT ->
request-changes, and remove the comment-only fallback for verdicts.
marcusrbrown and others added 2 commits June 1, 2026 04:03
* feat(setup): add DEFAULT_OMO_SLIM_VERSION constant + Renovate tracking

* feat(setup): add enable-omo-slim and omo-slim-preset action inputs

Mutually exclusive with enable-omo. Validates preset against the
openai/opencode-go allowlist and fails fast when both plugins are enabled.

* feat(setup): install OMO Slim and assemble its CI config

installOmoSlim runs the pinned slim installer with the validated preset.
buildCIConfig gains a slim mode that registers the slim plugin, pins
default_agent to orchestrator, guards against dual-plugin configs, and
version-gates orchestrator support.

* ci: add OMO Slim smoke job and document the inputs

A workflow_dispatch-gated job exercises enable-omo-slim end to end and
asserts the slim config assembly. README documents the new inputs and
the mutual-exclusivity contract with oMo.

* fix(setup): harden OMO Slim failure and version-gate ordering

Reject unverified slim versions before running the installer, fall back
to a non-slim config when the slim install fails so a missing plugin is
never pinned as default_agent, strip the legacy plugins key in slim mode,
and source the default version from the shared constant.

* chore: rebuild dist with refreshed pnpm store

* ci: drop dedicated OMO Slim job

Slim config assembly is covered by unit tests; a workflow_dispatch-only
job only adds a perpetually-skipped check to every PR. Dispatch fro-bot.yaml
for an on-demand live install smoke when needed.
@fro-bot fro-bot Bot changed the title chore(release): pending release v0.48.2 chore(release): pending release v0.49.0 Jun 1, 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.

2 participants