There are guidelines and tools for releasing artifacts to separate suite components

[izgeri]

GIVEN I am releasing suite component A
AND the release of suite component A produces an artifact A1
AND the artifact A1 must be uploaded to suite component B on release of suite component A
THEN there are Jenkins pipeline and/or GitHub action utilities that can copy the component A pipeline-built artifact A1 to a folder on a branch of component B
AND there is a Jenkins pipeline and/or GitHub action utility to open a PR to merge the branch including artifact A1 into the main branch of component B

Said plainly, there are tools I can use so that if my project's pipeline produces a ZIP or a brew .rb file, I can use my pipeline to upload the ZIP or .rb file to a separate GitHub repo (like our helm chart repository or homebrew cask) in a new pull request.

In order for this to be useful, the outcome of this card should be some examples and documentation that others may follow.

[izgeri]

Note - this may be accomplished by having component B watch for new releases of component A, and then modifying itself as appropriate. A GitHub action would work well to do this for OSS projects.