When performing the deploy job through github actions, the deployment piece to sonatype and maven central repo works correctly. However, when the job is wrapping up and maven-scm-plugin attempts to tag the latest commit on master with the new version, the job will fail:
Error: Provider message:
Error: The git-push command failed.
Error: Command output:
Error: Warning:********@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
After some investigation, I tried pushing tags straight from the runner to the repo and it worked fine. It seems to be isolated only to the maven-scm-plugin.
Expected
Maven-scm-plugin should have access to push to repo.
Bug
When performing the deploy job through github actions, the deployment piece to sonatype and maven central repo works correctly. However, when the job is wrapping up and maven-scm-plugin attempts to tag the latest commit on master with the new version, the job will fail:
https://github.com/kgress/scaffold/runs/3748030452?check_suite_focus=true#step:6:685
After some investigation, I tried pushing tags straight from the runner to the repo and it worked fine. It seems to be isolated only to the maven-scm-plugin.
Expected
Maven-scm-plugin should have access to push to repo.
This link might have some useful info. We might need to provide git login info to the pom? https://stackoverflow.com/questions/66944752/how-do-i-push-a-release-to-github-with-the-maven-release-plugin
Workaround
We can push tags manually after every deploy until fixed