Bump auto from 9.18.0 to 9.19.0

[dependabot-preview]

Bumps auto from 9.18.0 to 9.19.0.

Release notes

Sourced from auto's releases.

v9.19.0

Release Notes

From #996

The gradle plugin has enabled many Java and Android engineers to automate the versioning of their projects. While the old gradle plugin's features were primarily targeted at app developers, this release brings features that make auto ergonomic for library authors! 🎉

-SNAPSHOT Versioning

A common versioning pattern for java projects is -SNAPSHOT Versioning. It is especially helpful for library authors and helps with testing their libraries.

All you have to do to start using this feature is add -SNAPSHOT to your version in build.gradle or gradle.properties and auto will start using-snapshot Versioning. If you want to configure the snapshot suffix just set snapshotSuffix in gradle.properties.

Publish Support

Another useful feature for library authors, auto will now call the publish task if it is configured for your project. 🚀

versionFile deprecation

Previously this plugin had to use a versionFile to keep track of the version of the project. Now it will parse the gradle properties command for this information.

This is not a breaking change, you'll just have an extra file you can delete

---

🚀 Enhancement

• auto, @auto-it/core, @auto-it/conventional-commits, @auto-it/gradle
  • 🐘 Gradle Plugin: Add support for snapshot versioning, publishing, and less configuration #996 (@sugarmanz Jeremiah_Zucker@Intuit.com @hipstersmoothie)

Authors: 3

• Andrew Lisowski (@hipstersmoothie)
• Jeremiah (Jeremiah_Zucker@Intuit.com)
• Jeremiah Zucker (@sugarmanz)

Changelog

Sourced from auto's changelog.

v9.19.0 (Sat Mar 07 2020)

Release Notes

From #996

The gradle plugin has enabled many Java and Android engineers to automate the versioning of their projects. While the old gradle plugin's features were primarily targeted at app developers, this release brings features that make auto ergonomic for library authors! 🎉

-SNAPSHOT Versioning

A common versioning pattern for java projects is -SNAPSHOT Versioning. It is especially helpful for library authors and helps with testing their libraries.

All you have to do to start using this feature is add -SNAPSHOT to your version in build.gradle or gradle.properties and auto will start using-snapshot Versioning. If you want to configure the snapshot suffix just set snapshotSuffix in gradle.properties.

Publish Support

Another useful feature for library authors, auto will now call the publish task if it is configured for your project. 🚀

versionFile deprecation

Previously this plugin had to use a versionFile to keep track of the version of the project. Now it will parse the gradle properties command for this information.

This is not a breaking change, you'll just have an extra file you can delete

---

🚀 Enhancement

• auto, @auto-it/core, @auto-it/conventional-commits, @auto-it/gradle
  • 🐘 Gradle Plugin: Add support for snapshot versioning, publishing, and less configuration #996 (@sugarmanz Jeremiah_Zucker@Intuit.com @hipstersmoothie)

Authors: 3

• Andrew Lisowski (@hipstersmoothie)
• Jeremiah (Jeremiah_Zucker@Intuit.com)
• Jeremiah Zucker (@sugarmanz)

---

Commits

• 1a0275b Bump version to: v9.19.0 [skip ci]
• 4d01458 Update CHANGELOG.md [skip ci]
• 5628873 Merge pull request #996 from sugarmanz/gradle-snapshot
• f6dfe71 add properties target to readme
• 6c3a3be add some fluff to the gradle readme
• 4c111bd tap into validate config
• 1d89a3b Merge origin/master into gradle-snapshot
• cb84be7 Bump brew formula [skip ci]
• See full diff in compare view

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.

If all status checks pass Dependabot will automatically merge this pull request.

---

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)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)