Skip to content

chore(main): release 1.4.0 - #147

Merged
jeremymcs merged 1 commit into
mainfrom
release-please--branches--main--components--patchdeck
Aug 20, 2026
Merged

chore(main): release 1.4.0#147
jeremymcs merged 1 commit into
mainfrom
release-please--branches--main--components--patchdeck

Conversation

@github-actions

@github-actions github-actions Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.4.0 (2026-08-20)

Features

  • recover from failed automation without manual clearing (24a1ce4)
  • recover from failed automation without manual clearing (16a6b40)

Bug Fixes

  • cut GitHub API spend on coverage, etags, feedback, CI, and releases (9a2c34d)
  • finalize code-owner fallback worktree before cleanup (d7087a4)
  • finalize code-owner fallback worktree before cleanup (5e51db4)
  • increase agent evaluation and apply timeouts for slow models (d87114b)
  • increase agent evaluation and apply timeouts for slow models (bf4ecc8)
  • persist PR list etags and reuse issue page 1 (cafc106)
  • prevent reply loop on PatchDeck's own audit-trail comments (9f9a29a)
  • raise agent apply and fallback timeouts for large fix batches (f980a1a)
  • raise agent apply and fallback timeouts for large fix batches (4932b78)
  • reply to and resolve rejected review threads (68cc7c9)
  • reply to and resolve rejected review threads (and prevent reply loop) (3670496)
  • report issue work timeout cause (f61be7f)
  • report issue work timeout cause (ec56330)
  • reuse settled CI status fetches for a commit SHA (1df430f)
  • skip review-thread GraphQL when PR comments are unchanged (1c423f9)
  • stage agent-resolved conflicts before checking unmerged files (5fc4fbc)
  • stage agent-resolved conflicts before checking unmerged files (40d01da)
  • stop paging closed PRs once the release since-bound is passed (86cea61)
  • stop queued jobs from failing in-progress babysit runs (b23a4fc)
  • stop queued jobs from failing in-progress babysit runs (6f71213)
  • stop Search API polling for issue coverage (0316a82)
  • sync tauri release versions (f190b4f)
  • sync Tauri release versions (d143f3f)
  • ui: make issues and PRs usable on mobile (1162b37)
  • ui: make issues and PRs usable on mobile (b0965e5)
  • ui: stop the detail action rail from crushing the title (c8e7369)
  • update release please action (a55634a)
  • update Release Please action (7c520f7)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--patchdeck branch from 7012ed1 to adff996 Compare July 1, 2026 11:23
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--patchdeck branch from adff996 to 8d3072f Compare August 18, 2026 03:20
@github-actions github-actions Bot changed the title chore(main): release 1.3.1 chore(main): release 1.4.0 Aug 18, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--patchdeck branch 4 times, most recently from ebddeb8 to f5572fe Compare August 18, 2026 08:23
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--patchdeck branch 2 times, most recently from 1cf75ac to c568eae Compare August 18, 2026 13:20
jeremymcs added a commit to cwbcheng/patchdeck that referenced this pull request Aug 18, 2026
Two configuration bugs kept producing pull requests that could never merge.

Dependabot grouped every npm update under a single `*` pattern, so ten breaking
majors arrived as one PR (jeremymcs#175): tailwindcss 3->4, zod 3->4 and typescript
5->7 each broke the build on their own, and typescript 7 is not supported by
any released typescript-eslint. The group now batches only minor and patch
updates; majors come as individual PRs that can be reviewed and migrated one at
a time.

release-please ran with the default GITHUB_TOKEN. GitHub deliberately does not
start workflow runs for pull requests opened with that token, so the required
lint-and-test check never ran on a release PR and every one of them stayed
BLOCKED (jeremymcs#147 had to be nudged with an empty commit). Passing a PAT makes the
PR author-created from Actions' point of view, which starts the checks.

Requires a repository secret named RELEASE_PLEASE_TOKEN, a PAT with contents
and pull-requests write scope. The expression falls back to GITHUB_TOKEN so the
workflow keeps working until the secret exists.
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--patchdeck branch 2 times, most recently from 870e7b8 to 9a17b5f Compare August 18, 2026 15:16
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--patchdeck branch from 9a17b5f to db6c39e Compare August 20, 2026 01:47
@jeremymcs
jeremymcs merged commit 7a4ef15 into main Aug 20, 2026
3 checks passed
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant