Skip to content

docs: add minor merge and release skill - #3038

Open
Saad Najmi (Saadnajmi) wants to merge 12 commits into
microsoft:0.87-mergefrom
Saadnajmi:release-stack-merge-skill
Open

Saad Najmi (Saadnajmi) wants to merge 12 commits into
microsoft:0.87-mergefrom
Saadnajmi:release-stack-merge-skill

Conversation

@Saadnajmi

@Saadnajmi Saad Najmi (Saadnajmi) commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Current release stack

Documentation alongside #3037. Keep the release process aligned with #3098.

Validation and backups

The branch-specific repaired source passed hardened immutable installation, constraints, and its complete release-helper selection. The selected 18-head packet records 1,406 passing helper tests. Exact source-tree equivalence is used for rewritten endpoints where applicable; the two changed linear RC checkpoints were tested separately.

Native/API evidence retains its recorded scope. The SwiftPM and RNTester repairs have six focused native build passes. Public stable versions and runtime/API contents were preserved except for the independently reviewed SwiftPM destination repair where applicable.

Public-registry lock correction passed all 18 hosted generation, hardened immutable, constraints, and metadata-audit jobs in run 35769816507. Only equivalent executable-path spelling changes are permitted; dependency versions, checksums, and ranges are unchanged. The previous functional test results remain applicable to this metadata-only correction. Fresh GitHub CI and review remain required. Previous heads are preserved on the same repository under backup/pre-ci-repair-20260922/<original-branch> and backup/pre-public-registry-20260922/<original-branch>; local complete-history bundles were verified as well.

The 0.87 PR sequence is one first-parent path: #3037#3104#3105#3106#3100#3101#3107. The redundant #3102/#3103 reviews are consolidated into #3105.

This section supersedes earlier stack order, source identity, and validation-status notes below.


Summary

  • Adds the repository merge-minor command and registration stub.
  • Captures the topology, conflict-provenance, Jujutsu/Git, validation, evidence, and publication lessons from preparing the 0.84–0.87 stack.
  • Treats prepared merge/release branches as recreatable baselines: this skill PR will evolve as the stack is reviewed, edited, rebased, and re-judged.

Scope

  • .ai/commands/merge-minor.md — canonical operational instructions
  • .claude/commands/merge-minor.md — command registration stub
  • .ai/index.md — command index

Review workflow

This draft is based on 0.87-merge so changes learned while reviewing earlier stack branches can be layered here. Keep it draft until the stack review/rebase cycle is complete.

Validation

  • Independent planner/executor/judge PASS
  • Prettier and git diff --check pass
  • Referenced repository scripts and documentation paths verified

Final CI follow-up

This branch receives only these independently reviewed follow-up paths:

  • .github/workflows/microsoft-npm-publish.yml
  • .github/workflows/microsoft-pr.yml
  • packages/react-native/ReactNativeApi.d.ts
  • packages/react-native/scripts/ios-prebuild/__tests__/hermes-test.js
  • packages/react-native/scripts/ios-prebuild/__tests__/hermes-version-test.js

The complete 16-head batch passed 92 recorded validation commands, including branch-specific API revalidation/generated TypeScript, full formatting checks, and combined targeted suites where applicable. Native changes are limited to the reviewed #3033 destination guards (also present in stable 0.85) and #3104's sidecar-copy correction (already present in its descendants). Exact source equivalence preserves earlier native results elsewhere. The public-registry lockfiles and package manifests remain byte-identical.

Previous heads are backed up at backup/pre-ci-followup-20260922/<original-branch> on their source repository. Fresh current-head CI remains required. The one-first-parent 0.87 sequence is preserved.

Flow/lint closeout

This branch receives the reviewed Flow annotation/test-fixture or duplicate Jest mapper correction. Full Flow, ESLint, and format checks pass; generator output/runtime AST or effective Jest mapper behavior remain equivalent as applicable. Public-registry locks, package manifests, and API declarations remain unchanged. Backups are verified under backup/pre-flow-lint-20260922/<original-branch>. The single first-parent PR path is preserved; current-head CI remains the final acceptance gate.

@Saadnajmi
Saad Najmi (Saadnajmi) marked this pull request as ready for review July 29, 2026 21:10
@Saadnajmi
Saad Najmi (Saadnajmi) requested a review from a team as a code owner July 29, 2026 21:10
Document fork, stable, stack recreation, and focused extraction workflows with strict topology, validation, evidence, and publication guards.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Preserve validated per-branch source and corrected stack dependencies.
Preserve package versions and the linear stack; change only equivalent executable-path metadata.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.
Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.

This branch has not been deployed

No deployments
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