This repository has been archived by the owner on Sep 8, 2022. It is now read-only.
Update dependency com.netflix.nebula:gradle-info-plugin to v11 #58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/com.netflix.nebula-gradle-info-plugin-11.x
branch
2 times, most recently
from
33f0458
to
865fa04
Compare
renovate
bot
force-pushed
the
renovate/com.netflix.nebula-gradle-info-plugin-11.x
branch
3 times, most recently
from
d92d30f
to
acf568f
Compare
renovate
bot
force-pushed
the
renovate/com.netflix.nebula-gradle-info-plugin-11.x
branch
2 times, most recently
from
f2a65bb
to
660b402
Compare
renovate
bot
force-pushed
the
renovate/com.netflix.nebula-gradle-info-plugin-11.x
branch
2 times, most recently
from
203228c
to
47604ea
Compare
renovate
bot
force-pushed
the
renovate/com.netflix.nebula-gradle-info-plugin-11.x
branch
from
47604ea
to
3e9d749
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.0.3->11.3.3Release Notes
nebula-plugins/gradle-info-plugin
v11.3.3What's Changed
Stringto avoid theirObjectform from being serializedv11.3.0What's Changed
v11.2.0What's Changed
v11.1.0What's Changed
Full Changelog: nebula-plugins/gradle-info-plugin@v11.0.1...v11.1.0
v11.0.1jartask cacheabilityv11.0.0Breaking change. Gradle 7 support
v10.1.3Improve credential stripping from Git remote origin URLs
v10.1.2Build-Date-UTCv10.1.1Build-Date-UTCand useBuil-Datewith current timezonev10.1.0BasicInfoPlugin:Build-Dateuses UTC and introduceBuild-Timezoneattributev10.0.0Breaking change. Requires Gradle 6.7+
InfoJavaPlugin: add toolchain support for Build-Java-Version.v9.3.0Upgrade JNA for Apple Silicon compatibility
v9.2.0v9.1.2Add guard around POSIXUtil due to JNA not working on Apple Silicon
v9.1.1Implementation-Title,Implementation-VersionandBuilt-Statusto ignored propertiesv9.1.0MANIFEST.MFattributesv8.5.0TitusProviderfor CIv8.4.0InfoJarManifestPlugin: configure META-INF normalization to ignore gradle-info-plugin attributesv8.3.2forUseAtConfigurationTimeusage to work with old versions of gradlev8.3.1forUseAtConfigurationTimeusage to work with old versions of gradlev8.3.0All tasks in the plugin should now follow the Gradle lazy configuration.
v8.2.0GitScmProvidersupports Full-Change attribute to get a non abbreviated commit hashv8.1.0v8.0.0Use
ProviderFactoryin order to support configuration cacheThis is a breaking change and requires Gradle 6.5+
v7.1.4PerforceScmProvider: handle null WORKSPACE env variable value https://github.com/nebula-plugins/gradle-info-plugin/pull/65v7.1.3writeManifestPropertiesis invoked as a dependency ofJartasks again. Its output is not bundled into the jars though. That returns the original contract but still achieves our caching improvements.v7.1.2v7.1.1v7.1.0v7.0.1Avoid metadata properties file conflicts when multiple jar tasks are present within a single gradle project module. The final content would be correct but caching would not be efficient.
v7.0.0The adds properties file with metadata into each jar. Changes in this metadata file will not cause the
jartask to execute but reused previous output if possible. This feature is no longer requiringwriteManifestPropertiestask invocation so this task won't be invoked anymore as part ofjartask invocation.v6.0.0Manifest.mf entries are no longer inputs of
Jartasks. It has the following implications. A change of an entry (e.g. project status, branch name etc.) will not causeJartasks to rerun. It means in some cases you can have stale metadata. The benefit is much better cacheableJartasks. Local task avoidance or Gradle distribute caching will only rebuild the archive when there is an actual content change. This is very important for shaded jars which are expensive to build.Dependencies info plugin is now avoiding the resolution of deprecated configurations to follow the recommended usage of each configuration by Gradle.
v5.2.0v5.1.1v5.0.0Upgrade to Gradle 5.x - breaking change
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled due to failing status checks.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.