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

qunitjs / qunit / 9489275739
90%

Build:
DEFAULT BRANCH: main
Ran 12 Jun 2024 08:28PM UTC
Jobs 1
Files 33
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

12 Jun 2024 08:25PM UTC coverage: 58.663%. Remained the same
9489275739

push

github

Krinkle
Build: Remove pushing of release artefact to detached Git commit

For QUnit 1.x and QUnit 2.x, we supported use of QUnit via
Git submodules, where we put the Git tag on a commit that isn't in the
main line, but instead a detached commit that contains the release
artefacts. This is also what Bower built on top of.

These two distribution methods will continue to work for old releases,
but QUnit 3.0 will instead only be canonically published to
code.jquery.com from where it can be downloaded over HTTP and HTTPS
(for setups that prefer something simpler than npm).

This means we don't need a separate "prepare" and "release" commit,
so merge these steps into one, and place the tag on the main branch
commit instead.

This also means we need to do our version field differently. We can:
* Keep "-pre" in Git, but have the release step temporarily remove it
  without including in the tagged commit.
* Change proper version for the release commit, then push another
  commit that changes it back.
* Use the proper version always, and let the build step inject "-dev"
  for non-release builds.

I went with the third option, which seems most conventional in the JS
ecosystem these days to simply leave it at the last release number
between releases.

Ref https://github.com/qunitjs/qunit/issues/1677.

1202 of 2049 relevant lines covered (58.66%)

92.71 hits per line

Jobs
ID Job ID Ran Files Coverage
1 9489275739.1 10 May 56418 07:47AM UTC 0
58.66
GitHub Action Run
Source Files on build 9489275739
Detailed source file information is not available for this build.
  • Back to Repo
  • e9e3ecfd on github
  • Prev Build on main (#9488524390)
  • Next Build on main (#9489451958)
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