Repository navigation
[JUM-889][Chore] Sync v0.2.15 release into dev - #528
Merged
Merged
Conversation
…524) ## Summary - Promote `dev` → `main` after #523: force-reset stale `chore/release-*` tips + force generated-automation diffs against `main` on CircleCI branch-push (empty-diff / STALE_DATA blockers for unattended `v0.2.15`). ## Problem Statement - Related issue(s): JUM-889 - Related PR(s): #523, #522 ## 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: fix - 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-be9fb69b - 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: promoting #523 fixes so app-release can land v0.2.15 unattended - Target cycle (`Start date` -> `End date`): 2026-09-25 -> 2026-10-27 - Priority group for this PR (`P0` / `P1` / `P2`): P0 - [x] This PR contains tasks from only one priority group. ## Branch Promotion Path (Required) - Source branch: `dev` - Target branch: `main` - [x] The leading `JUM-XXXX` matches the single Linear Issue declared above. - [ ] This task PR targets `dev`. - [x] 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. - [ ] 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`: `5148a101`, `2254de8c` (via #523) ## Scope of Change ### Domain / Business Rules - None ### Application / Use Cases - None ### Adapters / Infrastructure - `ci-cd/create-app-release-tag.js`, `ci-cd/check-generated-automation-pr.js` (already on `dev` via #523) ### API / Contracts (OpenAPI, DTOs, handlers, controllers) - None ## Detailed Technical Changes 1. Release promotion only of #523. 2. Unblocks generated `chore/release-v*` branch-gate empty-diff / stale tip failures. ## Test plan - [x] #523 required CircleCI checks passed - [ ] Required checks on this promotion PR - [ ] After merge: recreate/re-run app-release for `v0.2.15` / merge #522 Made with [Cursor](https://cursor.com)
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_ba60348b-68a4-4ff7-904f-d7a028d31729) |
27 of 30 tasks
web2solutions
added a commit
that referenced
this pull request
Oct 4, 2026
## Summary - Fast-forward `dev` to `main` tip `967f2837` so promote #601, release `v0.3.3`, and changelog sync commits are not stranded on `main` only. - No new product changes; ancestry alignment only (same pattern as #528). ## Problem Statement After `#601` promote and automated release/changelog PRs (`#603`–`#605`), `main` is 6 commits ahead of `dev`, which blocks the next tip promote. - Related issue(s): https://linear.app/jumentix/issue/JUM-916 - Related PR(s): #601, #602, #604 - Related check run(s): pending on this PR ## Project Tracking (Required) - Linear Project: `Jumentix` (`https://linear.app/jumentix`) - Focused epic link: https://linear.app/jumentix/project/epicdocs-jumentix-website-deep-docs-playgrounds-seoai-dae8af894bf6 - Epic milestone: n/a (epic has no open milestones) - Primary task nature: `release` - Epic-delegated agent ID: `cursor` - Child task issue link: https://linear.app/jumentix/issue/JUM-916 - Project Update: reconcile after promote - Linear Project link(s): https://linear.app/jumentix/project/epicdocs-jumentix-website-deep-docs-playgrounds-seoai-dae8af894bf6 - Linear Issue link(s): https://linear.app/jumentix/issue/JUM-916 - Linear Issue ID list (comma separated): JUM-916 - Item status at PR creation: Done (follow-up reconcile) - Target cycle (`Start date` -> `End date`): 2026-10-04 -> 2026-10-04 - Priority group for this PR (`P0` / `P1` / `P2`): P2 - [x] This PR contains tasks from only one priority group. ## Branch Promotion Path (Required) - Source branch: `main` - Target branch: `dev` - Required PR title format: `[JUM-XXXX][Nature] <concise outcome>` - [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] Every linked issue already contains this PR URL. - [x] Every linked issue already contains commit hash/range evidence. - [x] PR description includes mapping of task -> commit(s). - Task -> commit(s) mapping: - `JUM-916`: `8feb7809`..`967f2837` (already on `main`; sync into `dev`) ## Scope of Change ### Domain / Business Rules - None. ### Application / Use Cases - None. ### Adapters / Infrastructure - None (version bumps + changelog already merged on `main`). ### API / Contracts (OpenAPI, DTOs, handlers, controllers) - None. ## Detailed Technical Changes 1. Fast-forward `dev` to include `#601` promote, `v0.3.3` release, and changelog sync commits. ## Architecture and Design Alignment - [x] Domain logic remains inside domain/application layers. - [x] Controllers/handlers do not instantiate repositories/services directly. - [x] Ports/adapters boundaries are respected. - [x] No new circular dependencies introduced. - [x] Event publishing/listening flow remains consistent. ## Security Impact - Security impact: No security impact - Secrets handling reviewed: [x] N/A - Input/output sanitization reviewed: [x] N/A - AuthN/AuthZ impact: [x] No - Data exposure risk (password/salt/token/PII): [x] No - Sonar security findings addressed or unaffected: [x] Yes ## Data and Migration Impact - Data model impact: None - Migration required: [x] No - Rollback strategy: Revert the merge commit on `dev`. ## Breaking Changes None. ## Acceptance Criteria - [x] `dev` tip matches `main` tip after merge. - [x] No new product commits introduced by this PR. - [x] Architecture boundaries remain enforced. - [x] No regression in existing workflows beyond ancestry sync. ## Test Plan (Evidence) - [x] Commits already validated on `main` (promote #601 + release #604 + changelog gates). - [ ] Remaining required checks on this PR (CircleCI) pending. ## Feedback Resolution (Required) - [x] Every GitHub review thread is resolved natively. - [x] Every general comment has a visible resolution response by the PR author or a repository maintainer. - [x] Each resolution response uses exactly one marker and, for `resolved`, a SHA from this PR: ```html <!-- jumentix-pr-feedback: resolved comment=https://github.com/OWNER/REPO/pull/NUMBER#issuecomment-ID commit=PR_COMMIT_SHA --> <!-- jumentix-pr-feedback: invalid comment=https://github.com/OWNER/REPO/pull/NUMBER#issuecomment-ID --> ``` ### Coverage - Project coverage >= 95%: [ ] Yes (pending CI) - Patch coverage >= 95%: [ ] Yes (pending CI) - Codecov status passing: [ ] Yes (pending CI) ### SonarQube Cloud - Quality Gate passing: [ ] Yes (pending CI) - New vulnerabilities introduced: [x] No - New security hotspots reviewed: [x] N/A ## Performance / Reliability Impact No measurable impact. ## Observability - Logs updated: [x] No - Metrics/Tracing updated: [x] N/A ## Deployment and Rollout - Deployment notes: Merge (FF) `main` into `dev`. - Feature flag needed: [x] No - Rollout strategy: Merge when required checks pass. - Rollback steps: Revert merge on `dev`. ## Risks and Mitigations 1. Risk: Local pre-push hit a flaky offlinePersistenceMatrix browser timeout. Mitigation: This PR uses already-green `main` commits; CI on GitHub/CircleCI is the merge gate. ## Documentation Updates - [x] README updated (if needed) — n/a - [x] Additional docs updated (if needed) — n/a - [x] Changelog untouched; GitHub Actions synchronizes it only after the validated `main` merge ## Reviewer Checklist - [x] Changes are clear and scoped. - [x] Acceptance criteria are testable and satisfied. - [x] Tests are sufficient for risk level. - [x] Security and data impacts are addressed. - [ ] CI checks pass fully. Made with [Cursor](https://cursor.com)
This branch was successfully deployed
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.
Summary
devtomaintip after unattendedv0.2.15release (chore(release): v0.2.15 #525), GitHub Release, and changelog sync (chore: synchronize changelog #527).Problem Statement
Project Tracking (Required)
Jumentix(https://linear.app/jumentix)Start date->End date): 2026-09-25 -> 2026-10-27P0/P1/P2): P1Branch Promotion Path (Required)
maindevJUM-XXXXmatches the single Linear Issue declared above.dev.main, it is a release promotion sourced fromdev, references the task PRs/issues already merged intodev, and introduces no unreviewed changes.main.Bidirectional Traceability (Required)
JUM-889:1122076d(chore(release): v0.2.15 #525),5a177a63(chore: synchronize changelog #527),5f7169be([JUM-889][Fix] Promote unattended release branch-gate fixes to main #524)Scope of Change
Domain / Business Rules
Application / Use Cases
Adapters / Infrastructure
dev←main(v0.2.15)API / Contracts (OpenAPI, DTOs, handlers, controllers)
Detailed Technical Changes
devlaggedmainby 3 commits after release + changelog.Test plan
v0.2.15; Release published; dry-runnoop/no-releasable-commitsMade with Cursor