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

Prepare 1.3.5 #4015

Merged
merged 3 commits into from
May 20, 2024
Merged

Prepare 1.3.5 #4015

merged 3 commits into from
May 20, 2024

Conversation

missylbytes
Copy link
Contributor

Changes proposed in this PR

Prepare release for 1.3.5 (https://github.com/hashicorp/engineering-docs/blob/main/consul/consul-k8s/release-process.md#prepare-the-point-release-branch)

How I've tested this PR

How I expect reviewers to test this PR

Checklist

@missylbytes missylbytes added pr/no-changelog PR does not need a corresponding .changelog entry pr/no-backport signals that a PR will not contain a backport label labels May 20, 2024
@@ -4,7 +4,7 @@
apiVersion: v2
name: consul
version: 1.3.5
appVersion: 1.17.5
appVersion: 1.17.3
Copy link
Member

Choose a reason for hiding this comment

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

This was a little confusing for me because there is a v1.17.4 tag of hashicorp/consul; however, it seems this is because we didn't have our tag naming conventions in place at the time.

v1.17.3 is the latest patch release available on homebrew and dockerhub, so I believe this is correct.

@missylbytes missylbytes merged commit 3071e41 into release/1.3.5 May 20, 2024
30 of 56 checks passed
@missylbytes missylbytes deleted the prepare-1.3.5 branch May 20, 2024 21:20
@nathancoleman nathancoleman mentioned this pull request May 20, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-backport signals that a PR will not contain a backport label pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants