Skip to content

change(ci): Updated release pipeline#1008

Open
eddie-knight wants to merge 2 commits into
mainfrom
grcli-release-pipeline
Open

change(ci): Updated release pipeline#1008
eddie-knight wants to merge 2 commits into
mainfrom
grcli-release-pipeline

Conversation

@eddie-knight
Copy link
Copy Markdown
Collaborator

@eddie-knight eddie-knight commented May 21, 2026

This change set allows us to publish releases to https://grc.store in addition to the GH releases page.

This is a first step — the PR was already getting big so I decided not to go through and bring every catalog into compliance with the latest schema.

This disables the website updates due to the change in artifact shape. We should update that pipeline in a dedicated PR.

Test run: https://github.com/finos/common-cloud-controls/actions/runs/26257290484
Result: https://grc.store/search/finos-ccc/ccc.objstor.cp

I left a whole bunch of claude ultrareview comments inside the PR so that it is clear where we need to make follow-up PRs. I will be drafting those as soon as we merge this in.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 21, 2026

Deploy Preview for common-cloud-controls canceled.

Name Link
🔨 Latest commit afcf707
🔍 Latest deploy log https://app.netlify.com/projects/common-cloud-controls/deploys/6a0fd9d749bf190008a99dac

Signed-off-by: Eddie Knight <knight@linux.com>
@eddie-knight eddie-knight changed the title Updated release pipeline change(ci): Updated release pipeline May 21, 2026
@finos finos deleted a comment from linux-foundation-easycla Bot May 21, 2026
@eddie-knight eddie-knight force-pushed the grcli-release-pipeline branch from 8507e18 to fc81f45 Compare May 21, 2026 22:58
Signed-off-by: Eddie Knight <knight@linux.com>
@eddie-knight eddie-knight marked this pull request as ready for review May 22, 2026 04:38
@eddie-knight eddie-knight requested review from a team as code owners May 22, 2026 04:38
@eddie-knight
Copy link
Copy Markdown
Collaborator Author

I pinged @TheJuanAndOnly99 for guidance on the failing check. It can be safely ignored for now.

Copy link
Copy Markdown
Contributor

@sshiells-scottlogic sshiells-scottlogic left a comment

Choose a reason for hiding this comment

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

Looks good as far as I can tell

Copy link
Copy Markdown
Member

@robmoffat robmoffat left a comment

Choose a reason for hiding this comment

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

One further improvement I would like to see is that this should run automaticatically as well as workflow dispatch.

i.e.

  • Build the catalogs.
  • Compare (perhaps just the IDs) to previous versions
  • If there is changed content, perform the release automatically.

That would mean we complete #993 too

"description": "Global/common capability IDs"
"pattern": "^CCC\\.Core\\..+$",
"description": "Global/common capability IDs (CP## or F## during migration)"
},
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.

can we not pull in these schema files from Gemara now?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Yes we could achieve the vetting strictly through the CUE schema, but @sshiells-scottlogic requested that we persist the IDE support via jsonschema

grcli validate -f "$ARTIFACT" --spec /tmp/gemara-spec

# Create a GitHub release
- name: Create GitHub Release
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.

we need to create the GitHub release too

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

draft: false
prerelease: true
# NEW publishing step: push the typed catalog to grc.store.
- name: Publish to grc.store
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.

Who or what owns grc.store? Are we creating a new link to a proprietary service here?

Is this infra owned by OpenSSF?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

That's all built and maintained by me at the moment. It'll unlock several capabilities in addition to what we have from the current GitHub release flow — especially valuable is the grcli pull ... command which will allow anyone to fetch official immutable release artifacts and vet provenance in a single command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants