Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

First npm release of @bitpin-dev/bitpin-sdk: manual publish + trusted publisher

Open
  • Is something wrong?
#12 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, typescript
Domain
devops, release

Research direction

Read the release workflow release.yml and the CI-built archive bitdev-pin-bitpin-sdk-0.1.1.tgz referenced in the issue. Merge the “release ts 0.1.1” PR, wait for build-ts, then follow the listed npm trusted-publishing and access settings steps. Done when 0.1.1 is published, trusted publishing is configured, the waiting job is rejected, and the old unscoped package is unpublished.

Written by the indexing model from the issue text.

Description

release typescript

The TypeScript SDK is published as @bitpin-dev/bitpin-sdk, a scoped package that belongs to the bitpin-dev npm organization (#20). The release workflow publishes with npm trusted publishing (OIDC, with provenance) from the npm environment; no npm token is stored.

npm can only add a trusted publisher to a package that exists, so the first version is published by hand once:

  • npm organization bitpin-dev, 2FA on
  • GitHub environment npm with required reviewers
  • Merge the "release ts 0.1.1" PR; let build-ts finish and leave publish-ts waiting
  • Publish the CI-built package by hand, as a member of bitpin-dev: npm publish bitpin-dev-bitpin-sdk-0.1.1.tgz --access public
  • npmjs.com → @bitpin-dev/bitpin-sdk → Settings → Trusted publishing → GitHub Actions: bitpin-dev / bitpin-sdk / release.yml / environment npm
  • Settings → Publishing access → "Require two-factor authentication and disallow tokens"
  • Reject the waiting publish-ts job (0.1.1 is already out)
  • Unpublish the old unscoped bitpin-sdk from the personal account: npm unpublish bitpin-sdk --force (allowed within 72 hours of publishing)

After that, every ts-vX.Y.Z release publishes automatically once someone approves the npm environment.

Dominant language
Python
Stars
0
Forks
0
Avg merge
28m
Merged PRs (30d)
20

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bitpin-dev/bitpin-sdk

All issues in bitpin-dev/bitpin-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.