[go: up one dir, main page]

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

Release v1.7.0 #4050

Merged
merged 1 commit into from
Jun 2, 2022
Merged

Release v1.7.0 #4050

merged 1 commit into from
Jun 2, 2022

Conversation

realshuting
Copy link
Member

Signed-off-by: ShutingZhao shuting@nirmata.com

Release v1.7.0.

Signed-off-by: ShutingZhao <shuting@nirmata.com>
@realshuting realshuting enabled auto-merge (squash) June 2, 2022 10:52
@realshuting realshuting merged commit 704dc46 into kyverno:release-1.7 Jun 2, 2022
@@ -1,8 +1,8 @@
apiVersion: v2
type: application
name: kyverno-policies
version: v2.4.0-rc3
appVersion: v1.7.0-rc3
version: v2.4.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@realshuting, why, when tagging a Kyverno release, are we also modifying the kyverno-policies Helm chart? The "kyverno" Helm chart I understand, but these are just the PSS policies which have not been changed in a while.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The kyverno-policies chart has both version (chart version) and appVersion, I think it would be clear to bump both versions when there's a new release, and it would be less confusing if both versions were consistent with the chart kyverno.

If we only bump version here, the user would see v2.4.0 with appVersion 1.6.x which indirectly indicates the policies chart only works for Kyverno 1.6.x.

@realshuting realshuting deleted the release-1.7 branch June 28, 2022 07:41
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.

4 participants