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.0.0 - autoclosed #57

Closed

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 1, 2024

Mend Renovate

This PR contains the following updates:

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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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.

v2.0.0-rc-2: 2.0.0-rc-2 - preparations for 2.0.0-final

Notable changes:
  • Add closeStagingRepositories and releaseStagingRepositories summary tasks - #​236 (PR by @​Vampire)
  • Require Gradle 6.2+ (PRs by @​TWiStErRob)
  • Ability to build itself with Gradle 8.5
  • Multiple internal refactorings and improved idiomaticity (PRs by @​TWiStErRob and @​3flex)
  • Drop kotlin-dsl plugin and remove redundant buildSrc - #​295 and #​301 (PRs by @​3flex)
  • Make the artifact ID explicit rather than relying on implicit naming - #​255 (PR by @​TWiStErRob)
  • Massive dependency upgrades with Renovate
Backward incompatible changes
  • closeAndReleaseStagingRepository has been renamed to closeAndReleaseStagingRepositories for consistency

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

Thanks to all the contributors to this release: @​TWiStErRob, @​3flex, @​Goooler, @​Vampire, @​espertus and @​renovate-bot ;-).


Configuration

📅 Schedule: Branch creation - "on the first day of the month" (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 added the Renovate label Jun 1, 2024
Copy link

sonarqubecloud bot commented Jun 1, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@renovate renovate bot changed the title Update dependency io.github.gradle-nexus:publish-plugin to v2.0.0 Update dependency io.github.gradle-nexus:publish-plugin to v2.0.0 - autoclosed Jun 4, 2024
@renovate renovate bot closed this Jun 4, 2024
@renovate renovate bot deleted the renovate/io.github.gradle-nexus-publish-plugin-2.x branch June 4, 2024 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants