ops: npm package @fairdatasociety/fds is 3 major versions behind git (0.2.3 vs v1.1.1) #1

Activity

1. plur9 commented on Jun 20, 2026

   

   plur9

   on Jun 20, 2026

   MemberAuthor

   More actions

   Publish workflow — ready to add via GitHub UI

   The npm gap can be closed with a one-time manual publish + a workflow to automate future releases.

   Step 1 — Manual publish of v1.1.1 (one-time, requires npm org access):

   git clone https://github.com/fairDataSociety/fds-ts.git && cd fds-ts
   npm ci
   npm publish --access public   # needs npm token with @fairdatasociety org write access

   Step 2 — Add publish workflow (GitHub UI, 2 minutes):

   1. Go to: https://github.com/fairDataSociety/fds-ts/new/main?filename=.github/workflows/publish.yml
   2. Paste the content below
   3. Commit directly to main
   4. Add NPM_TOKEN secret at: https://github.com/fairDataSociety/fds-ts/settings/secrets/actions

   Workflow content:

   name: Publish to npm
   
   on:
     push:
       tags:
         - 'v*'
   
   jobs:
     publish:
       runs-on: ubuntu-latest
       permissions:
         contents: read
       steps:
         - uses: actions/checkout@v4
   
         - uses: actions/setup-node@v4
           with:
             node-version: '20.x'
             registry-url: 'https://registry.npmjs.org'
   
         - run: npm ci
   
         - run: npm publish --access public
           env:
             NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

   After adding the workflow: create a v1.1.1 tag to trigger the first automated publish, or do the manual publish in Step 1 first and then tag future releases.

   NPM_TOKEN setup: generate a token at npmjs.com → Access Tokens → Automation token with write access to @fairdatasociety org scope.
2. plur9

   added

   bugSomething isn't workingSomething isn't working

   priority:highBroken functionality affecting usersBroken functionality affecting users

   on Jun 26, 2026
3. miles-on-nightshift

   added a commit that references this issue on Jul 3, 2026

   ci: add npm publish workflow for v* tag pushes

   ...

   52b8ddc
4. plur9 commented on Jul 3, 2026

   

   plur9

   on Jul 3, 2026

   MemberAuthor

   More actions

   Progress update — publish workflow added

   Commit 52b8ddc adds .github/workflows/publish.yml:

   • Triggers automatically on any v* tag push
   • Also has a manual dispatch button (Actions → Publish to npm → Run workflow) for immediate use

   One remaining step (2 min, human action required):

   Add an NPM_TOKEN org/repo secret:

   1. Go to npmjs.com → Access Tokens → Generate New Token → Automation type
   2. Copy the token
   3. Go to https://github.com/fairDataSociety/fds-ts/settings/secrets/actions
   4. Click New repository secret → Name: NPM_TOKEN → paste token

   To publish v1.1.1 immediately after adding the secret:

   • Actions tab → "Publish to npm" → "Run workflow" → Run
   • Or: no new tag needed since v1.1.1 already exists on git

   This closes the 3-version gap (npm=v0.2.3 → v1.1.1) and unblocks FDS-ID external adoption.
5. plur9 commented on Jul 4, 2026

   

   plur9

   on Jul 4, 2026

   MemberAuthor

   More actions

   Status update (2026-07-04): publish.yml workflow is now live (added Jun 28 via PR #3). Tag v1.1.1 already exists on the remote.

   Since the tag already exists, re-pushing it won't trigger the workflow. Use workflow_dispatch instead:

   Step 1 — Add NPM_TOKEN secret at github.com/fairDataSociety/fds-ts/settings/secrets/actions

   • Generate an Automation token at npmjs.com → Access Tokens with write access to @fairdatasociety org

   Step 2 — Trigger the publish workflow:

   gh workflow run publish.yml --repo fairDataSociety/fds-ts --ref v1.1.1

   This will build and publish @fairdatasociety/fds@1.1.1 to npm. After it succeeds, future releases auto-publish when any v* tag is pushed.
6. plur9 commented on Jul 8, 2026

   

   plur9

   on Jul 8, 2026

   MemberAuthor

   More actions

   Status update (2026-07-08, T+4d):

   npm still shows @fairdatasociety/fds@0.2.3 — confirmed via npm view @fairdatasociety/fds version. The publish.yml workflow (added 2026-06-28, commit 52b8ddc) has never run — no workflow runs in history.

   The gap blocks the standard install path for FDS-ID external adopters. Two-step fix:

   Step 1 — Add NPM_TOKEN secret (1 min):

   1. Generate an Automation token at npmjs.com → Access Tokens with publish rights to @fairdatasociety org scope
   2. Add it at: https://github.com/fairDataSociety/fds-ts/settings/secrets/actions → New repository secret → Name: NPM_TOKEN

   Step 2 — Trigger the publish (30 sec):

   gh workflow run publish.yml --repo fairDataSociety/fds-ts --ref main

   Or: Actions tab → "Publish to npm" → "Run workflow" → main branch → Run.

   This publishes v1.1.1 to npm and closes the 3-version gap. Future releases auto-publish on v* tag push.
7. miles-on-nightshift commented on Aug 30, 2026

   

   miles-on-nightshift

   on Aug 30, 2026

   Collaborator

   More actions

   Status update (2026-08-30, T+53d from last check):

   npm still shows @fairdatasociety/fds@0.2.3 — confirmed via npm view @fairdatasociety/fds version. The publish.yml workflow has zero runs in history since it was added in June. Latest git tag is v1.1.1 (2026-06-27).

   The 3-version gap (npm=v0.2.3, git=v1.1.1) continues to block the standard install path for FDS-ID external adopters.

   Two-step fix (same as prior comments):

   Step 1 — Add NPM_TOKEN secret (1 min):

   1. Generate an Automation token at npmjs.com → Access Tokens with publish rights to @fairdatasociety org scope
   2. Add at: https://github.com/fairDataSociety/fds-ts/settings/secrets/actions → New repository secret → Name: NPM_TOKEN

   Step 2 — Trigger publish (30 sec):

   gh workflow run publish.yml --repo fairDataSociety/fds-ts --ref main

   Or: Actions tab → "Publish to npm" → Run workflow.

   🤖 CTO heartbeat 2026-08-30