chore(release): v1.2.4 - #516
Merged
Merged
Conversation
prolific-automation
added
release
dct-ready-for-review
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
script-this
added
team-dct
and removed
dct-ready-for-review
The fix spans filter-sets, eligibility-count, and message help text, not just filters — file-count heuristic mis-tie-broke it into that section.
script-this
added
the
dct-ready-for-review
benmatselby
approved these changes
Sep 2, 2026
dessskris
approved these changes
Sep 2, 2026
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
5 participants
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.
Automated release PR — detected unreleased user-facing commits since
v1.2.3.Version was auto-computed as a PATCH bump (
v1.2.3->v1.2.4). If this batch of changes includes a breaking change (a removed flag, a changed output format — see the version-bump table in DEVELOPMENT.md), edit the## 1.2.4heading inCHANGELOG.mdto the next MINOR version before merging.Merging this PR (with the
releaselabel, already applied) will triggercreate-release.ymlas usual — nothing is released until then.Not the right time (other work still landing, want to batch more in)? Just close this without merging — it won't reopen itself, but if unreleased commits still remain, the next scheduled run will propose a fresh PR.