Skip to content

Use per-vendor release note details#3099

Merged
DRSDavidSoft merged 1 commit into
cmderdev:masterfrom
DRSDavidSoft:codex/vendor-per-vendor-details
Jun 30, 2026
Merged

Use per-vendor release note details#3099
DRSDavidSoft merged 1 commit into
cmderdev:masterfrom
DRSDavidSoft:codex/vendor-per-vendor-details

Conversation

@DRSDavidSoft

@DRSDavidSoft DRSDavidSoft commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Change generated vendor update PR release notes from one large collapsible block to one collapsible <details> block per updated vendor.
  • Add a GitHub release shield per vendor in the update table.
  • Put the compare link at the end of each vendor release-note blockquote as "View full changes".
  • Apply 👆 Dependencies and 🗃️ Vendor labels to generated vendor update PRs.

Label check

  • 👆 Dependencies already exists and is already used by Dependabot.
  • 🔄️ GitHub Actions already exists and is already used by Dependabot.
  • Created 🗃️ Vendor (#0366d6) for vendored dependency update PRs.

Validation

  • git diff --check
  • Executed the updated PR-body generation logic locally against the ⬆️ Update 4 vendored dependencies #3093 version set and verified it emits four vendor-specific <details> blocks, four GitHub release shields, and four final blockquoted compare links.

@DRSDavidSoft DRSDavidSoft force-pushed the codex/vendor-per-vendor-details branch from 9b03d40 to e8d62b2 Compare June 30, 2026 21:40
@DRSDavidSoft DRSDavidSoft force-pushed the codex/vendor-per-vendor-details branch from e8d62b2 to 2d6a20e Compare June 30, 2026 21:41
@DRSDavidSoft DRSDavidSoft merged commit e2ff95d into cmderdev:master Jun 30, 2026
1 check passed
@DRSDavidSoft DRSDavidSoft deleted the codex/vendor-per-vendor-details branch June 30, 2026 21:48
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