Skip to content

docs(changelog): fold the premature 5.0.0 section back into Unreleased - #1168

Merged
Carme99 merged 1 commit into
mainfrom
w2-clog
Oct 8, 2026
Merged

Carme99 merged 1 commit into
mainfrom
w2-clog

Conversation

@Carme99

@Carme99 Carme99 commented Oct 8, 2026

Copy link
Copy Markdown
Owner

Summary

The 6 Oct session cut a ## [5.0.0] - 2026-10-06 section and bumped the manifests, but no v5.0.0 tag was ever pushed — the dated section misstates history and the [Unreleased] link pointed at a nonexistent tag range. This folds all 131 entries back into Unreleased under one subhead each, rebases [Unreleased] on v4.7.0, and removes the premature AppStream 5.0.0 entry (release.yml asserts top-entry-matches-tag, so leaving it would fail the real cut).

No version literals touched: the manifests stay 5.0.0 as the working version toward the real release.

What changed

  • CHANGELOG.md: 5.0.0 section folded into Unreleased (131 entries verified byte-identical, zero lost/added); subheads merged to Added/Changed/Fixed/Security/Refactor/Test/Docs; [5.0.0] link def deleted; [Unreleased] rebased on v4.7.0
  • com.presencejam.app.metainfo.xml: premature 5.0.0 release entry removed (4.7.0 back on top)
  • tray/mod.rs: correct the try_state lock-free overclaim — it is a short map lookup under one uncontended mutex (tauri-2.11.6 state.rs:108,161)

Tests

  • Entry-preservation proof: old Unreleased+5.0.0 vs new Unreleased, 131 = 131, missing 0 added 0
  • Every ## [X] header has a matching [X]: definition
  • python3 docs/link-audit.py: clean

No v5.0.0 tag was ever pushed, so the dated section misstates history.
131 entries merge under one subhead each (Added/Changed/Fixed/Security/
Refactor/Test/Docs); [Unreleased] rebases on v4.7.0; the 5.0.0 AppStream
entry goes (release.yml asserts top-entry-matches-tag). Also corrects the
try_state lock-free overclaim (Mutex-guarded map lookup).
@Carme99
Carme99 merged commit 11a146c into main Oct 8, 2026
14 checks passed
@Carme99
Carme99 deleted the w2-clog branch October 8, 2026 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant