Thank you for your reply, Ricardo. I understand that in those PRs all references are pointing to 10.0.0 released artifacts, however it looks to me that the content of the PR itself is a missing artifact of the release and the steps to submit the PRs to those repositories should be added to the release procedure document (and it's fine to have manual steps).
I'd suggest that we incorporate these new artifact(s) - which is the source that will create the PR for the operator repositories - for the next release. On Mon, Dec 16, 2024 at 12:51 PM ricardo zanini fernandes <[email protected]> wrote: > > Hi! Sorry, I missed this email. > > What we do is to use what we already have released to send a PR to those > repos. Nothing is created. For example, the last PRs I opened were for 10.0.0. > We used the artifacts published on our 10.0.0 tag. It's a manual step since > they won't accept bot accounts opening PRs there. > > > > On Thu, Dec 12, 2024 at 7:36 PM Alex Porcelli <[email protected]> wrote: >> >> Hi Ricardo, or anyone knowledgeable about the topic, >> >> I’m seeking clarification regarding the origins of the source content >> for the following PRs: >> >> - https://github.com/k8s-operatorhub/community-operators/pull/5428 >> - >> https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/5632 >> >> From my perspective, it seems that the content of these PRs should >> have been included as part of the release as a dedicated artifact and >> incorporated into the release procedure instructions for submitting >> PRs to the appropriate external repositories. >> >> Could you please confirm if this understanding is correct or provide >> further context on the expected process? >> >> Thank you in advance for your insights! >> >> - >> Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
