chore(release): authenticate git pushes with deploy key#5
Open
alexb-splunk wants to merge 1 commit into
Open
Conversation
c900dbb to
5f69e3d
Compare
Use the protected pypi environment's SSH key for release commits and tags while retaining GITHUB_TOKEN for GitHub release API operations. Keep changelog entries focused on commits that affect versioning.
5f69e3d to
89d8bf0
Compare
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
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.
Summary
RELEASE_DEPLOY_KEYenvironment secretGH_TOKENfor GitHub API operations while using SSH for release commit and tag pushesValidation
git diff --checkpyproject.tomlwith Pythontomllibactions/checkout@v7supports thessh-keyinputuv run tox -e lint,formatRelease procedure
The Main ruleset now allows Deploy keys to bypass with Always allow. Merging this PR will trigger a fresh release workflow; approve the
pypienvironment deployment to publish v1.1.0.The previously failed workflow should not be rerun because it uses the old workflow definition.