Skip to content

merge queue: checking #5 on main (3099cf8) - #7

Closed
mergify[bot] wants to merge 10 commits into
mainfrom
mergify/merge-queue/1206b9df40
Closed

mergify[bot] wants to merge 10 commits into
mainfrom
mergify/merge-queue/1206b9df40

Conversation

@mergify

@mergify mergify Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch enjoyed-confit-qiosye of the default queue, to test #5 before it merges into main. Pushing to this branch or closing this pull request removes #5 from the queue.

What this draft tests

Mergify checks that #5 still passes CI on top of main. CI runs on this draft's code, built in this order:

  1. main at 3099cf8
  2. #5, the pull request of this batch

This is attempt 2: the checks of an earlier draft of this batch failed, and Mergify runs them again. The earlier drafts are listed below.

⏳ Where it stands: being checked

CI is running on this draft.

Waiting for

  • check-success = checks / check

Follow the default queue in the dashboard

What happens next

  • Once the checks pass and every merge condition is met, Mergify merges #5 into main and closes this draft.
  • If a check fails, Mergify removes #5 from the queue and closes this draft.

Retried after failed checks (1 previous attempt):

  • #6 (attempt 1)
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 3099cf8cffd055201543fd0d841a18c5450e170f
previous_check_retries:
  - attempt: 1
    batch_pr_head_sha: bbc7a187807646d09fac3e3ff0029d5defa57a03
    batch_pr_number: 6
    draft_pr_head_sha: bbc7a187807646d09fac3e3ff0029d5defa57a03
    draft_pr_number: 6
previous_failed_batches: []
pull_requests:
  - number: 5
    scopes: []
queue_base_sha: 3099cf8cffd055201543fd0d841a18c5450e170f
scopes: []
...
Required conditions of queue rule default for merge
  • check-success = checks / check
Required conditions to stay in the queue

systemfsoftware-maker and others added 10 commits November 20, 2026 19:41
…orkflow

- Scoped package name, workspace-member layout, flake, release caller, and the enrollment order for the owner.
…e/drizzle-pg-extras

- The release tooling lists workspace members and drops the root package, so the package moves to packages/drizzle-pg-extras under a private root.
- Rename to @systemfsoftware/drizzle-pg-extras; the CLI bin stays drizzle-pg-extras and runtime identifiers are unchanged.
- Pin pnpm 12.9.0, the version the flake provides, and regenerate the lockfile with it.
- Derive VERSION from the package manifest so a release edits no source file.
- Run attw, publint and the rc install inside the member; let ci.yml be dispatched.
- packages.<system>.workspace-tarballs lists the scoped package; the dev shell provides Node 24 and pnpm 12.
… publishing

- Caller pins the shared release workflow by commit SHA, with ci.yml dispatched on the release PR branch and npm-publish on.
- release.jsonc and a change-intent directory supply what the workflow reads from a caller.
- pnpm 12.9, the version the flake pins, resolves the `rc` tag to 1.0.0-rc.5-ab785fc, an older snapshot build that fails the drizzle-kit snapshot-chain tests; pnpm 12.21 resolved 1.0.0-rc.5.
- Installing the exact version keeps the job on the release candidate the suite was written against.
- The approval gate requires the R0 line verbatim as the first entry under Requirements; no other text changed.
- The approval gate requires the standard R0 wording verbatim; the interim issue-reference sentence is dropped rather than moved, because the issue id and person name must not appear in this public repository.
@mergify mergify Bot closed this Nov 20, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1206b9df40 branch November 20, 2026 23:51
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.

1 participant