Repository navigation
Publish the approved package and verify the registry release #11
Description
Blocked until all release gates and final-candidate validation pass and the owner explicitly authorizes npm publication and tag/release creation. Creating this issue is planning only.
- Record explicit owner authorization for package/version and release/tag actions.
- Publish the reviewed artifact using the approved method.
- Clean registry install: verify React/Next usage, CSS exports, ESM/CommonJS and declarations.
- Create authorized GitHub release/tag matching the reviewed commit and release notes.
- Record actual registry/release URLs and support matrix; do not mark done on an attempted publish.
Acceptance: verified registry artifact and matching authorized release/tag. No publication occurs as part of project setup.
References: roadmap, development/acceptance guide.
Beta publication attempt — 2026-10-13
The owner authorized accessibility-plugin-react@2.0.0-beta.1 under beta and ISC. Source cf4348b passed all CI jobs, including 66 unit tests and 55 browser passes (five intentional skips). npm browser authentication completed, but the registry rejected upload with E403 because the maintainer account is temporarily suspended after a recent security-sensitive action. Registry checks confirmed no beta release/tag and latest remains 1.0.0. Publication and clean registry consumer verification remain incomplete. See PR #18 and docs/RELEASE.md for the verified archive and retry procedure.
Version 2 / GitHub Actions follow-up
The owner superseded the beta candidate with 2.0.0/latest and authorized GitHub Actions publishing plus merging PR #17/#18. Both are merged into main at 1d4ab1c. Action 38359604307 passed validation and archive checksum verification, then npm denied upload with E404/permission error. Trusted publisher setup was not saved: CLI returned 403 and browser showed the temporary account suspension. Registry remains 1.0.0/latest. A fresh connection form is filled for prabothcharith/accessibility-react, publish.yml, Allow npm publish, no environment; awaiting owner browser authorization. This issue remains open; no 2.0.0 publication or registry consumer success is claimed.
Activity
prabothcharith commentedon Oct 16, 2026
Publication update — 2026-10-16
The npm trusted-publisher connection was saved and the failed publish job in Action 38359604307 was rerun against the previously validated archive from main commit 1d4ab1c. The checksum check passed and npm accepted accessibility-plugin-react@2.0.0 through OIDC under latest.
The Action's immediate registry check raced npm's publish-time malware scan and returned a temporary 404. After scanning completed, independent verification confirmed:
PR #20 records the publication and hardens Windows/npm-12/registry-propagation validation. No Git tag or GitHub release was created; that checklist item remains separately gated.
prabothcharith commentedon Oct 21, 2026
Completed. accessibility-plugin-react@2.0.2 is published to NPM under latest via automated GitHub Actions OIDC trusted publishing. Registry metadata, package integrity, and live registry consumer tests across React 18, React 19, and Next.js were successfully verified.