-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release automation broken on this repository? #11
Comments
Yes, the automatic-releases is broken in plenty of those components which were created after the initial introduction of the automatic-releases. I have no idea if I do not have sufficient permissions or sth. like this but it seems that the secrets needed to access the API is not available for some components. Sadly the error reporting of automatic-releases is not really clear about the "why". Asserting stuff is good for the happy-path but in case a problem occurs, it gives exactly no information about the problem itself. Thats why I was not able to fix that problem but I could narrow it down to the place where the github release is actually created. Maybe the github release does not allow empty release description or sth. like this, but I have no idea without proper error reporting. |
Hmm, the organization secrets are not overridden here: same permissions as everything else.
We could raise logging verbosity (needs ejecting of the reusable workflow, while we try it). I had similar issues in Roave/DocbookTool#232 Practically, we set the Ref: https://github.com/laminas/automatic-releases/blob/f01e2555db36adfa0ba743b299dcd60d32394e80/src/Environment/EnvironmentVariables.php#L70 |
Whatever it was, it was resolved. |
Bug Report
Summary
See https://github.com/laminas/laminas-cache-storage-adapter-benchmark/actions/runs/3655683449/jobs/6177279507
Apparently, our release automation is failing to create a release:
Branch switching also didn't work.
The text was updated successfully, but these errors were encountered: