Repository navigation
chore(release): bump version to 0.5.38 - #750
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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#25was 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_HUMANand blocked the PR, so any comment nobody had anticipated stopped the loop. A🐳 Image for commit … publishedcomment fromgithub-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_REQUESTEDreview 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:
NEEDS_HUMAN. They are now not enqueued at all.QUEUED. It now preserves the existing status.Other changes
.catch(() => {})(Fix: eliminate silently swallowed errors via .catch(() => {}) #744).as anycasts in the projects page (Remove pervasive as any casts in projects page #731).eslint10.8.0 → 10.8.1,tsx4.23.9 → 4.23.11,lucide-react1.29.0 → 1.30.0,github/codeql-actionbump.Upgrade notes
No configuration changes. Behaviour change only in PR-follow-up ingestion; existing queue items are unaffected.