Uh oh!
There was an error while loading. Please reload this page.
[draft tally] v2-2026-07-28 integration branch vs main - #2282
[draft tally] v2-2026-07-28 integration branch vs main#2282felixweinberger wants to merge 1 commit into
Conversation
|
@modelcontextprotocol/client@modelcontextprotocol/codemod@modelcontextprotocol/server@modelcontextprotocol/server-legacy@modelcontextprotocol/express@modelcontextprotocol/fastify@modelcontextprotocol/hono@modelcontextprotocol/nodecommit: |
Mirrors the v1.x-2026-07-28 arrangement: pull_request triggers are unfiltered (PRs targeting the branch already get CI); this adds the branch to the push filters so post-merge state runs CI too.
3d7b726 to
caf5b72Comparefelixweinberger
commented
Jun 12, 2026
Superseded by the proper integration-branch setup: v2-2026-07-28 now starts from main with CI push triggers, and work arrives as reviewed chunk PRs targeting the branch (pull_request CI is unfiltered). No carrier PR needed. |
Standing draft — running tally of the
v2-2026-07-28integration branch vsmain. Not for merging in this form.Work toward the 2026-07-28 (draft) revision accumulates on
v2-2026-07-28via reviewed chunk PRs (e.g. #2281, #2285). This draft exists to:main(size + surface at a glance),main(conflicts, or changes onmainthat break the combined state) surfaces here immediately rather than at the end.When the branch is complete it gets merged to
maineither wholesale or re-sliced into reviewable PRs — decided then. History note: this PR briefly existed as a CI carrier for an earlier wholesale push of the branch; the branch was reset and now grows chunk-by-chunk.