Qiskit / coheriq / 41156597182
93%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 5
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
coverage: 91.525%. Remained the same
41156597182

push

github

web-flow 
Create the GitHub release atomically (#44)

* Create the GitHub release atomically

GitHub now creates releases as immutable, which forbids uploading
assets after publication.  ghalactic/github-release-from-tag
publishes the release and then uploads assets as a separate call, so
the 0.1.0 release was published with no assets and the job failed.
The pypi job depends on it, so 0.1.0 never reached PyPI.

Replace the action with gh release create, which creates a draft,
uploads the assets, and publishes only once they are attached.  A
failure now leaves a deletable draft rather than a published release
that can never be corrected.

Keep pypi downstream of the GitHub release so a PyPI upload, which
cannot be undone, only happens once everything else has succeeded.

Bump the version to 0.1.1, since 0.1.0's PyPI filenames can never be
reused.

Assisted-by: Claude Opus 5

* Set earliest_version so release notes render

The deployed docs build from stable/0.1, where reno found the 0.1.0 tag at
the base of the branch and stopped scanning before collecting any notes.  It
computed an earliest version of 0.0.0, so the stop point and the only content
coincided, and release-notes.html rendered its heading with nothing under it.

Naming 0.1.0 explicitly puts it inside the reported range.  This is the same
setting the other addons carry, each pointing at its own first release.

Assisted-by: Claude Opus 5

270 of 295 relevant lines covered (91.53%)

0.92 hits per line

Jobs
ID Job ID Ran Files Coverage
1 41156597182.1 5
91.53
GitHub Action Run
Source Files on build 41156597182