OmniLayer / OmniJ

OmniLayer for Java, JVM, and Android
Apache License 2.0
133 stars 89 forks source link

Bump org.ajoberstar.git-publish from 2.1.3 to 4.2.0 #240

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps org.ajoberstar.git-publish from 2.1.3 to 4.2.0.

Release notes

Sourced from org.ajoberstar.git-publish's releases.

4.2.0

Adds support for shallow clones, via the fetchDepth property on publications.

Breaking Changes

None

Enhancements

  • #57 Support shallow clones

Fixes

None

Deprecations

None

Compatibility

Tested on the following version:

Java Version Gradle Versions
11 7.0.2, 7.6.1, 8.0.2, 8.1.1
17 7.3.3, 7.6.1, 8.0.2, 8.1.1

4.1.1

A small release to fix a bug related to Gradle's stale output tracking. If your project's .gradle directory is missing (e.g. first build) Gradle would delete the publish repo dir (build/gitPublish/*) after the gitPublishCopy thinking it was stale. As a result the gitPublishCommit would fail due to a missing repo directory. We now inform Gradle that the copy task's state should not be tracked (the other tasks were already set up that way).

NOTE: The fix to #99 only works on Gradle 7.3+. I highly recommend not using lower versions of gradle.

Breaking Changes

None

Enhancements

None

Fixes

  • #99 No such file or directory during gitPublishCommit

Deprecations

None

Compatibility

... (truncated)

Commits
  • 3e29a1b Update actions in workflows
  • 28cf8c8 Merge pull request #104 from ajoberstar/shallow
  • 73370cf Support shallow clone/fetch
  • 16a8de9 Upgrade grgit dependency
  • 69c4d71 Build with Gradle 8.1.1
  • f370117 Test against Gradle 8
  • 6791131 Document sign prop on publication
  • 621ef14 Clarify maintenance status
  • 58699af Merge pull request #100 from ajoberstar/bug
  • fa8aa9e patch: Fix no such file or directory during commit
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
msgilligan commented 1 year ago

See https://github.com/ConsensusJ/consensusj/commit/8313a2423febc93c0dd92883278648e1b74bf5a8 We probably need to change the gitPublishPush.dependsOn dependency.

msgilligan commented 1 year ago

See ConsensusJ/consensusj@8313a24 We probably need to change the gitPublishPush.dependsOn dependency.

Yes. Fixed in fb36e9d718152b5af1c83c62aab608a4447aad4d