Skip to content

merge queue: checking unstable (581bde1) and #1210 together - #1220

Closed
mergify[bot] wants to merge 3 commits into
unstablefrom
mergify/merge-queue/6780ad5b58
Closed

merge queue: checking unstable (581bde1) and #1210 together#1220
mergify[bot] wants to merge 3 commits into
unstablefrom
mergify/merge-queue/6780ad5b58

Conversation

@mergify

@mergify mergify Bot commented Aug 5, 2026

Copy link
Copy Markdown

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch unstable (581bde1) and #1210 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #1210.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 581bde12afe91557210d3a5e8cf11d6a9cab8115
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1210
    scopes: []
scopes: []
...

shane-moore and others added 3 commits August 3, 2026 17:04
Docs merged to unstable went live at anchor.sigmaprime.io before any
released binary had the documented flags, and each release window
advertised download URLs that 404 until the release was published.
Deploy on release publish instead, serialize deploys under a constant
concurrency group, and fix the arch-less Linux download example that the
version-sync regex was mangling.

Closes #1209
Cap npm ci, Playwright install, and the GitHub stats fetch at 10 minutes
so a hang fails the job before the S3 sync instead of holding the
docs-deploy concurrency group for the 6h default. No job-level timeout
on purpose: it could cancel the sync mid-run.
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

Your PR title doesn't follow the Conventional Commit guidelines.

Example of valid titles:

  • feat: add new user login
  • fix: correct button size
  • docs: update README

Usage:

  • feat: Introduces a new feature
  • fix: Patches a bug
  • chore: General maintenance tasks or updates
  • test: Adding new tests or modifying existing tests
  • perf: Performance improvements
  • refactor: Changes to improve code structure
  • docs: Documentation updates
  • ci: Changes to CI/CD configurations
  • revert: Reverts a previously merged PR

Breaking Changes

Breaking changes are noted by using an exclamation mark. For example:

  • feat!: changed the API
  • chore(node)!: Removed unused public function

Help

For more information, follow the guidelines here: https://www.conventionalcommits.org/en/v1.0.0/

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.82%. Comparing base (581bde1) to head (cf62b6a).

Additional details and impacted files
@@            Coverage Diff            @@
##           unstable    #1220   +/-   ##
=========================================
  Coverage     64.82%   64.82%           
=========================================
  Files           163      163           
  Lines         27785    27785           
=========================================
  Hits          18013    18013           
  Misses         9772     9772           
Flag Coverage Δ
rust 64.82% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mergify mergify Bot closed this Aug 5, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/6780ad5b58 branch August 5, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants