Skip to content

chore(release): bump version to 0.5.38 - #750

Merged
its-saffron[bot] merged 1 commit into
mainfrom
chore/release-v0.5.38-31235728558
Aug 8, 2026
Merged

its-saffron[bot] merged 1 commit into
mainfrom
chore/release-v0.5.38-31235728558

Conversation

@its-saffron

@its-saffron its-saffron Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Version bump for release v0.5.38. The release will be published after this PR passes the required checks and merges.

Highlights

Fix: the PR-fix loop no longer re-queues itself forever.

misospace/pinchflat#25 was re-enqueued every sweep — twice — dispatching a coder each time at a PR that needed a human. Two independent causes:

Comments now enqueue only on actionable signal. Previously an unclassifiable comment became NEEDS_HUMAN and blocked the PR, so any comment nobody had anticipated stopped the loop. A 🐳 Image for commit … published comment from github-actions[bot] was enough.

The old approach — matching known bot markers — had already been extended once for a size-diff table (llmkube-images#114) and the next bot's format walked straight through. So the default is inverted instead: a comment creates work only if it carries actionable signal, or @-mentions the loop. That filters on whether a comment is a work request rather than on who wrote it, so bots keep their genuinely actionable feedback and chatter from anyone is ignored. The @-mention override means a human can still direct the loop without phrasing the ask for a regex.

Duplicate evidence no longer resurrects a resolved item. An undismissed CHANGES_REQUESTED review is re-read every sweep, so each resolution was undone 15 minutes later. Repeat evidence now preserves the item's status; new evidence re-queues as before. The enqueue is still recorded in history — the status flip caused the churn, not the audit row.

Two reversed contracts

Both are deliberate and worth knowing when reading old tests:

  • Ambiguous comments used to enqueue as NEEDS_HUMAN. They are now not enqueued at all.
  • Repeat evidence used to move an item back to QUEUED. It now preserves the existing status.

Other changes

Upgrade notes

No configuration changes. Behaviour change only in PR-follow-up ingestion; existing queue items are unaffected.

@its-saffron
its-saffron Bot requested a review from joryirving as a code owner August 8, 2026 02:46
@its-saffron
its-saffron Bot enabled auto-merge (squash) August 8, 2026 02:46
@its-saffron
its-saffron Bot merged commit 8669671 into main Aug 8, 2026
6 of 7 checks passed
@its-saffron
its-saffron Bot deleted the chore/release-v0.5.38-31235728558 branch August 8, 2026 02:49
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