ci: add release-drafter workflow
Metadata
Current evaluation
Merged the release-drafter workflow to automate contributor attribution for future releases. Approved by two reviewers and passed CI checks, with one integration test failing but not blocking the merge.
Suggested action: —
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/canonical/snapcraft/blob/main/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `make lint`?
- [ ] Have you successfully run `make test`?
---
Re-adds the release drafter, which should make it easier to get a list of contributors for future releases.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged the release-drafter workflow to automate contributor attribution for future releases. Approved by two reviewers and passed CI checks, with one integration test failing but not blocking the merge. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a CI workflow that reinstates the release drafter, automating contributor list generation for future releases. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a CI workflow that reinstates the release-drafter tool. This automates contributor list generation for future releases, streamlining the release process. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1239 ci: remove release-drafter workflow | rockcraft | merged | Merged. The release-drafter workflow was removed as the publish workflow already overwrites its output, rendering it redundant. Approved and integrated after CI validation. | |
| #369 ci: drop release-drafter workflow | starbase | merged | Merged PR removing the unused release-drafter CI workflow. The automation was redundant as release notes are already generated by the release-publish workflow and maintained in per-repository changelogs. Approved by two reviewers and passed CI checks. | |
| #78 ci: fix release-drafter config | starbase | merged | Merged following reviewer approval and passing CI. The change corrected the release-drafter configuration with a single line update. Integration completed without unresolved review comments. | |
| #3117 ci: setup release-drafter | snapcraft | merged | Merged to configure release-drafter for CI automation. Approved after passing checks, the PR added 43 lines across two files. A reviewer suggested renaming a GitHub section to Tooling, which was adopted. | |
| #2331 ci: remove release drafter workflow | charmcraft | merged | Merged the removal of the release drafter CI workflow, which was no longer used and consistently failing. Approved by two reviewers, the change deletes 16 lines across one file. | |
| #159 ci: remove release-drafter workflow | craft-archives | merged | Merged removal of the release-drafter workflow to align with starbase. Approved by two reviewers with passing CI checks, the change deleted 46 lines across two files. | |
| #375 ci: drop release drafter | craft-store | merged | Merged. Removed the Release Drafter GitHub Actions workflow and configuration files to eliminate inactive automated release note drafting. Approved by two reviewers and passed CI checks. | |
| #5314 ci: remove duplicate release-drafter workflow | snapcraft | merged | Merged removal of a duplicate release-drafter workflow from CI. Approved by two reviewers, the change deletes 16 lines across one file to streamline automation. | |
| #6262 ci: drop release drafter | snapcraft | merged | Merged to remove release drafter workflows per discussion #6253. Approved by two reviewers, the change deletes two CI configuration files and removes 22 lines of code after passing integration and security checks. | |
| #75 ci: update release-drafter file | craft-archives | merged | Merged a fix for a failing release-drafter CI check by renaming the config file from .yaml to .yml, as the tool only accepts .yml. Approved by one reviewer with no coverage impact. Backport to starbase planned. |