fix(ci): use https for scm developerConnection#2832
Merged
willosborne merged 1 commit intoJul 16, 2026
Conversation
The maven-release-plugin pushes over the developerConnection URL, which was ssh://github.com/..., but the release workflow only authenticates git operations over HTTPS (via GITHUB_TOKEN url.insteadOf rewrite) and there's no SSH key on the runner. This caused release:prepare to fail at prepare:scm-commit-release with "Permission denied (publickey)".
lbulanti-ms
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The "Release and publish CALM models to Maven Central" workflow fails during
release:prepare(prepare:scm-commit-release) withPermission denied (publickey). See failing run: https://github.com/finos/architecture-as-code/actions/runs/29491469083/job/87598351650Root cause:
maven-release-pluginpushes over the<scm><developerConnection>URL, which wasscm:git:ssh://github.com/finos/architecture-as-code.git. The release workflow only authenticates git operations over HTTPS (checkout withGITHUB_TOKENplus agit config url."https://x-access-token:...@github.com/".insteadOf "https://github.com/"rewrite) — it never sets up an SSH key, so the SSH push fails.Fix: change
developerConnectionto use HTTPS too, so it's covered by the same token-basedinsteadOfrewrite the workflow already sets up.Type of Change
Affected Components
Testing
maven-javadoc-pluginversion fixed in a prior PR resolves cleanly; this change targets the earlierrelease:preparepush failure, one line, well-understood cause)Checklist