Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@getnema/adapter-fumadocs@0.2.0

Minor Changes

• abc6d37: New docHref(href, pagePath, basePath?): map corpus-style relative .md
  links (with .//../ segments and #anchors) to canonical rendered
  routes. Page bodies link the way agents read them — relative .md paths —
  and emitting those verbatim in HTML 404s from the docs index and yields
  non-canonical URLs elsewhere. The raw .md/MCP surfaces keep the verbatim
  links (agent parity); only the human-facing HTML rewrites them.

Patch Changes

• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0
  • @getnema/adapter-kit@0.1.2
  • @getnema/core@0.2.1

@getnema/cli@0.5.0

Minor Changes

• 53b99d1: Harden the approval flow after a human approves (Approval actions: promotion survives but the merge step is fragile (auto-merge setting, CI retrigger, post-promote failure) #96): the approval actions
  treat the merge as best-effort — the durable outcome is the promotion, so a
  blocked merge (checks pending, repo auto-merge disabled) is reported in the
  confirmation comment instead of failing the run. nema doctor gains a repo
  auto-merge governance check and the docs spell out the protected-branch
  requirements (NEMA_PROMOTE_TOKEN + "Allow auto-merge").

• e287c2a: Solo-maintainer approval: the /nema approve comment-command (Solo-maintainer deadlock: approval loop assumes PR author ≠ approver, but agent PRs are often authored under the maintainer's own identity #93).

  GitHub forbids review-approving your own pull request, so when an agent
  proposes under the maintainer's identity the review button never appears —
  the solo maintainer could never promote anything. An explicit, permission-
  checked /nema approve comment on the PR is the same human gate, recorded
  honestly:

  • schema: new maintainer-command review method; the draft-pages-not-reviewed
    gate requires it to carry a PR-referencing reviewed transition, exactly like
    github-pr-approval.
  • cli: nema approve --method maintainer-command; nema doctor's
    propose-identity check now recognizes a wired comment-command workflow as a
    valid solo mode instead of warning.
  • create-nema: scaffolded repos ship .github/workflows/nema-approve-command.yml
    out of the box — commenting /nema approve (write/admin only, fork-guarded)
    promotes the PR's draft pages and merges. Zero setup for solo maintainers.

• e287c2a: Bot identity for the propose step — fixes the solo-maintainer deadlock (Solo-maintainer deadlock: approval loop assumes PR author ≠ approver, but agent PRs are often authored under the maintainer's own identity #93).

  The one invariant needs the draft-PR author and the human approver to be different
  forge accounts, because GitHub forbids approving your own pull request. When
  nema open-pr / propose_changes run with the maintainer's own gh auth — the
  default for a solo maintainer driving an agent — the loop deadlocks: nothing can
  ever be promoted.

  • NEMA_PROPOSE_TOKEN (machine-user PAT or GitHub-App installation token): when
    set, propose commits, the branch push, and the PR creation all authenticate as
    the bot, so any human maintainer can approve. NEMA_BOT_NAME / NEMA_BOT_EMAIL
    override the committer identity (default nema-bot).
  • resolveProposeIdentity() / GitHubHost(cwd, { identity }) in the producer;
    the CLI and MCP server pick the env up automatically.
  • nema open-pr prints which identity it proposes with, and warns about the
    deadlock when proposing with the ambient identity.
  • nema doctor gains a propose-identity governance check: warns when no
    NEMA_PROPOSE_TOKEN is set or when it resolves to the same account that
    approves.

Patch Changes

• Updated dependencies [e287c2a]
• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0
  • @getnema/gates@0.5.0
  • @getnema/producer@0.5.0
  • @getnema/mcp@0.4.1
  • @getnema/core@0.2.1
  • @getnema/drift@0.2.1
  • @getnema/provenance@0.1.2

create-nema@0.4.0

Minor Changes

• e287c2a: Solo-maintainer approval: the /nema approve comment-command (Solo-maintainer deadlock: approval loop assumes PR author ≠ approver, but agent PRs are often authored under the maintainer's own identity #93).

  GitHub forbids review-approving your own pull request, so when an agent
  proposes under the maintainer's identity the review button never appears —
  the solo maintainer could never promote anything. An explicit, permission-
  checked /nema approve comment on the PR is the same human gate, recorded
  honestly:

  • schema: new maintainer-command review method; the draft-pages-not-reviewed
    gate requires it to carry a PR-referencing reviewed transition, exactly like
    github-pr-approval.
  • cli: nema approve --method maintainer-command; nema doctor's
    propose-identity check now recognizes a wired comment-command workflow as a
    valid solo mode instead of warning.
  • create-nema: scaffolded repos ship .github/workflows/nema-approve-command.yml
    out of the box — commenting /nema approve (write/admin only, fork-guarded)
    promotes the PR's draft pages and merges. Zero setup for solo maintainers.

@getnema/gates@0.5.0

Minor Changes

• e287c2a: Solo-maintainer approval: the /nema approve comment-command (Solo-maintainer deadlock: approval loop assumes PR author ≠ approver, but agent PRs are often authored under the maintainer's own identity #93).

  GitHub forbids review-approving your own pull request, so when an agent
  proposes under the maintainer's identity the review button never appears —
  the solo maintainer could never promote anything. An explicit, permission-
  checked /nema approve comment on the PR is the same human gate, recorded
  honestly:

  • schema: new maintainer-command review method; the draft-pages-not-reviewed
    gate requires it to carry a PR-referencing reviewed transition, exactly like
    github-pr-approval.
  • cli: nema approve --method maintainer-command; nema doctor's
    propose-identity check now recognizes a wired comment-command workflow as a
    valid solo mode instead of warning.
  • create-nema: scaffolded repos ship .github/workflows/nema-approve-command.yml
    out of the box — commenting /nema approve (write/admin only, fork-guarded)
    promotes the PR's draft pages and merges. Zero setup for solo maintainers.

Patch Changes

• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0
  • @getnema/core@0.2.1
  • @getnema/drift@0.2.1
  • @getnema/provenance@0.1.2

@getnema/producer@0.5.0

Minor Changes

• e287c2a: Bot identity for the propose step — fixes the solo-maintainer deadlock (Solo-maintainer deadlock: approval loop assumes PR author ≠ approver, but agent PRs are often authored under the maintainer's own identity #93).

  The one invariant needs the draft-PR author and the human approver to be different
  forge accounts, because GitHub forbids approving your own pull request. When
  nema open-pr / propose_changes run with the maintainer's own gh auth — the
  default for a solo maintainer driving an agent — the loop deadlocks: nothing can
  ever be promoted.

  • NEMA_PROPOSE_TOKEN (machine-user PAT or GitHub-App installation token): when
    set, propose commits, the branch push, and the PR creation all authenticate as
    the bot, so any human maintainer can approve. NEMA_BOT_NAME / NEMA_BOT_EMAIL
    override the committer identity (default nema-bot).
  • resolveProposeIdentity() / GitHubHost(cwd, { identity }) in the producer;
    the CLI and MCP server pick the env up automatically.
  • nema open-pr prints which identity it proposes with, and warns about the
    deadlock when proposing with the ambient identity.
  • nema doctor gains a propose-identity governance check: warns when no
    NEMA_PROPOSE_TOKEN is set or when it resolves to the same account that
    approves.

Patch Changes

• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0
  • @getnema/gates@0.5.0
  • @getnema/core@0.2.1
  • @getnema/drift@0.2.1
  • @getnema/provenance@0.1.2

@getnema/schema@0.3.0

Minor Changes

• e287c2a: Solo-maintainer approval: the /nema approve comment-command (Solo-maintainer deadlock: approval loop assumes PR author ≠ approver, but agent PRs are often authored under the maintainer's own identity #93).

  GitHub forbids review-approving your own pull request, so when an agent
  proposes under the maintainer's identity the review button never appears —
  the solo maintainer could never promote anything. An explicit, permission-
  checked /nema approve comment on the PR is the same human gate, recorded
  honestly:

  • schema: new maintainer-command review method; the draft-pages-not-reviewed
    gate requires it to carry a PR-referencing reviewed transition, exactly like
    github-pr-approval.
  • cli: nema approve --method maintainer-command; nema doctor's
    propose-identity check now recognizes a wired comment-command workflow as a
    valid solo mode instead of warning.
  • create-nema: scaffolded repos ship .github/workflows/nema-approve-command.yml
    out of the box — commenting /nema approve (write/admin only, fork-guarded)
    promotes the PR's draft pages and merges. Zero setup for solo maintainers.

@getnema/adapter-kit@0.1.2

Patch Changes

• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0
  • @getnema/core@0.2.1

@getnema/core@0.2.1

Patch Changes

• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0

@getnema/drift@0.2.1

Patch Changes

• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0

@getnema/mcp@0.4.1

Patch Changes

• e287c2a: Bot identity for the propose step — fixes the solo-maintainer deadlock (Solo-maintainer deadlock: approval loop assumes PR author ≠ approver, but agent PRs are often authored under the maintainer's own identity #93).

  The one invariant needs the draft-PR author and the human approver to be different
  forge accounts, because GitHub forbids approving your own pull request. When
  nema open-pr / propose_changes run with the maintainer's own gh auth — the
  default for a solo maintainer driving an agent — the loop deadlocks: nothing can
  ever be promoted.

  • NEMA_PROPOSE_TOKEN (machine-user PAT or GitHub-App installation token): when
    set, propose commits, the branch push, and the PR creation all authenticate as
    the bot, so any human maintainer can approve. NEMA_BOT_NAME / NEMA_BOT_EMAIL
    override the committer identity (default nema-bot).
  • resolveProposeIdentity() / GitHubHost(cwd, { identity }) in the producer;
    the CLI and MCP server pick the env up automatically.
  • nema open-pr prints which identity it proposes with, and warns about the
    deadlock when proposing with the ambient identity.
  • nema doctor gains a propose-identity governance check: warns when no
    NEMA_PROPOSE_TOKEN is set or when it resolves to the same account that
    approves.

• Updated dependencies [e287c2a]

• Updated dependencies [e287c2a]

  • @getnema/schema@0.3.0
  • @getnema/gates@0.5.0
  • @getnema/producer@0.5.0
  • @getnema/core@0.2.1
  • @getnema/drift@0.2.1
  • @getnema/provenance@0.1.2

@getnema/provenance@0.1.2

Patch Changes

• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0

@getnema/actions@0.1.6

Patch Changes

• Updated dependencies [e287c2a]
• Updated dependencies [e287c2a]
  • @getnema/schema@0.3.0
  • @getnema/gates@0.5.0
  • @getnema/producer@0.5.0
  • @getnema/core@0.2.1
  • @getnema/provenance@0.1.2

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nema	Ready	Preview, Comment	Jul 21, 2026 8:48am