Repository navigation
🚀 - 3.10.0 - Release v3.10.0 verification setup and compact comment workflows #665
Description
Release Type
Minor
Release Version
3.10.0
Changelog
-
Centralize native comment verification coordination in a versioned Copilot reusable workflow, keeping repository and generated callbacks compact while preserving same-job setup, native timeouts, exact workflow/Action version binding and cleanup. Preserve reviewed runner placement during upgrade, block unsupported custom bootstrap migration, and document Actions runner 2.336.0+ and reusable-workflow policy requirements (🔧🧑💻 - refactor centralize native comment verification in a reusable workflow #662, chore: centralize comment verification in one reusable workflow #663).
-
Prepare repository verification dependencies with a native, repository-owned composite action. Execute the reviewed trusted-main snapshot before candidate verification, with isolated credentials and native post-step cleanup (✨ - Support repository owned verification setup hooks without editing generated workflows #647, feat: prepare repository verification with native composite actions #652).
-
Generate
.github/actions/copilot-verification-setup/action.ymlonly when absent, preserve existing consumer actions and their auxiliary files, and expose opt-inVERIFICATION_SETUPactivation in the shared web/terminal assistant. Include the starter in npm and document staged upgrades and rollback (✨🧑💻 - Generate verification setup starter preserve consumer actions and expose wizard activation #656, feat(#656): generate verification setup actions and expose wizard activation #657). -
Improve unsupported stored-configuration recovery, actionable SDD ownership diagnostics, companion SDD case/acceptance consistency, and Bugbot finding mutation and duplicate reconciliation diagnostics (🐛🧑💻 - Improve diagnostics and recovery for unsupported PR configuration schemas #635, 🐛🧑💻 - Pre branch SDD ownership analysis fails without an actionable issue diagnostic or clarification card #636, 🐛🧑💻 - bug Bugbot persists a review then fails reconciliation with opaque provider.unavailable #646, 🐛🧑💻 - bug generated companion SDD publishes colliding case IDs and inconsistent acceptance mappings #653, 🐛🧑💻 - Bugbot reconciliation retains an orphan unknown finding alongside duplicate semantic reports #655; PRs fix: diagnose unsupported stored configuration with safe recovery #642, fix: publish actionable SDD ownership diagnostics #650, fix: retain actionable finding mutation diagnostics #651, fix(sdd): validate companion case and acceptance consistency #654, fix: Bugbot reconciliation retains an orphan unknown finding alongside duplicate semantic reports (#655) #658).
-
Forward live merge-queue attestations through release/hotfix publication, stabilize hosted Windows permission-journal coverage, and keep bounded RepoWise analysis available on demand (🐛🧑💻 - bugfix intermittent hosted Windows permission journal test exceeds Jest timeout #577, 📝🧑💻 - Clarify deployment queue syntax and managed AGENTS.md hash scope #637, 🔧 - Run RepoWise only on demand to avoid CI bottlenecks #639, 🐛🧑💻 - Release and hotfix publication callbacks omit live merge queue attestations #643, 🔧🧑💻 - Optimize manual RepoWise analysis and complete bounded dead code and history scans #644; PRs fix: bugfix intermittent hosted Windows permission journal test exceeds Jest timeout (#577) #638, docs: clarify deployment queues and managed pointer hashes #640, chore: run RepoWise only on manual dispatch #641, chore: complete bounded manual RepoWise analysis #645, fix: forward live queue attestations on publication #649).
-
Reject mutually incompatible proposed SDD file paths and distinguish literal configuration-marker mentions from real stored state, preserving existing supported records and human description text (release review release(3.10.0): promote to master #660).
-
Restrict native verification request cleanup to requests created by the validated invocation; clarify the consumer hook versus Copilot coordinator scope (release review release(3.10.0): promote to master #664).
Additional Context
The maintainer explicitly authorized publishing this minor after compact comment coordination, all current-head checks and complete review with no unresolved findings. Encapsulation is implemented by #662/#663 and merged into develop as f5f462b. The official sync into release/3.10.0 passed six verification gates at 4d7906e.
This is a fresh unpublished attempt replacing #661 and promotion #664. Their frozen operation 63381e09-9a3d-440d-aa28-a8efcaa85308 and source identity remain unchanged for audit. The new review found two actionable corrections: native request cleanup must never remove an unvalidated or unowned request file, and the hook SDD must distinguish consumer reusable workflows from the supported Copilot coordinator. Apply and validate these before starting a new preparation. Four other findings were resolved with primary GitHub syntax and existing lifecycle/configuration evidence. No production merge, version tag or npm publication occurred in the previous attempt.
Use the installed Action-owned release branch and official preparation, production PR, protected merge, npm trusted publication, GitHub Release, major Action ref and development reconciliation. Do not manually create/reset/force-push branches or tags, or alter the superseded durable operation. Wait for branch admission before normal contributor commits to the exact canonical ref. Freeze the corrected validated source only after these review corrections. Before merge require all applicable checks and complete current-head review with no unresolved findings. Verify publication identity across accepted production SHA, package.json, immutable v3.10.0 tag, npm version/gitHead, GitHub Release and moving v3 ref; verify registry CLI, setup starter, reconciliation and issue completion.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
[-]Release v3.10.0 verification setup and compact comment workflows[/-][+]🚀 - 3.10.0 - Release v3.10.0 verification setup and compact comment workflows[/+]fix(verification): clean up only owned native requests (#665)
efraespada commentedon Oct 22, 2026
The Action admitted this issue and exposed release/3.10.0. Normal fast-forward commit d33064a now addresses both actionable findings from superseded promotion #664: native request cleanup is gated on validated successful request creation, and the SDD explicitly distinguishes excluded consumer reusable hooks from the supported Copilot-owned coordinator. Three regressions reproduced deletion on the old code and now pass; existing success/failure cases also assert owned request cleanup. All 93 runner/protocol/controller/post tests passed, together with typecheck, lint, specification/catalog generation and validation, documentation/workflow checks, build, reproducible staged build validation and npm package validation. Graphify was updated locally. The previous operation remains unchanged for audit. Start a fresh official preparation only from this corrected candidate, with all current-head platform checks and complete review required before merge.
vypbot commentedon Oct 22, 2026
❌ Release
3.10.0Action required
Managed promotion PR #666 was closed without merge.. Retry after correcting the cause.
What Copilot protected
Production updated: No. Package status: not published.
Progress
develop@f5f462bmasterdevelopflowchart LR D[Source snapshot] --> R[Version prepared] R --> P[Production PR] P --> A[Accepted in production] A --> N[Package and release] N --> B[Development reconciliation] B --> C[Complete]prepared -> production PR -> accepted -> published -> reconciled -> complete
Current transition
release/3.10.0masterLinks
Release control center · release/3.10.0 branch · f5f462b origin commit · d33064a prepared commit · Compare changes · Promotion PR #666
Technical details
c8ac4e53-427a-471b-8ebb-c2577d7a9e7bproduction-lineageauto-merged33064affc66229cae37a27dd8b37dcdd27457f8pendingefraespada commentedon Oct 22, 2026
Superseded by a fresh unpublished attempt after promotion #666 review. Retain the frozen operation and source as audit evidence. The new candidate will preserve Cursor key minimization at the reusable call and clarify the remaining historical SDD sentence before preparation. Nothing has been merged to production or published.