Closed vinamra28 closed 1 year ago
Thank you @vinamra28.
If you have release branches in the CLI, the easier is to put those as
name
as they can be updated automatically as new patch releases are created. Also branches allow for doc fixes to end up on the website without the need of a patch release.If you don't use release branches, I would recommend configuring only the latest patch version for each release.
thanks @afrittoli for replying, we do have release branches in CLI but the problem is we have separate release branches for individual patch release. Example v0.26.1 and v0.26.0 are separate branches in CLI 😅
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: AlanGreene
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Changes
As of now the latest version of CLI displayed is v0.23.1 whereas the latest current release is v0.28.0. Updating the sync/config/cli.yaml with the latest releases that were done post v0.23.1
Signed-off-by: vinamra28 jvinamra776@gmail.com
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:
See the contribution guide for more details.