docs: write the [1.5.0] changelog section (TRA-1142) - #595
Open
mikestankavich wants to merge 1 commit into
Open
Conversation
`[Unreleased]` was empty against 104 commits since v1.4.1, and TRA-1142's acceptance requires a real `[1.5.0]` section before the tag is cut. Recounted from `git log v1.4.1..main` rather than from the `v1.5.0` label, which turned out to understate the release in two ways: - **The schema moves to 40, not 39.** `000040_users_must_change_password` landed via TRA-1135 (#590), which carried no `v1.5.0` label and was therefore invisible to the label-derived shipping list. TRA-1142 predicted "no migration expected is exactly when a stray one goes unnoticed" and that is what happened. The label has since been added to TRA-1135. - Four other user-visible landings were unlabelled: tag-store batching toward TRA-1150 (#582), BLE write-failure visibility (#583), fragment-reassembly hardening (TRA-1148, #581), and removal of a dead device-name search (#585). TRA-1150 is described as what it is — a main-thread starvation fix that does not close the ticket, which is still Backlog. Claiming the wedge fixed here would be wrong. Dated 2026-08-27; bump it if the tag slips. Refs: TRA-1142
Contributor
|
🚀 Preview Deployment Update ✅ This PR has been successfully merged into the preview branch. The preview environment will update shortly at: https://app.preview.trakrf.id |
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
1 participant
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.
CHANGELOG.md's[Unreleased]section was empty against 104 commits / ~20 PRs sincev1.4.1. TRA-1142's acceptance requires a real[1.5.0]section before the tag is cut, so this writes it.The recount changed the release
I built this from
git log v1.4.1..main, not from thev1.5.0label — TRA-1142 explicitly asks for that ("recount from the platform repo before cutting the tag"). The label understated the release in two ways:The schema moves to 40, not 39.
000040_users_must_change_passwordlanded via TRA-1135 (#590), which carried nov1.5.0label and so was invisible to the label-derived shipping list. TRA-1142's own warning — "'no migration expected' is exactly when a stray one goes unnoticed" — is precisely what happened. I've added the label to TRA-1135 and corrected the release ticket's acceptance criterion.Four other user-visible landings were unlabelled: tag-store batching toward TRA-1150 (#582), BLE write-failure visibility (#583), fragment-reassembly hardening (TRA-1148, #581), and removal of a dead device-name search (#585).
Two deliberate wording choices
Backlog; calling it fixed in a customer-facing changelog would be wrong.Note
Dated
2026-08-27. Bump the date if the tag slips — it's a one-word edit and it's the only thing in here that can go stale.Refs: TRA-1142