v0.10.7

• fix(validators): check object GVK in bundle service account validator (#161)

v0.10.6: Add Service Account Config to Scorecard (#153)

• Add Service Account Config to Scorecard (#153)
• feat: add new validator to only check the usage of deprecate apis (#156)
• Modified the controller-runtime and controller-tools versions (#154)
• Add validation for Kind and APIVersion (#152)
• Add Timestamp to Scorecard Test Results (#137)
• fix: Fix check to verify OCP label versions when it is =v4.x (#148)
• Add maxOpenShiftVersion test for parsing full version string (#147)
• Warn on maxOpenShiftVersion specifying more than major.minor (#146)
• feat: bump k8s to v0.22.0 (#145)

v0.10.5

Validate SA names do not match csv deployment spec (#144)

OLM is unable to properly handle the case where a bundle author
explicitly adds a hardcoded reference to a service account with a name
that matches the name of the service account defined by the deployment
spec in the CSV. This commit adds a validation method to ensure that the
name of the service account in a bundle does not match
deployment.Spec.Template.Spec.ServiceAccountName in the csv's spec

v0.10.4

Add openapi markers for csv (#141)

v0.10.3

Merge pull request #139 from jchunkins/add_conditions

Add conditions to catalog source

v0.10.2

Add ResolutionFailed condition type for subscription #138
Add storage spec to scorecard config #135

v0.10.1

Add conditions array to OperatorGroup v1 status #133
Add validation to CSV name length #134

v0.6.2

OperatorCondition cherry-pick v0.6.x (#132)

* Expand validation to annotations

- Add validation function for well known case sensitive annotation names
- Use new validation function in CSV and OperatorGroups
- Add minimal OperatorGroup validator calling new function
- Add / update unit tests and test data
- update usage readme

Signed-off-by: John Hunkins <jhunkins@us.ibm.com>

* Add conditions array to OperatorCondition's spec

The conditions array in the spec is now available for operator to
create/update as the operator progresses through installation
process. As the spec is updated, the object generation will be
incremented and it can be used for tracking object changes.

Signed-off-by: Vu Dinh <vudinh@outlook.com>

* Add OperatorCondition v2 with spec.conditions array

Signed-off-by: Vu Dinh <vudinh@outlook.com>

* Add ConditionType to v2 api

Signed-off-by: Vu Dinh <vudinh@outlook.com>

* Regen go-bindata for crd changes for OperatorCondition

Signed-off-by: Vu Dinh <vudinh@outlook.com>

Co-authored-by: John Hunkins <jhunkins@us.ibm.com>

v0.10.0

• chore: bump k8s to 1.21 (#130)
• Introduce verify github action (#127)
• Update generated deepcopy (#128)

v0.9.2

Regen go-bindata for crd changes for OperatorCondition