NVIDIA / nodewright / 33219469703
82%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 59
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: 82.599% (+0.2%) from 82.365%
33219469703

push

github

web-flow 
fix(changelog): promote RELEASE_NOTES.md's Unreleased heading on a release cut (#550)

Every hand-authored release note is written under `## Unreleased`, and nothing
renamed that heading to the version being cut. The release workflows extract the
human-authored body by matching a heading that is exactly `## <tag>`, so
`## Unreleased` matched nothing and the notes were dropped. An empty match is
indistinguishable from the common, legitimate case of a release with no
hand-authored notes, so the miss stayed silent for months.

gen-changelog.sh now promotes `## Unreleased` to `## <component>/vX.Y.Z - <date>`
when cutting a release and opens a fresh empty `## Unreleased` above it. The notes
path comes from the existing component-to-path case, so the CLI's irregular
operator/cmd/cli path is handled without a third spelling. An empty block promotes
to nothing, and an existing section for the target version is left alone.

A patch only promotes when HEAD is the matching release/vX.Y.x. Unlike
CHANGELOG.md, which is sourced from the release-branch range, the notes are read
from the working tree: on the release branch that is exactly the cherry-picks the
patch ships, on main it is the next minor's notes. Cutting a patch from anywhere
else regenerates the CHANGELOG as normal and leaves RELEASE_NOTES.md untouched
with a warning naming the branch to re-run from.

release-tag.sh warns before the create-tag confirm when Unreleased still holds
content and no section exists for the tag. Finals only, since an RC is tagged
mid-stabilization before the cut that promotes the heading. Its bump menu now
previews the resulting version the way gen-changelog.sh's already did.

Backfills the stranded notes, attributed by ancestor-checking each blame commit
against the component's release tags rather than by date: operator/v0.18.0 and
operator/v0.17.0, chart/v0.18.0, cli/v0.3.0. Two operator entries post-date the
release/v0.18.x cut and correctly stay under Unreleased. The alrea... (continued)

9180 of 11114 relevant lines covered (82.6%)

7.64 hits per line

Coverage Regressions

Lines Coverage ∆ File
18
79.35
 1.22% operator/internal/controller/skyhook_controller.go
13
91.05
 0.66% operator/cmd/cli/app/node/node_status.go
8
97.16
 0.0% operator/api/nodewright/v1alpha1/nodewright_types.go
2
89.34
 0.03% operator/internal/wrapper/node.go
Jobs
ID Job ID Ran Files Coverage
1 33219469703.1 59
82.6
 GitHub Action Run
Source Files on build 33219469703