xops upstream

Close the loop with
upstream packages.

Change requests live in docs. Fixes ship. Consumers never hear about them. Workarounds stay forever. xops upstream turns that scattered process into a tracked lifecycle.

The lifecycle

From change request
to verified fix.

xops upstream connects a documented change request in your consumer repo to the upstream package fix — and closes the loop with verification proof.

  • 1
    Write the change requestCR or FR documented in the consumer repo as markdown
  • 2
    Submit upstreamxops opens a structured issue on the upstream package repo
  • 3
    Owner ships a fixNew npm version published by the upstream package owner
  • 4
    Pull the fix versionConsumer lockfile updated to the exact fixed version
  • 5
    Verify and closeTests run against original acceptance criteria; verification comment posted as proof
Upstream fixes become traceable instead of scattered.
✓ Bundled in @x12i/ops — no separate plugin install.
full lifecycle
# 0. authenticate (gh auth login or PAT) $ xops upstream auth login ✓ using GitHub token from gh auth # 1. submit from markdown file $ xops upstream submit --file fr.md --package @x12i/ops --repo x12i/npm ✓ Issue #42 opened on x12i/npm # 2. check status $ xops upstream status --id CR-FUNCX-2 ✓ Fix shipped: @upstream/pkg@3.1.2 # 3. pull the fix version $ xops upstream pull-fix --id CR-FUNCX-2 ✓ Lockfile updated to 3.1.2 # 4. verify and close $ xops upstream verify --id CR-FUNCX-2 --comment ✓ Tests pass with 3.1.2 ✓ Verification comment on #147 ✓ Issue closed

CLI surface

All upstream commands.

xops upstream
xops upstream submit --file <path>File CR/FR from markdown (--stdin, --body, --repo supported)
xops upstream auth loginAuthenticate via gh or PAT (status / logout also available)
xops upstream submit --id <id>Open a structured issue on the upstream repo
xops upstream status --id <id>Check whether a fix has shipped
xops upstream pull-fix --id <id>Update lockfile to the exact fixed version
xops upstream verify --id <id>Run tests against original acceptance criteria
xops upstream verify --id <id> --commentPost verification result as a comment on the upstream issue
Planned
xops upstream submit --relayTokenless submit via x12i upstream relay (FR-XNPM-4)