Bump com.netflix.nebula:nebula-publishing-plugin from 20.3.0 to 21.0.0

[dependabot]

Bumps com.netflix.nebula:nebula-publishing-plugin from 20.3.0 to 21.0.0.

Release notes

Sourced from com.netflix.nebula:nebula-publishing-plugin's releases.

v21.0.0

What's Changed

• Replace project.buildDir with project.layout.buildDirectory by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#188
• Introduce BaseIntegrationTestKitSpec by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#189
• Config cache compatibility by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#190
• Add configuration cache for publishing verification phase by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#191

Full Changelog: nebula-plugins/nebula-publishing-plugin@v20.3.0...v21.0.0-rc.1

v21.0.0-rc.2

Full Changelog: nebula-plugins/nebula-publishing-plugin@v21.0.0-rc.1...v21.0.0-rc.2

v21.0.0-rc.1

What's Changed

• Replace project.buildDir with project.layout.buildDirectory by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#188
• Introduce BaseIntegrationTestKitSpec by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#189
• Config cache compatibility by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#190
• Add configuration cache for publishing verification phase by @​rpalcolea in nebula-plugins/nebula-publishing-plugin#191

Full Changelog: nebula-plugins/nebula-publishing-plugin@v20.3.0...v21.0.0-rc.1

Commits

• 5ffcbb4 Restore IvyCompileOnlyPlugin
• 0bf65e2 Merge pull request #191 from nebula-plugins/publish-verification-config-cache
• bf3ad53 Enable configuration cache in tests
• 6c2f4ad PublishVerificationPlugin: replace VerificationViolationsCollectorHolderExten...
• 1bf4945 Remove plugins that can't be config cache compliant and are IVy based
• f8376a0 Merge pull request #190 from nebula-plugins/config-cache-compatibility
• 60e860f make IvyRemoveInvalidDependenciesPlugin and IvyRemovePlatformDependenciesPlug...
• b629334 Make IvyCompileOnlyPlugin config cache compatible
• 0c0edb1 IvyNebulaPublishPlugin: manage component information properly
• 9f298df Make MavenRemoveInvalidDependenciesPlugin config cache compatible
• 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 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 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)

Check List

• New functionality includes testing.
• All tests pass
• New functionality has been documented.
• New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

[github-actions]

Compatibility status:

Checks if related components are compatible with change f5c8cdd

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/performance-analyzer.git]

[github-actions]

❌ Gradle check result for f5c8cdd: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for bfbbf15: SUCCESS

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f92f846) 71.36% compared to head (f5c8cdd) 71.33%.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #11671      +/-   ##
============================================
- Coverage     71.36%   71.33%   -0.04%     
- Complexity    59152    59153       +1     
============================================
  Files          4906     4906              
  Lines        278198   278198              
  Branches      40422    40422              
============================================
- Hits         198542   198442     -100     
- Misses        63111    63267     +156     
+ Partials      16545    16489      -56     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[reta]

❌ Gradle check result for f5c8cdd: FAILURE

#10704

[github-actions]

❕ Gradle check result for f5c8cdd: UNSTABLE

• TEST FAILURES:

      1 org.opensearch.remotestore.RemoteIndexPrimaryRelocationIT.testPrimaryRelocationWhileIndexing

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-11671-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f7d291456810603f259a243aee98188be5c7070a
# Push it to GitHub
git push --set-upstream origin backport/backport-11671-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-11671-to-2.x.