chore: synchronize changelog - #518
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_5ad477d9-c4a5-4bac-8f07-2776f51b35e7) |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_37cfcca3-d74b-457b-99bd-e823e57fb63f) |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_ab7603b9-9081-4fc7-a7bf-2d7e75efea8b) |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #518 +/- ##
=======================================
Coverage 98.12% 98.12%
=======================================
Files 477 477
Lines 15224 15224
Branches 2051 2051
=======================================
Hits 14938 14938
Misses 220 220
Partials 66 66
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
## Summary - Fast-forward `dev` to current `main` tip (`v0.2.14` ancestry + changelog sync #518) — `dev` was 29 commits behind. - Tolerate changelog-sync race in `create-app-release-tag.js`: when `sync-changelog` lands the chore branch first, reuse its tip instead of failing `createCommitOnBranch` on a stale OID (app-release run 36175725849). ## Problem Statement - Related issue(s): JUM-889 - Related PR(s): #516, #517, #518 ## Project Tracking (Required) - Linear Project: `Jumentix` (`https://linear.app/jumentix`) - Focused epic link: https://linear.app/jumentix/project/epicrelease-git-tags-drive-changelog-github-releases-and-npm-publish-1488546fc45e - Epic milestone: First tagged release published — 2026-10-27 - Primary task nature: chore - Epic-delegated agent ID: cursor - Child task issue link: https://linear.app/jumentix/issue/JUM-889/governance-epic-record-first-real-tagreleasepublish-proven-end-to-end - Project Update: https://linear.app/jumentix/project/epicrelease-git-tags-drive-changelog-github-releases-and-npm-publish-1488546fc45e/activity#project-update-dcedc54f-1d24-4df1-a584-f6645fe2ab54 - Linear Project link(s): https://linear.app/jumentix/project/epicrelease-git-tags-drive-changelog-github-releases-and-npm-publish-1488546fc45e - Linear Issue link(s): https://linear.app/jumentix/issue/JUM-889/governance-epic-record-first-real-tagreleasepublish-proven-end-to-end - Linear Issue ID list (comma separated): JUM-889 - Item status at PR creation: reconciling main into dev after v0.2.14 - Target cycle (`Start date` -> `End date`): 2026-09-25 -> 2026-10-27 - Priority group for this PR (`P0` / `P1` / `P2`): P1 - [x] This PR contains tasks from only one priority group. ## Branch Promotion Path (Required) - Source branch: `codex/chore/JUM-889-reconcile-main-into-dev` - Target branch: `dev` - [x] The leading `JUM-XXXX` matches the single Linear Issue declared above. - [x] This task PR targets `dev`. - [ ] If this PR targets `main`, it is a release promotion sourced from `dev`, references the task PRs/issues already merged into `dev`, and introduces no unreviewed changes. - [x] This PR is not a direct task/topic branch promotion to `main`. ## Bidirectional Traceability (Required) - [x] PR description includes mapping of task -> commit(s). - Task -> commit(s) mapping: - `JUM-889`: `cb2f6c28` fix(release): tolerate changelog-sync race after tagging (+ fast-forward of main tip) ## Scope of Change ### Domain / Business Rules - None ### Application / Use Cases - None ### Adapters / Infrastructure - `ci-cd/create-app-release-tag.js` — race-tolerant changelog sync after tag - Branch reconciliation: `dev` ← `main` (`97977fce`) ### API / Contracts (OpenAPI, DTOs, handlers, controllers) - None ## Detailed Technical Changes 1. `dev` lagged `main` by 29 commits after release promotion #517 / changelog #518. 2. After tagging, app-release and sync-changelog both touch `chore/changelog-sync-*`; reuse tip OID on conflict so the workflow stays unattended. ## Test plan - [x] pre-commit `ci:gate:task` green locally - [ ] CCI branch-gate / required checks on this PR - [ ] After merge: `dev` tip matches `main` ancestry for v0.2.14; promote race-fix to `main` if needed Made with [Cursor](https://cursor.com)



Generated changelog sync, opened automatically by the sync-changelog workflow. Drift fix for JUM-862.
Note
Low Risk
Documentation-only changelog alignment with no runtime or application code changes.
Overview
This PR re-synchronizes
CHANGELOG.mdwith git history after the automatedsync-changelogworkflow detected drift (JUM-862).It adds an Unreleased placeholder (
No changes.), introduces av0.2.14 - 2026-09-25section, and records two new entries for JUM-889 unattended release/changelog automation (#516, #517) ahead of the existingchore(release): v0.2.14line.Reviewed by Cursor Bugbot for commit eb6b34c. Bugbot is set up for automated code reviews on this repo. Configure here.