Skip to content

MANUAL RUN: npm trusted publishing for the @rustybuns packages #662

Closed as not planned

Description

@QuinnsCode

.github/workflows/npm-publish.yml (from #650) publishes with npm trusted publishing, so no npm token lives anywhere. npm has to be told to trust that workflow, which needs your npm login:

For each of @rustybuns/ports, @rustybuns/shell-bun, @rustybuns/native, @rustybuns/cli on npmjs.com → package → Settings → Trusted Publisher → GitHub Actions:

  • Organization or user: QuinnsCode
  • Repository: RustyBuns
  • Workflow filename: npm-publish.yml
  • Environment: npm

Then, once the next release has gone out from CI (push tag v<version>), set each package's "Publishing access" to Require two-factor authentication and disallow tokens, so a laptop token can't publish any more.

Check: the version page on npmjs.com shows the provenance badge linking to the run.

Activity

  1. added
    manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it
    on Oct 11, 2026
  2. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Tracked in #609, the one hands-on checklist. The steps here still apply; tick them there.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions