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

cmaurer / relative.time.parser / 20628242378
80%

Build:
DEFAULT BRANCH: master
Ran 31 Dec 2025 10:23PM UTC
Jobs 3
Files 2
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

31 Dec 2025 10:23PM UTC coverage: 80.0%. Remained the same
20628242378

push

github

web-flow
fix: updating build artifacts (#33)

* feat: add semantic-release for automated versioning and publishing

- Add semantic-release with changelog and git plugins
- Configure releases on master (full) and feature/* branches (prerelease)
- Update GitHub Actions to run semantic-release after successful builds
- Remove unused blanket.js coverage tool (replaced by nyc)
- Update Gruntfile to remove blanket dependency

Semantic-release will:
- Analyze commits to determine version bump
- Update package.json with new version
- Generate/update CHANGELOG.md
- Create GitHub release with release notes
- Publish to npm

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix:
- adding test for invalid regex
- removing unused files

* fix: updating

* feat(ci): add separate prerelease stage for non-master branches

- Split release job into 'release' (master only) and 'prerelease' (all other branches)
- Update .releaserc.json to support any branch as prerelease with wildcard pattern
- Prerelease versions use branch name as identifier (e.g., 1.2.0-feature-foo.1)
- Prereleases published to 'next' npm channel

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: updating

* fix: updating

* feat(ci): add pre-release stage for feature branches

- Add pre-release job that runs on feature/* branches (not master)
- Update .releaserc.json to specifically match feature/* branches
- Prereleases strip 'feature/' prefix from version identifier
- Example: feature/foo creates 1.2.0-foo.1 on 'next' npm channel

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: updating

* fix: updating

* fix: updating

* fix: updating releaserc

* fix: updating build artifacts

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

11 of 18 branches covered (61.11%)

Branch coverage included in aggregate %.

33 of 37 relevant lines covered (89.19%)

51.08 hits per line

Jobs
ID Job ID Ran Files Coverage
1 node-20.x - 20628242378.1 31 Dec 2025 10:23PM UTC 2
80.0
GitHub Action Run
2 node-18.x - 20628242378.2 31 Dec 2025 10:23PM UTC 2
80.0
GitHub Action Run
3 node-22.x - 20628242378.3 31 Dec 2025 10:23PM UTC 2
80.0
GitHub Action Run
Source Files on build 20628242378
  • Tree
  • List 2
  • 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 #20628242378
  • cdd7f023 on github
  • Prev Build on master (#20627922274)
  • Next Build on master (#20628301965)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc