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

mpyw / axios-case-converter / 29558582046 / 1
93%
master: 93%

Build:
Build:
LAST BUILD BRANCH: dependabot/github_actions/actions-minor-22cf09a089
DEFAULT BRANCH: master
Ran 17 Jul 2026 05:55AM UTC
Files 4
Run time 1s
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

17 Jul 2026 05:55AM UTC coverage: 93.069%. Remained the same
29558582046.1

Pull #87

github

mpyw
ci: switch release to workflow_dispatch and publish before tagging

Triggering npm publish on GitHub Release creation is an anti-pattern: if the
publish fails, the tag and Release are already finalized. Under GitHub's
Immutable Releases that tag name can never be reused, so a failed publish
burns a version number.

The workflow now runs on workflow_dispatch, publishes to npm first
(prepublishOnly runs the checks/tests), and creates the tag and GitHub
Release only after a successful publish. The version is derived from
package.json.

Ref: https://zenn.dev/yumemi_inc/articles/github-release-not-a-publish-trigger
Pull Request #87: ci: switch release to workflow_dispatch, publish before tagging

88 of 98 branches covered (89.8%)

Branch coverage included in aggregate %.

100 of 104 relevant lines covered (96.15%)

35.81 hits per line

Source Files on job node:24 axios:^1 - 29558582046.1
  • Tree
  • List 4
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 29558582046
  • f16c4024 on github
  • Prev Job for on ci/dispatch-release (#29547406013.3)
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