Skip to content
This repository has been archived by the owner on Feb 25, 2024. It is now read-only.

Bump gradle-nexus-staging-plugin from 0.21.1 to 0.30.0 #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps gradle-nexus-staging-plugin from 0.21.1 to 0.30.0.

Release notes

Sourced from gradle-nexus-staging-plugin's releases.

0.30.0

  • Replace from old unsupported HTTP Builder to OkHttp 4 - #188 - PR by anuraaga
  • Switch project development to maintenance mode - see below
  • Switch build to Gradle 6.8.3
  • Remove deprecated since 0.8.0 promoteRepository and closeAndPromoteRepository tasks

Backward compatibility note. Due to the internal HTTP client library change, the plugin might start behaving slightly different in certain situations.

PROJECT DEVELOPMENT SWITCHED TO THE MAINTENANCE MODE. To make releasing to Maven Central even easier, I and Marc Phillip (the author of nexus-publish-plugin) combined forces to create a next generation, unified 2-in-1 plugin - gradle-nexus-publish-plugin. It is a recommended solution, as our development effort will be put in that new plugin. See my blog post and the official migration guide.

Thank you for over 5 years of releasing with my plugin!

0.22.0

  • Change default retrying time to 5 minutes - a value recommended by Sonatype (suggestion by Mikhail Yakushin)
  • Switch build to Gradle 6.6
  • Bump some dependencies
  • Check basic compatibility with Gradle up to 6.6
  • CI server sanity check for Java 14 compatibility

0.21.2

Changelog

Sourced from gradle-nexus-staging-plugin's changelog.

0.30.0 - 2021-02-26

  • Replace from old unsupported HTTP Builder to OkHttp 4 - #188 - PR by anuraaga
  • Switch project development to maintenance mode - see below
  • Switch build to Gradle 6.8.3
  • Remove deprecated since 0.8.0 promoteRepository and closeAndPromoteRepository tasks

Backward compatibility note. Due to the internal HTTP client library change, the plugin might start behaving slightly different in certain situations.

PROJECT DEVELOPMENT SWITCHED TO THE MAINTENANCE MODE. To make releasing to Maven Central even easier, I and Marc Phillip (the author of nexus-publish-plugin) combined forces to create a next generation, unified 2-in-1 plugin - gradle-nexus-publish-plugin. It is a recommended solution, as our development effort will be put in that new plugin. See my blog post and the official migration guide.

Thank you for over 5 years of releasing with my plugin!

0.22.0 - 2020-08-17

  • Change default retrying time to 5 minutes - a value recommended by Sonatype (suggestion by Mikhail Yakushin)
  • Switch build to Gradle 6.6
  • Bump some dependencies
  • Check basic compatibility with Gradle up to 6.6
  • CI server sanity check for Java 14 compatibility

0.21.2 - 2019-12-23

Commits
  • e7f5648 Release version: 0.30.0
  • fcb453c Trigger release
  • f57facd #193 Document maintenance mode and migration recommendation
  • 7d0598e Increase network timeouts to match those from new plugin
  • 38b35e4 #83 Remove deprecated promoteRepository and closeAndPromoteRepository tasks
  • 21254a2 Bump plugin-publish-plugin from 0.12.0 to 0.13.0 (#190)
  • 431f045 Bump nebula-test from 7.9.2 to 7.10.2
  • 8aca63f Some workarounds on CDeliveryBoy limitations
  • 4dc1904 Bump byte-buddy from 1.10.14 to 1.10.21 (#191)
  • a769666 Bump gradle-animalsniffer-plugin from 1.5.1 to 1.5.3 (#189)
  • 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Feb 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants