-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Update CHANGELOG.md for 1.18.5, 1.17.12, 1.16.16 #29708
Conversation
CI Results: |
Build Results: |
CHANGELOG.md
Outdated
@@ -6,6 +6,8 @@ | |||
## 1.19.0-rc1 Enterprise |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## 1.19.0-rc1 Enterprise | |
## 1.19.0-rc1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This shouldn't have the Enterprise designation right now.
@@ -6,6 +6,8 @@ | |||
## 1.19.0-rc1 Enterprise | |||
### February 20, 2025 | |||
|
|||
**Enterprise LTS:** Vault Enterprise 1.19 is a [Long-Term Support (LTS)](https://developer.hashicorp.com/vault/docs/enterprise/lts) release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you double check that this verbiage matches the 1.16 verbiage from when it was also released to CE?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The first time we tagged 1.16.x as an LTS was in April 24,2024, for the 1.16.2 minor release so I assumed it was ok to tag at the RC since it was probably due to timing
Description
Update CHANGELOG.md for 1.18.5, 1.17.12, 1.16.16
TODO only if you're a HashiCorp employee
backport/
label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x
, but older release branches will bebackport/ent/x.x.x+ent
.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.