Skip to content

ci: automate secure npm releases - #13

Merged
Upd4ting merged 4 commits into
mainfrom
ci/secure-release-workflow
Sep 2, 2026
Merged

ci: automate secure npm releases#13
Upd4ting merged 4 commits into
mainfrom
ci/secure-release-workflow

Conversation

@Upd4ting

@Upd4ting Upd4ting commented Sep 2, 2026

Copy link
Copy Markdown
Member

Summary

  • add a manual latest/next release workflow using release-it and npm Trusted Publishing
  • harden CI with pinned actions, Node 24, frozen installs, and conventional PR titles
  • enable npm provenance and skip token-based npm prechecks for OIDC
  • run the interface unit suite directly with Mocha, avoiding the active core provider that currently makes the test harness ambiguous
  • include unit and package-consumer tests in every release

Validation

  • 75 unit tests passed
  • package-consumer tarball test passed
  • release-it stable dry-run proposed 0.0.13 with npm tag latest
  • release-it next dry-run proposed 0.0.13-next.0 with npm tag next
  • workflow YAML and release configuration parsed successfully

No package was published.

@Upd4ting
Upd4ting merged commit 335cf52 into main Sep 2, 2026
2 checks passed
@Upd4ting
Upd4ting deleted the ci/secure-release-workflow branch September 2, 2026 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant