-
Task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Future Sustainability
-
2
-
False
-
-
False
-
Not Selected
-
NEW
-
NEW
-
If Release Note Needed, Set a Value
-
-
Context
When a LO upstream release happens it will trigger automatically operator-publish-operator-hub.yml [1] this inherently will use operator-reusable-hub-release.yml [2] which will actually do the heavy lifting. Somewhere in 2025 Grafana changed how we fetched credentials in GH Actions and this broke this workflow. The goal of this issue is to fix it.
[1] https://github.com/grafana/loki/blob/main/.github/workflows/operator-publish-operator-hub.yml
[2] https://github.com/grafana/loki/blob/main/.github/workflows/operator-reusable-hub-release.yml
Acceptance Criteria
- After a release the automation will create the publish PRs on the respective repos
Developer notes
- I would give a try to inherit secrets since that's where we are currently failing "Secret APP_ID is required, but not provided while calling. Secret APP_PRIVATE_KEY is required, but not provided while calling."