Correct the v0.4.0 tag targets to current main heads

Browse Source

Why: Backend #195 and Frontend #82 (parallel task feature/project-member-access)
merged after the original targets (Backend 15566f9 / Frontend c294835), and Dev
main 20e086e pins exactly those new heads (5d5fc989/eb2d6d32). Tagging the stale
SHAs would make RDM pins->v0.4.0 a downgrade versus Dev main, so the release must
land on current main HEADs; the checkout origin/main command already does this.

Evidence: SELF rows on the card - four-repo ls-remote (main HEADs recorded, all
v0.4.0 tag refs empty), git ls-tree origin/main pins, and 15566f9../42cda9c0..
commit ranges showing the parallel merges.

Impact: Dev task card release-plan section only; no code or pins change.

Refs: task feature/rdm-increment-settings-duties; related Backend #195,
Frontend #82, Dev #527.

...

This commit is contained in:

weichen

2026-10-13 14:07:33 +00:00

parent 20e086e48b

commit b763e5e1ae

1 changed files with 237 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

.task/feature-rdm-increment-settings-duties.md

+237 -2

File diff suppressed because one or more lines are too long