Skip to content

Latest commit

 

History

History
27 lines (15 loc) · 2.01 KB

MAINTENANCE.md

File metadata and controls

27 lines (15 loc) · 2.01 KB
Raw

Maintenance guide

Releasing a new version

See also the internal development notes to learn how to check for and obtain new Venafi client tools versions.

  1. Bump the version number in venafi_codesigning_gitlab_integration/support/version.txt.

  2. Determine the version numbers of the latest 4 Venafi client tools minor versions (see the Image versioning policy). Update the VENAFI_CLIENT_TOOL_VERSIONS specification in .github/workflows/ci-cd.yml accordingly.

  3. Ensure that all these Venafi client tools versions are stored in Azure Blob Storage.

    When uploading, beware of these:

    • Ensure version numbers are removed from filenames.

      • Rename Venafi Code Signing Clients vX.X.X.dmg to Venafi Code Signing Clients.dmg
      • Rename venafi-codesigningclients-X.X.X-linux-x86_64.rpm to venafi-codesigningclients-linux-x86_64.rpm

    • Access tier: Cool.

    • Set the directory equal to the full Venafi client tools version, including patch version. For example: 20.4.0

  4. Ensure the CI is successful.

  5. Manually run the "CI/CD" workflow. Set the create_release parameter to true. Wait until it finishes. This creates a draft release.

  6. Edit the draft release's notes and finalize the release.