Skip to content

CMP-4603: Require compliance-sdk by its release tag v0.1.1 - #1356

Merged
Vincent056 merged 1 commit into
ComplianceAsCode:masterfrom
Vincent056:cmp-4603-sdk-tag
Aug 25, 2026
Merged

CMP-4603: Require compliance-sdk by its release tag v0.1.1#1356
Vincent056 merged 1 commit into
ComplianceAsCode:masterfrom
Vincent056:cmp-4603-sdk-tag

Conversation

@Vincent056

Copy link
Copy Markdown

compliance-sdk now has real releases: v0.1.0 is the exact commit this repo pinned as a pseudo-version, and v0.1.1 adds the Go 1.25.11 directive to match this repo. Requiring the tag ends the dependence on branch-head reachability that broke consumers when the sdk's main history was rewritten (today's stackrox go mod tidy incident — mitigated short-term by an archive tag at the orphaned commit).

Vendored source is byte-identical (same commit); the diff is version markers only (go.mod / go.sum / vendor/modules.txt, 5 lines).

(This was meant to ride #1351 but that merged first — re-landed on fresh master.)

🤖 Generated with Claude Code

@openshift-ci-robot

Copy link
Copy Markdown
Collaborator

@Vincent056: This pull request references CMP-4603 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "5.1.0." or "openshift-5.1.0.", but it targets "compliance-operator-1.10.0" instead.

Details

In response to this:

compliance-sdk now has real releases: v0.1.0 is the exact commit this repo pinned as a pseudo-version, and v0.1.1 adds the Go 1.25.11 directive to match this repo. Requiring the tag ends the dependence on branch-head reachability that broke consumers when the sdk's main history was rewritten (today's stackrox go mod tidy incident — mitigated short-term by an archive tag at the orphaned commit).

Vendored source is byte-identical (same commit); the diff is version markers only (go.mod / go.sum / vendor/modules.txt, 5 lines).

(This was meant to ride #1351 but that merged first — re-landed on fresh master.)

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
openshift-ci Bot requested a review from vickeybrown August 18, 2026 17:03
@github-actions

Copy link
Copy Markdown

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:1356-41cd7a877bcc5612ec44c151f7c793e0d85b9e8b

@openshift-ci

openshift-ci Bot commented Aug 19, 2026

Copy link
Copy Markdown

@guzalv: changing LGTM is restricted to collaborators

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

compliance-sdk now has real releases: v0.1.0 is the exact commit this
repo pinned as a pseudo-version, and v0.1.1 adds the Go 1.25.11
directive to match this repo. Requiring the tag ends the dependence on
branch-head reachability that broke consumers when the sdk's main
history was rewritten - tags are immutable once published.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:1356-1f82503360e3447edf85a71d4b5ce139c7f2a06b

@yuumasato

Copy link
Copy Markdown
Member

/test e2e-aws-serial

@yuumasato yuumasato left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
Just pending CI

@openshift-ci

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guzalv, Vincent056, yuumasato

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [Vincent056,yuumasato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Vincent056
Vincent056 merged commit f86698d into ComplianceAsCode:master Aug 25, 2026
16 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants