• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ilpanich / axiam-typescript-sdk / 32357708529
94%

Build:
DEFAULT BRANCH: main
Ran 20 Aug 2026 10:12AM UTC
Jobs 1
Files 48
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Aug 2026 10:11AM UTC coverage: 92.547%. Remained the same
32357708529

push

github

web-flow
ci(release): publish axiam-sdk via Trusted Publishing, and cut 1.0.0-alpha31 (#67)

* chore(release): prepare axiam-typescript-sdk 1.0.0-alpha31

1.0.0-alpha29 and 1.0.0-alpha30 were both tagged and both failed to publish:

  npm error You must specify a tag using --tag when publishing a prerelease
  version.

npm >= 11 refuses to publish a prerelease with no dist-tag, and the publish job
upgrades to npm@latest because Trusted Publishing needs >= 11.5.1. Every version
this package ships is a prerelease, so the failure was total — it hit the
pre-publish dry run, before any registry side effect, which is why the registry
still stops at 1.0.0-alpha28.

The fix (085831c) derives the dist-tag from the version and passes it to every
publish call. It landed on main AFTER the v1.0.0-alpha30 tag was cut, so the
tagged tree never had it and the release could not have succeeded. Nothing more
is wrong with the workflow: reproduced locally against npm 12.0.2, the current
tree fails without --tag and publishes as `axiam-sdk@1.0.0-alpha30` with tag
`alpha` when it is passed.

This bump exists so the fix can actually be exercised — a re-cut of alpha30
would re-run the crates.io/docs publishers for a version they have already
released.

No tag is pushed here. Tag v1.0.0-alpha31 once this is on main to publish.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Bru8z9upeUe4iBLaNT5Hvq

* ci(release): say which npm credential the publish will use, before building

Neither npm release has reached `npm publish` yet. alpha29 and alpha30 both
died at the `npm publish --dry-run` gate on the missing prerelease `--tag`, and
the real publish step was SKIPPED both times — so Trusted Publishing has never
actually been exercised, and "the first release with Trusted Publishing failed"
is not yet a claim the logs support.

That matters because the job cannot currently tell you which credential it is
using. setup-node writes `_authT... (continued)

1197 of 1333 branches covered (89.8%)

Branch coverage included in aggregate %.

1895 of 2008 relevant lines covered (94.37%)

436.64 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32357708529.1 20 Aug 2026 10:12AM UTC 48
92.55
GitHub Action Run
Source Files on build 32357708529
  • Tree
  • List 48
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #32357708529
  • 416800c2 on github
  • Prev Build on main (#32346130129)
  • Next Build on main (#32404482282)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc