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.
Just try for the CI first, if everything will be ok, it will implemented in release job and also for another projects.
This pull request includes several changes to the GitHub Actions workflows and the
pom.xml
file to improve the Maven deployment process. The key updates involve the removal of GPG key installation steps and the renaming of environment variables for better clarity.Changes in GitHub Actions workflows:
.github/workflows/maven_deploy_snapshot.yml
: Removed the steps for installing the GPG secret key and renamed the environment variablesPASSPHRASE
toMAVEN_GPG_PASSPHRASE
and addedMAVEN_GPG_KEY
for better clarity. [1] [2] [3] [4].github/workflows/maven_deploy_snapshot_dev.yml
: Similar to the changes inmaven_deploy_snapshot.yml
, removed the GPG key installation steps and updated environment variables. [1] [2] [3] [4] [5]Changes in
pom.xml
:signer
configuration to the GPG plugin to specify the use of Bouncy Castle (bc
).