Skip to content

Set ReleaseVersion for generated notes #1217

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

Merged
merged 1 commit into from
Mar 26, 2020
Merged

Set ReleaseVersion for generated notes #1217

merged 1 commit into from
Mar 26, 2020

Conversation

saschagrunert
Copy link
Member

@saschagrunert saschagrunert commented Mar 26, 2020

What type of PR is this?

/kind bug

What this PR does / why we need it:

We need to set the ReleaseVersion within the JSON for the generated
notes to display them correctly on relnotes.k8s.io.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

/cc @evillgenius75 @JamesLaverack @reylejano-rxm @jluk @puerco

Does this PR introduce a user-facing change?

- Fixed missing `release_version` field in generated `krel release-notes` JSON output

@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/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 26, 2020
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject 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 Mar 26, 2020
@jeefy
Copy link
Member

jeefy commented Mar 26, 2020

/test pull-release-test

@jeefy
Copy link
Member

jeefy commented Mar 26, 2020

This is failing for the same reason that #1180 is failing.

It looks like it tries to pull the latest alpha +1, but the test data is hard coded to v1.19.0-alpha.0

@saschagrunert
Copy link
Member Author

This is failing for the same reason that #1180 is failing.

It looks like it tries to pull the latest alpha +1, but the test data is hard coded to v1.19.0-alpha.0

Here is the fix #1218 😇

We need to set the ReleaseVersion within the JSON for the generated
notes to display them correctly on relnotes.k8s.io.

Signed-off-by: Sascha Grunert <[email protected]>
@jeefy
Copy link
Member

jeefy commented Mar 26, 2020

woot

/lgtm

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jeefy, 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:

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 added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 26, 2020
@k8s-ci-robot k8s-ci-robot merged commit 7d67ab0 into kubernetes:master Mar 26, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone Mar 26, 2020
@saschagrunert saschagrunert deleted the release-version branch March 26, 2020 14:14
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/bug Categorizes issue or PR as related to a bug. 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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants