Having the versions.go file aligned between v4.2.x and v4.5.x series is required for the migration process from v4.2 to v4.5.
What does this PR do?
This commit includes the latest release of CaaSP v4.2.x series in
versions.go file. This is required to let skuba compute a full and
precise migration path from v4.2.x to v4.5.x.
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:
link to other PRs that should be merged together
link to packages that should be released together
upstream issues
Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
2 approvals:
1 developer: code is fine
1 QA: QA is fine
there is a PR for updating documentation (or a statement that this is not needed)
Why is this PR needed?
Having the
versions.gofile aligned between v4.2.x and v4.5.x series is required for the migration process from v4.2 to v4.5.What does this PR do?
This commit includes the latest release of CaaSP v4.2.x series in versions.go file. This is required to let skuba compute a full and precise migration path from v4.2.x to v4.5.x.
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug. If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:
Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp. At the time of creating the issue, this PR can be work in progress (set its title to [WIP]), but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises: