-
Review this repo:
- [x] Determine whether improvements can be made to update/modernize the release process
- [x] Review README and CONTRIBUTING to determine if either documentation set is missing impo…
-
There is a standard for how GitHub tags and releases are done in component projects
-
Between suite releases a component may move from 1.3.4 to 1.5.7.
The combined changelog should take into account all the changes between 1.3.4 and 1.5.7
-
If the repo has a changelog that doesn't meet the standard, do try to change earlier entries to match the standard.
If the repo doesn't have a changelog use this as a starter:
```
# Changelog
All …
-
- There is a failing builds dashboard for suite release components that we can check as we’re preparing to do a suite release
- In particular, there is a view of projects that have had a failing build…
-
We need to add automated end-to-end tests for Conjur OSS, but our e2e automation system is bloated and likely running many redundant tests.
Draft requirements (may be revised):
- Tests run in a reali…
-
The conjur quick-start (the way we have our users spin up conjur env) doesn't have the latest additions from Conjur (the Conjur logs) and therefore, the formatting is not correct. Which means we might…
-
**Phase One: Initial Release**
Given a list of GitHub repositories and corresponding tagged versions (you can use the list from [here](https://github.com/cyberark/conjur/blob/c8a037a77e9baa8ebdd1252a…
-
Based on the template provided by the TWs in cyberark/conjur-docs#717, enable outputting the suite release notes in the documentation format and automatically submitting a PR to the docs repo with the…
-
When attempted to deploy the helm chart, got an error about the deployment version.
```
C:\Users\username\Downloads>C:\Users\username\Downloads\helm-v3.0.2-windows-amd64\windows-amd64\helm.exe in…