gfx-rs/wgpu

`CHANGELOG` check in CI doesn't check for deleted release sections

Open

#9245 opened on Mar 16, 2026

View on GitHub
 (2 comments) (0 reactions) (2 assignees)Rust (9,290 stars) (703 forks)batch import
area: infrastructuregood first issuetype: bug

Description

Deleting an entire released section has no consequences with the current CHANGELOG check, i.e.:

 ## Unreleased
 
 hay sup

-## Release 2
-
-later suckers
-
 ## Release 1
 
 - i'm freeeee

It's unlikely to pass review, but it'd be nice to plug this gap.

Contributor guide

Tech stack
rustgithub actions
Domain
ci cddeveloper experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
CI workflow syntaxCHANGELOG format
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine the existing CI workflow files in .github/workflows/ (likely ci.yml) and the CHANGELOG validation script. The script currently checks for unreleased sections but does not detect when a released section is deleted. Identify the regex or logic used to parse the CHANGELOG and modify it to also flag deletions of release entries. Check the issue comments for any maintainer guidance. Add a test case that demonstrates a deleted release section being caught.