Skip to content

release(3.10.12): promote to master - #941

Closed
vypbot wants to merge 15 commits into
masterfrom
release/3.10.12
Closed

vypbot wants to merge 15 commits into
masterfrom
release/3.10.12

Conversation

@vypbot

@vypbot vypbot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

🚀 Production promotion

Purpose: accept the prepared change in production.

Origin Prepared source Destination Publication
develop@​5bee5ef release/3.10.12@​b438550 master Package status: not published

Ready before review

  • ✅ Build and release validation
  • ✅ Package smoke test
  • ⏳ Protected-branch checks and reviews

After merge

  • After merge, Copilot will tag and publish the accepted production commit.
  • Development reconciliation: develop.

Compare changes · Release control center

Technical details

Operation eabb56ee-0a42-4bfc-925f-ebe06e4cbc31; strategy production-lineage; merge mode auto.

efraespada and others added 15 commits November 7, 2026 23:30
release(3.10.11): reconcile master into develop
…anged-domus-evaluations: generate bounded complete progress facts (#937)
…a-diagnostic-reason: retain bounded Bugbot response diagnostics (#920)
…a-diagnostic-reason: parse diagnostic documentation on Windows (#920)
…anged-domus-evaluations: bound complete source facts by actual JSON bytes (#937)
…a-diagnostic-reason: fetch the pinned driver through its immutable asset API (#920)
…anged-domus-evaluations: complete prompt delivery before native fixture exit (#937)
…anged-domus-evaluations: prepare reproducible native and generated merge inputs
…anged-domus-evaluations: use reviewed checksum-bound native driver download
…thout-a-diagnostic-reason into bugfix/937-released-acceptance-recovery-exhausts-on-r11-in-three-unchanged-domus-evaluations
…anged-domus-evaluations: diagnose freshness failures and ineligible sync conflicts
…anged-domus-evaluations: wait for canonical catalog read completion
…anged-domus-evaluations: serialize all catalog recovery reads
…covery-exhausts-on-r11-in-three-unchanged-domus-evaluations

Fix bounded progress generation and review recovery diagnostics
@vypbot vypbot linked an issue Nov 8, 2026 that may be closed by this pull request
@docs-page

docs-page Bot commented Nov 8, 2026

Copy link
Copy Markdown

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/copilot~941

Documentation is deployed and generated using docs.page

@vypbot

vypbot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor Author

Copilot approval · Human review needed

Status: This pull request is outside the configured approval scope.
Completed: 1/1 observed checks succeeded; Bugbot complete.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: b43855072e71; base: 0bb87c429030; reason: scope.

@efraespada
efraespada disabled auto-merge November 8, 2026 18:00
@efraespada
efraespada marked this pull request as draft November 8, 2026 18:00
@efraespada
efraespada marked this pull request as ready for review November 8, 2026 18:00
@vypbot

vypbot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor Author

Bugbot: review complete

Current status: No active findings on b438550.

Pull request · Verified commit · Workflow run

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.09%. Comparing base (0bb87c4) to head (b438550).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #941      +/-   ##
==========================================
+ Coverage   96.07%   96.09%   +0.02%     
==========================================
  Files        1519     1526       +7     
  Lines       47247    47472     +225     
  Branches    14699    14772      +73     
==========================================
+ Hits        45391    45618     +227     
+ Misses        698      697       -1     
+ Partials     1158     1157       -1     
Files with missing lines Coverage Δ
src/application/errors/bugbot_freshness_error.ts 100.00% <100.00%> (ø)
src/application/errors/bugbot_mutation_error.ts 100.00% <100.00%> (ø)
...ion/errors/bugbot_verification_response_failure.ts 100.00% <100.00%> (ø)
...tion/policies/application_error_message_catalog.ts 100.00% <ø> (ø)
.../policies/application_error_presentation_policy.ts 100.00% <100.00%> (ø)
...ion/policies/bugbot_literal_verification_policy.ts 100.00% <100.00%> (ø)
...tion/policies/progress_assessment_length_policy.ts 100.00% <ø> (ø)
...ion/policies/progress_compact_assessment_policy.ts 100.00% <100.00%> (ø)
...ication/policies/progress_partition_byte_policy.ts 100.00% <100.00%> (ø)
...ation/policies/progress_partition_length_policy.ts 100.00% <100.00%> (ø)
... and 22 more

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@efraespada

Copy link
Copy Markdown
Member

Publication hold: the macOS platform check failed in recents_center.test.ts while waiting for the first consented future visit. This candidate has not been merged or published, and auto-merge is disabled.

The test race is now reproducible without retries: retain the capture response between native delivery and client permit adoption. The previous helper reports readiness while adoption is still blocked (RED: expected false, received true). Awaiting the existing RecentsClient.refresh() promises keeps readiness pending until adoption completes; the full 12-case integration file passes with the controlled delay. No additional RPC, production behavior, timeout, skip or privacy assertion is introduced.

This promotion is being closed unmerged under the documented unpublished-candidate replacement procedure. Its operation eabb56ee-0a42-4bfc-925f-ebe06e4cbc31, candidate b43855072e715c611b0b23189962a091b45b762c and failed macOS run 42507623565 remain historical evidence. A normal correction on the same Action-managed release/3.10.12 ref will go through complete fresh replacement verification, a new promotion and fresh review/CI/platform/coverage gates before any merge or publication. The version remains 3.10.12 only if npm, the immutable tag and every GitHub Release (including drafts) remain vacant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants