-
Notifications
You must be signed in to change notification settings - Fork 2
v1.17.6 suite.1
The next suite version v1.17.6+suite.1 is planned for release in Apr 2021. It was delayed one month due
to a security fork preventing us from releasing cyberark/conjur
.
The target dates are as follows:
- Kick off held Apr 27, 2022.
- Hand off to Technical Writers by May 13, 2022.
- Release by May 20, 2022.
-
Check the Jenkins dashboard to ensure builds are green.
-
If any builds have recently not been green, review the project and determine whether updates are required pre-release.
Components requiring updates pre-suite release (with issue links):
- cyberark/conjur-api-java
- cyberark/cloudfoundry-conjur-buildpack
- cyberark/conjur-service-broker
- cyberark/secretless-broker
- cyberark/secrets-provider-for-k8s
- cyberark/conjur-authn-k8s-client
- cyberark/conjur
- cyberark/summon
- cyberark/summon-aws-secrets
- cyberark/terraform-provider-conjur
-
Review the unreleased changes in the wiki. Determine whether any additional releases will be required before creating a new suite release.
Components requiring releases pre-suite release:
- cyberark/conjur - 1.17.6 (Eric is releasing this Conjur version as part of Enterprise release)
- cyberark/conjur-api-go - 0.10.1
- cyberark/conjur-api-java - 3.0.3
- cyberark/conjur-service-broker - 1.2.5
- cyberark/cloudfoundry-conjur-buildpack - 2.2.4
- cyberark/secretless-broker - 1.7.13
- cyberark/summon - 0.9.3
- cyberark/summon-conjur - 0.6.4
- cyberark/summon-aws-secrets - 0.4.2
- cyberark/secrets-provider-for-k8s - 1.4.3
- cyberark/conjur-authn-k8s-client - 0.23.6
-
Create a docs issue to add a new OSS suite release.
Docs issue: ONYX-17310
-
Create a PR to update the suite.yml to include updated versions. Include a draft of the markdown release notes by running the following command in your release branch:
summon -p keyring.py \ --yaml 'GITHUB_TOKEN: !var github/api_token' \ ./parse-changelogs \ -v {suite release version} \ -t release \ -o RELEASE_NOTES.md
- Conjur product owner reviews and approves the PR. All changes are:
- Complete and usable by users
- Documented
- Conjur product manager reviews the PR and adds "What's new" text in a comment.
- PR is updated to include "What's new" text.
- Conjur maintainer reviews and approves the PR, ensuring the PR checklist is complete for a release.
- Conjur maintainer merges the PR and creates a tag.
- Conjur maintainer copies the HTML release notes from the draft release to the docs issue.
- Technical writers publish the release notes.
- Conjur maintainer publishes the draft GitHub release.