feat(tasks): add task-to-task relations (blocks / duplicates / relates)#224
Merged
Conversation
Empty release-trigger commit. The feature itself landed on main in the #222 promotion, but the squash commit was typed chore(release), which release-please ignores when computing releases - so no v14.2.0 release PR was proposed. This commit restates the feature with its original conventional message so release-please proposes v14.2.0 with a proper changelog entry. Refs: #221, #222 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
joshishiv4
approved these changes
Jun 10, 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
2 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.
Summary
One empty commit that re-states the task-relations feature with its original conventional message, so release-please proposes the v14.2.0 release it should have proposed after #222.
Why this is needed
The #222 promotion was squash-merged with the title
chore(release): promote staging to main for v14.2.0— the squash erased the underlyingfeat(tasks):message, and release-please ignoreschorecommits when computing releases. Its workflow ran successfully and concluded: nothing to release. No release PR, no tag.What happens after this merges
chore: release mainPR proposing v14.2.0 with the task-relations changelog entrypackage.json/ CHANGELOG / manifestv14.2.0,14.2,14,latest)Preventing this permanently
From the next promotion onward, the promotion PR description should carry a
BEGIN_COMMIT_OVERRIDEblock enumerating the underlying conventional commits (release-please reads it instead of the squash title), so every promotion produces a detailed release automatically. This is being added to the team workflow.No file changes — the commit is intentionally empty.
🤖 Generated with Claude Code
BEGIN_COMMIT_OVERRIDE
feat(tasks): add task-to-task relations between work items
END_COMMIT_OVERRIDE