Update plugin org.ajoberstar.git-publish to v5 #222
Merged
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.
This PR contains the following updates:
4.2.2
->5.1.0
Release Notes
ajoberstar/gradle-git-publish (org.ajoberstar.git-publish)
v5.1.0
Compare Source
Resolves some regressions discovered by @marcphilipp.
Most notably, with Grgit removed any authentication methods you previously used such as
GRGIT_USER
or-Dorg.ajoberstar.grgit.auth.username
won't work in v5. This version adds new options to replace them.Breaking Changes
None
Enhancements
username
andpassword
properties toGitPublication
for cases where credentials are needed (via #116)Fixes
fetchDepth
when the project is in a shallow clone (via #116)Deprecations
None
Compatibility
Tested on the following version:
v5.0.0
Compare Source
Major change to reimplement using the Git CLI. The prior versions used grgit, which is deprecated and not necessary for the functionality of this plugin.
Using the Git CLI reduces use of further dependencies and increases compatibility with different Git features that JGit (which grgit wrapped) struggled with.
Since 5.0.0-beta.2: Unchanged
Since 5.0.0-beta.1: suppressed some of the noisy output and attempted a fix for #112 by using
objects/info/alternates
to reference the project's checkout repo rather than a full remote.Breaking Changes
GitPublishPush
will reportUP_TO_DATE
instead ofSKIPPED
if there aren't any commits to push upEnhancements
None
Fixes
objects/info/alternates
) which should avoid issues with lightweight checkouts (see #112)gitPublishReset
Deprecations
None
Compatibility
Tested on the following version:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.