Skip to content

Remove legacy Clojure plugin ID and align Nebula conventions - #70

Merged
chali merged 2 commits into
mainfrom
remove-legacy-plugin-marker
Nov 17, 2026
Merged

chali merged 2 commits into
mainfrom
remove-legacy-plugin-marker

Conversation

@chali

@chali chali commented Nov 17, 2026

Copy link
Copy Markdown
Member

Summary

  • Remove the legacy nebula.clojure plugin declaration, retaining only com.netflix.nebula.clojure, following dependency-lock.
  • Align settings and plugin conventions with dependency-lock using Nebula 26.x.
  • Update Plugin Portal links and document migration from the legacy ID.
  • No project-specific publication filtering.

Context

The 15.2.1 release published successfully to the Plugin Portal but failed uploading the legacy marker nebula.clojure:nebula.clojure.gradle.plugin to Sonatype with HTTP 400. Dependency-lock successfully publishes its modern marker to Sonatype. Removing the legacy ID avoids the failing legacy publication; the precise server-side reason for the rejection remains unconfirmed.

Verification

  • Successful final --dry-run -Prelease.useLastTag=true in a temporary clean, locally tagged clone with these changes.
  • Task-state inspection confirms no legacy marker publication, while the modern marker, nebula publication, and publishPlugins remain enabled in the release graph.
  • git diff --check passes.
  • Full test suite not run; no artifacts published during verification.

Compatibility

New releases no longer provide the nebula.clojure plugin ID. Consumers must use com.netflix.nebula.clojure; previously published versions are unchanged.

@chali
chali merged commit acb2f19 into main Nov 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant