Skip to content

fix(frontend): replace vendored upstream release history with syncode fork history - #246

Merged
dayartcrew-web merged 1 commit into
masterfrom
fix/release-history-syncode
Aug 18, 2026
Merged

dayartcrew-web merged 1 commit into
masterfrom
fix/release-history-syncode

Conversation

@dayartcrew-web

Copy link
Copy Markdown
Owner

Summary

  • Settings > Release history was rendering the upstream MCode changelog (0.0.29–0.3.0) that came in with the vendored apps/web UI — not this fork's history.
  • Fork versions 0.1.0–0.1.9 collided with upstream entries of the same number, so the post-update dialog and Release history showed upstream feature notes as this app's releases; 0.1.10–0.1.24 were missing entirely.
  • entries.ts now contains exactly the 24 releases this fork has tagged (v0.1.0–v0.1.24, no v0.1.5 — never tagged), authored from each tag's commit range.
  • New entries.test.ts guards provenance: version set must equal the fork's tagged set, no duplicates, newest-first authoring, no upstream branding (mcode/t3code/dpcode) in feature text, every release has ≥1 feature + date.

Test plan

  • npx vitest run src/whatsNew/ — 17/17 pass (5 new guard tests)
  • npx tsc --noEmit — clean
  • Full npm test — 2239 pass; 1 pre-existing wsTransport failure that also fails on clean master (unrelated)
  • Manual: open Settings > Release history in desktop build — shows 0.1.24 (Aug 19) down to 0.1.0 (Jul 21)

… fork history

Settings > Release history rendered the upstream MCode changelog (0.0.29-0.3.0)
vendored with the UI. Fork versions 0.1.0-0.1.9 collided with upstream entries,
showing wrong notes, and 0.1.10-0.1.24 were missing entirely. entries.ts now
contains only releases this fork tagged; entries.test.ts guards provenance,
ordering, uniqueness, and branding.
@dayartcrew-web
dayartcrew-web merged commit 163c44a into master Aug 18, 2026
4 checks passed
@dayartcrew-web
dayartcrew-web deleted the fix/release-history-syncode branch August 18, 2026 20:52
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