Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency io.github.gradle-nexus:publish-plugin to v2 #267

Merged
merged 1 commit into from
May 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 8, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.github.gradle-nexus:publish-plugin 1.1.0 -> 2.0.0 age adoption passing confidence

Release Notes

gradle-nexus/publish-plugin (io.github.gradle-nexus:publish-plugin)

v2.0.0: 2.0.0 - publishing with Ivy + sensible Gradle 8.x compatibility

Notable changes in 2.0

  • support publishing with Ivy - #​222
  • add closeStagingRepositories and releaseStagingRepositories summary tasks - #​236
  • deprecate build support for Java 8 (build target still set to 8, but building with JDK <11 might fail) - #​171
  • improve support for build cache and compatibility with Gradle 8.x
  • last, but not least - new team member - @​TWiStErRob - welcome aboard!
Backward incompatible changes
  • closeAndReleaseStagingRepository has been renamed to closeAndReleaseStagingRepositories for consistency

Full list of changes since 1.3.0: gradle-nexus/publish-plugin@v1.3.0...v2.0.0


Changes in 2.0.0-final (since rc-2):
  • simplify build configuration
  • enhance documentation
  • improve E2E tests execution on CI
  • build itself with Gradle 8.6
  • dependency upgrade

Full list of changes: gradle-nexus/publish-plugin@v2.0.0-rc-2...v2.0.0

Thanks to all the contributors to this release: @​TWiStErRob, @​3flex, @​Goooler.

v1.3.0: 1.3.0 - ability to create and release staging repository in separate calls

Notable changes:

  • Ability to create and release staging repository in separate calls (e.g. after manual verification) - #​19 (PR by @​vlsi)

Thanks to all the contributors to this release: @​vlsi.

v1.2.0: 1.2.0 - no deprecation warning in Gradle 7.6+

Notable changes:

  • Fix ConfigureUtil deprecation warning in Gradle 7.6+ - #​152
  • Improve "not in desired state" error message - #​157
  • CI basic regression tests with Gradle 8 (effectively from 5.0 to 8.0) - #​168
  • CI basic regression tests with JDK 17 (effectively with 8, 11 and 17) - #​179
  • Enhance documentation - #​94, #​135, #​108
  • Update used Gradle to 8.0 (still compatible with 5.0+) - #​168
  • Update project dependencies - #​169

More changes.

Big thank you to the contributors who provided pull requests: @​TWiStErRob, @​vlsi, @​nedtwigg, @​turansky, @​larsgrefer, @​nhajratw, @​tschuchortdev, @​JavierSegoviaCordoba and also those who were involved in any other way.


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/io.github.gradle-nexus-publish-plugin-2.x branch from 806a153 to e058e37 Compare May 23, 2024 16:59
@renovate renovate bot force-pushed the renovate/io.github.gradle-nexus-publish-plugin-2.x branch from e058e37 to 9a417cc Compare May 27, 2024 18:50
@orchestr7 orchestr7 merged commit d0f9d72 into main May 28, 2024
5 checks passed
@orchestr7 orchestr7 deleted the renovate/io.github.gradle-nexus-publish-plugin-2.x branch May 28, 2024 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant