Skip to content

chore(release): build v0.46.11 - #1122

Merged
github-actions[bot] merged 1 commit into
mainfrom
bot/nightly-macos-version-main-v0.46.11
Jun 7, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
bot/nightly-macos-version-main-v0.46.11

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Automated nightly macOS version bump for v0.46.11.

Source run: https://github.com/browseros-ai/BrowserOS/actions/runs/27085006340
Target ref: main

@github-actions
github-actions Bot merged commit 486cc68 into main Jun 7, 2026
1 check passed
@greptile-apps

greptile-apps Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

PR author is not in the allowed authors list.

@github-actions
github-actions Bot deleted the bot/nightly-macos-version-main-v0.46.11 branch June 7, 2026 06:33
Vasilev Dmitrii (gHashTag) added a commit to gHashTag/BrowserOS that referenced this pull request Aug 1, 2026
…a bold asterisk

Three defects in one chain, each hiding the next, each found only by driving the
same task again.

The brief carried the files in the boundary but not the files a criterion names,
so a task whose contract is about the application and whose lane is a test file
could not be judged at all. That was browseros-ai#1119.

Fixing it changed nothing, because criterion paths were resolved against the git
root while they are written against the project root: `BR-OUTPUT/...` became
`/Users/playra/BrowserOS/BR-OUTPUT/...`, which does not exist, and the miss was
swallowed by a `fileExists` guard. The contract had explicitly asked for a named
file that is missing to be reported as missing rather than skipped; had that
been honoured, the wrong root would have been visible immediately instead of
looking like a criterion with no paths in it. That was browseros-ai#1121.

With the right root the reviewer finally answered - 2733 characters instead of
198, four verdicts a person can read - and the parser reported zero. It requires
a line to begin with the criterion's number, and the model writes `**1. met**`.
Its own comment listed what it accepted, bare and checkbox, and markdown was
never in the list. That was browseros-ai#1122.

Driven the whole way: the same re-review that produced `parsed=0` three times
now produces `asked=4 parsed=4 recorded=4, unchecked=none`. Break test: removing
the markdown tolerance fails three assertions by name.

Ratchet 526 -> 538.

Closes gHashTag/trios#1119
Closes gHashTag/trios#1121
Closes gHashTag/trios#1122
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.

0 participants