Bump nl.littlerobots.version-catalog-update from 0.8.4 to 1.1.0

[dependabot]

Bumps nl.littlerobots.version-catalog-update from 0.8.4 to 1.1.0.

Release notes

Sourced from nl.littlerobots.version-catalog-update's releases.

Version 1.1.0

• Fix adding dependencies that are contributed through build scripts (#179)
• Add a new option to the versionCatalogUpdate task that will fail the build if there are updates for any dependency or specific dependencies. (#168)

v1.0.1

• Fix handling of version conditions using reject (#177)

v1.0.0

Version 1.0.0

This version no longer uses the dependency versions plugin for resolving versions, but is using Gradle APIs to resolve the version catalog dependencies. This option has been available behind a flag for a while and is now the default.

This is quite a big change which has a few behavioral changes, but will also result in a more predictable output.

If you do not need the functionality that the dependency versions plugin is providing, you can remove the plugin from your build.gradle, as it is no longer required for this plugin.

Some configuration options have changed, please refer to the README for details.

Resolving dependencies

Previously, only dependencies that where part of a depdencies block would be detected by the plugin. This would lead to situations where sometimes entries in the version catalog where not updated because these entries weren't used. Now all dependencies from the version catalog will be resolved and checked for updates, whether they are used or not in the project.

This also means most of the old options to keep dependencies are now no longer applicable; since the plugin is no longer "checking" what dependencies are used, it can also no longer determine which dependencies are not. See the README for updated configuration.

Because the plugin no longer requires dependencies to be used in your project, it's also very easy now to have "catalog only" projects. For an example see https://github.com/jamesward/kotlin-universe-catalog

Selecting versions

Previously the dependency versions plugin and its configuration would determine acceptable versions. As of this version the versionSelector configuration is used to configure this. The default configuration will prefer stable versions, unless the entry in the version catalog is already using an unstable version (like alpha, beta, etc.).

Creating a version catalog

Because the source of truth is now the version catalog file, there's no way anymore to create a new version catalog based on existing dependencies.

Improvement to version constraints

When a version constraint is applied to an entry in the version catalog, the plugin will now suggest suitable updates if they are available.

Version 0.8.5

• Fix setting version selector for kts build files (#149)
• Fixes for new resolver behaviour that had regressed vs the old resolver

Changelog

Sourced from nl.littlerobots.version-catalog-update's changelog.

Version 1.1.0

• Fix adding dependencies that are contributed through build scripts (#179)
• Add a new option to the versionCatalogUpdate task that will fail the build if there are updates for any dependency or specific dependencies. (#168)

Version 1.0.1

• Fix handling of version conditions using reject (#177)

Version 1.0.0

This version no longer uses the dependency versions plugin for resolving versions, but is using Gradle APIs to resolve the version catalog dependencies. This option has been available behind a flag for a while and is now the default.

This is quite a big change which has a few behavioral changes, but will also result in a more predictable output.

If you do not need the functionality that the dependency versions plugin is providing, you can remove the plugin from your build.gradle, as it is no longer required for this plugin.

Some configuration options have changed, please refer to the README for details.

Resolving dependencies

Previously, only dependencies that where part of a dependencies block would be detected by the plugin. This would lead to situations where sometimes entries in the version catalog where not updated because these entries weren't used. Now all dependencies from the version catalog will be resolved and checked for updates, whether they are used or not in the project.

This also means most of the old options to keep dependencies are now no longer applicable; since the plugin is no longer "checking" what dependencies are used, it can also no longer determine which dependencies are not. See the README for updated configuration.

Because the plugin no longer requires dependencies to be used in your project, it's also very easy now to have "catalog only" projects. For an example see https://github.com/jamesward/kotlin-universe-catalog

Selecting versions

Previously the dependency versions plugin and its configuration would determine acceptable versions. As of this version the versionSelector configuration is used to configure this. The default configuration will prefer stable versions, unless the entry in the version catalog is already using an unstable version (like alpha, beta, etc.).

Creating a version catalog

Because the source of truth is now the version catalog file, there's no way anymore to create a new version catalog based on existing dependencies.

Improvement to version constraints

When a version constraint is applied to an entry in the version catalog, the plugin will now suggest suitable updates if they are available.

... (truncated)

Commits

• 9b5539b Bump version for release
• c184b94 Update changelog
• b33217b Merge pull request #190 from littlerobots/version-catalog-plugin-check
• e36e65e Update Readme
• 2293071 Rename options
• 29a65db Verify that pinned libraries are still being reported when using --check
• 5d234d0 Introduce check option to fail the build if there are updates
• d9fb1f4 Merge pull request #181 from littlerobots/fix/filter-resolved
• b549575 Filter resolved versions
• f0fac4e Bump version for development
• Additional commits viewable 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.

---

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)