Repository navigation
Conversation
chore(sync): merge next into beta
Validation failure — not validated / keep draftValidated the clean simulated merge of source
The whole failing file passes in isolation using Focused allowed-values 16, validation-bypasses 18, ADM middleware 20 pass. Installation, lint, lockfile, incoming-commit lint, whitespace and dependency integrity checks pass (1093 signatures, 145 attestations). Required next gate: full |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## alpha #526 +/- ##
=======================================
Coverage 84.36% 84.36%
=======================================
Files 278 278
Lines 44189 44189
Branches 6822 6825 +3
=======================================
+ Hits 37278 37281 +3
+ Misses 6809 6806 -3
Partials 102 102 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Validation passed; synchronization completedPR merge CI run 44586288672 passed commitlint, static checks and regression tests. Checkout logs confirm simulated merge PR #526 merged at 2026-11-19T18:45:27Z as |
|
🎉 This PR is included in version 4.27.0-alpha.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Summary
Synchronize existing
betaintoalphaafter #525 merged with source ancestry preserved.beta:aa8a6ebf9643318af43c510741950dea1fa300c0alpha:5058096f7dad2cb015fa34539b85c527d76d1361594c9887e0fe457d5461f40abab7d1bdb105a1e5git cherrylists two unmatched non-merge entries, but the release trigger is empty; these represent one dependency change, not three independent features. No patch-equivalent or squash ambiguity identified. Resulting merge is conflict-free, changing onlypackage.jsonandpackage-lock.json(+5/-5); alpha-specific behavior remains in the merged tree.main → nextandnext → betaare synchronized by ancestry. No other synchronization PR remains open.Evidence
After: isolated merge resolves ADM 4.12.0 with the two-file diff above.
git merge --no-commit --no-ff betaon alpha in an isolated temporary worktree. No release branch pushes, local source edits, or developer-checkout changes.npm ci, lint, lockfile check, commitlint for all three incoming commits, and staged whitespace check pass.npm testpassed OpenAPI 4 and configuration 22; API finished with 1284 passing / 1 failing.Legacy reviewed state on release-track admission → rejects an incomplete staged batch without reviewing its valid companiontimed out after 20000ms inapp/tests/api/release-tracks/reviewed-state.spec.js. Middleware and scheduler were short-circuited by that failure. The entire reviewed-state file passes in isolation (17 tests); separately run middleware (29) and scheduler (15) suites also pass. The timeout cause is unconfirmed, and isolation success does not establish a full-suite pass. No tests changed, skipped, or weakened. Keep this PR draft until the full required checks pass on current tips.Merge Danger
Door: two-way
The dependency update can be reverted; runtime validation and allowed-value choices follow the installed ADM schemas. No migration, endpoint contract, or additional behavior is introduced by this synchronization beyond the existing source change.
Blast Radius: validation
Merge using a merge commit or ancestry-preserving fast-forward. Do not squash or rebase: propagation relies on preserving source ancestry.
Proposed merge message: