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

danger / danger-pr-comment / 42512820935
100%

Build:
DEFAULT BRANCH: main
Ran 08 Nov 2026 07:01PM UTC
Jobs 1
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

08 Nov 2026 07:00PM UTC coverage: 100.0%. Remained the same
42512820935

push

github

web-flow
Migrate release automation to ruby-gem-release (#15)

## Summary

Use the published `ruby-gem-release` gem pinned to `0.4.0` and its
reusable workflow pinned to `@v0.4.0`. The standard workflow handles
version selection, changelog validation, duplicate checks, publication,
atomic pushes, GitHub releases, and the next development iteration.

Custom code is limited to workflow-reference updates in the
README/installer/specs and the existing `RELEASERS` authorization gate.
There are no custom release tasks or workflow command overrides.

## Removed

Replace the bespoke release workflow and `scripts/release_version.rb`
with the library, removing custom version/changelog handling, HTTP
duplicate checks, empty-note parsing, publication/bump callbacks, and
their redundant tests. Keep only three project-specific tests:
workflow-reference updates, missing/duplicate reference rejection, and
leaving references unchanged when library changelog preparation fails.
Version selection, changelog formatting, and library validation are
covered upstream, not retested here. Remove the version-ordering
restriction: older unpublished maintenance versions are allowed, while
existing tags and RubyGems versions remain rejected.

## Follow-up: replace RELEASERS with protected-environment approval

**AI note on behalf of @dblock:** Later replace `RELEASERS` and its
authorization/actor-matching gates with protected-environment approval:
repository writers can edit the variable, so it is not an independent
security boundary. After protection is enabled, remove the custom gates
and variable. Other writers may dispatch, but only a maintainer may
approve publication.

Run as a repository admin to require approval from `numbata` or
`dblock`, allowing self-approval and retaining the existing `main`-only
policy:

```sh
gh api -X PUT repos/numbata/danger-pr-comment/environments/release --input - <<"JSON"
{
  "reviewers": [{"type": "User", "id": 82400}, {"type": "User", "id": 542335}],
  ... (continued)

20 of 20 relevant lines covered (100.0%)

8.3 hits per line

Jobs
ID Job ID Ran Files Coverage
1 42512820935.1 08 Nov 2026 07:01PM UTC 2
100.0
GitHub Action Run
Source Files on build 42512820935
  • Tree
  • List 2
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #42512820935
  • 497e46ab on github
  • Prev Build on main (#42377370360)
  • Next Build on main (#42689231083)
  • 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