Skip to content

[codex] Ensure dependencies label exists for release notes#1740

Draft
jeffspahr wants to merge 2 commits intokagent-dev:mainfrom
jeffspahr:codex/release-label-backfill
Draft

[codex] Ensure dependencies label exists for release notes#1740
jeffspahr wants to merge 2 commits intokagent-dev:mainfrom
jeffspahr:codex/release-label-backfill

Conversation

@jeffspahr
Copy link
Copy Markdown
Contributor

@jeffspahr jeffspahr commented Apr 23, 2026

Summary

  • ensure the repository-level dependencies label exists when release-note config changes land on main
  • keep the fix in repo code so it runs with maintainer-owned GITHUB_TOKEN permissions
  • remove the earlier open-PR backfill sweep from this PR

Why

GitHub is already using .github/release.yml for release note categorization, but the repository does not currently have a dependencies label. That leaves Dependabot PRs uncategorized, so they continue to fall into Other Changes.

This PR addresses only that missing prerequisite. It does not relabel existing PRs.

Impact

After merge, the workflow will create the dependencies label if it is missing. Once that label exists, future Dependabot PRs configured by .github/dependabot.yml can populate the Dependencies section in generated release notes.

Validation

  • node --test .github/scripts/release-label-backfill.test.mjs
  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release-label-backfill.yml"); puts "workflow yaml ok"'

Signed-off-by: Jeff Spahr <spahrj@gmail.com>
Signed-off-by: Jeff Spahr <spahrj@gmail.com>
@jeffspahr jeffspahr changed the title [codex] Backfill release labels after merge [codex] Ensure dependencies label exists for release notes Apr 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant