No.

No is a project that exists solely to test publication to Central Publisher Portal before the OSSRH sunset.

What does it do?

It prints "no!" to standard output and exits with an error.

Notes on publishing to Central Portal

  1. Migrate your namespace to Central Portal.
  2. Add this line to build.sbt:
    ThisBuild / sonatypeCredentialHost := xerial.sbt.Sonatype.sonatypeCentralHost
        

    This replaces any deprecated reference to tlSonatypeUseLegacyHost.

  3. Run the workflow on at least Java 11, lest your publish fail with a java/net/http/HttpTimeoutException. See xerial/sbt-sonatype#548.
    ThisBuild / githubWorkflowJavaVersions := Seq(JavaSpec.temurin("11"))
        

Coding standards

The ideal commit message asks a rhetorical question and ends with, No. Is this always possible? No.

FAQ

Will this be maintained long term?

No.

Are new features planned?

No.

Are you proud that this is on GitHub?

No.

May I send AI slop requests?

No.

Don’t you regret not naming this no4s?

No.

¿Puedo traducirlo al español?

Solo si se añade un signo de exclamación invertido. De lo contrario, ¡no!