Release v1.11.1+suite.1

Release checklist

• 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-puppet#246
  • cyberark/conjur-oss-suite-release#196

• 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 (with issue links):

  • cyberark/conjur#1953
  • cyberark/conjur-oss-helm-chart#112 - v2.0.2
  • cyberark/conjur-api-go#84 - v0.6.1
  • cyberark/secrets-provider-for-k8s#267 - v1.1.1

• Create a docs issue to add a new OSS suite release.

  Docs issue: cyberark/conjur-docs#1244

• 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
  

  PR link: cyberark/conjur-oss-suite-release#195

• 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 product owner reviews and approves the PR.

• 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.