Skip to content

Publish acture-a11y: create the npm name and set its trusted publisher (needs your npm login) #76

Open

Description

@thorwhalen

Part of #70 (steps 1-2 are in #75). The owner's decision on #70 was to publish acture-a11y.

Do not merge the "chore(release): version packages" PR until both steps below are done: the release job would try to publish a name that does not exist on npm yet and fail (same pattern as #65).

  1. First publish by hand (a new name cannot use trusted publishing until it exists). In a tw session, from a checkout of this repo after a11y: make acture-a11y publishable (#70 steps 1-2) #75 is merged and the build is done:
    npm login --auth-type=web
    cd packages/a11y && npm publish --access public
    
  2. Register the trusted publisher on the package's settings page: https://www.npmjs.com/package/acture-a11y/access (Trusted Publisher section: GitHub Actions, repository i2mint/acture, workflow release.yml).

Then merge the Version Packages PR. Done when npm view acture-a11y version returns a version and the release run is green.

Activity

  1. added
    manual-taskRequires the repo owner at the keyboard — agent cannot proceed on its own.
    on Oct 30, 2026
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-taskRequires the repo owner at the keyboard — agent cannot proceed on its own.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions