Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publish-release: Support adding release notes from a file #2403

Merged
merged 1 commit into from
Jan 27, 2022

Conversation

puerco
Copy link
Member

@puerco puerco commented Jan 27, 2022

What type of PR is this?

/kind feature

What this PR does / why we need it:

This commit adds a tiny new feature to publish-release. It introduces a new flag to the github subcommand:

--release-notes-file

When pointed to a Markdown file, this flag will read its contents and include it in the default release page template.

It also removes the assets list from the default template as the information is mostly intended for machines and the hashes are already published in the SBOM produced with the release.

Signed-off-by: Adolfo García Veytia (Puerco) [email protected]

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

For a sample of the new release page, check out the v0.2.0 release of bom:
https://github.com/kubernetes-sigs/bom/releases/tag/v0.2.0

Does this PR introduce a user-facing change?

- `publish-release` now supports a new `--release-notes-file` flag. When defined it will read a file and include its contents in a new section on the release page.
- The default template for the GitHub page no longer lists the release assets. The information was redundant as it already listed in the SBOM.

This commit adds a new flag to publish-release:

`--release-notes-file`

When pointed to a Markdown file, this flag will read its contents
and include it in the default release page template.

Signed-off-by: Adolfo García Veytia (Puerco) <[email protected]>
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. needs-priority cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/release-eng Issues or PRs related to the Release Engineering subproject labels Jan 27, 2022
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 27, 2022
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 27, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: puerco, saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [puerco,saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 085f84d into kubernetes:master Jan 27, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.24 milestone Jan 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants