projectnessie/nessie nessie-0.94.1

Nessie 0.94.1

on GitHub

• 8 commits since 0.94.0
• Maven Central: https://search.maven.org/search?q=g:org.projectnessie.nessie+v:0.94.1
• Docker images: https://github.com/projectnessie/nessie/pkgs/container/nessie and https://quay.io/repository/projectnessie/nessie?tab=tags
  It is a multiplatform Java image (amd64, arm64, ppc64le, s390x): docker pull ghcr.io/projectnessie/nessie:0.94.1-java
• PyPI: https://pypi.org/project/pynessie/ (See pynessie)
• Helm Chart repo: https://charts.projectnessie.org/

Try it

The attached nessie-quarkus-0.94.1-runner.jar is a standalone uber-jar file that runs on Java 17 or newer and it is also available via Maven Central. Download and run it (requires Java 17):

wget https://github.com/projectnessie/nessie/releases/download/nessie-0.94.1/nessie-quarkus-0.94.1-runner.jar
java -jar nessie-quarkus-0.94.1-runner.jar

Nessie CLI is attached as nessie-cli-0.94.1.jar, which is a standalone uber-jar file that runs on Java 11 or newer. Nessie CLI is also available as a Docker image: docker run --rm -it ghcr.io/projectnessie/nessie-cli:0.94.1.

Nessie GC tool is attached as nessie-gc-0.94.1.jar, which is a standalone uber-jar file that runs on Java 11 or newer. Shell completion can be generated from the tool, check its help command. Nessie GC tool is also available as a Docker image: docker run --rm ghcr.io/projectnessie/nessie-gc:0.94.1 --help.

Nessie Server Admin tool is attached as nessie-server-admin-tool-0.94.1-runner.jar, which is a standalone uber-jar file that runs on Java 17 or newer. Shell completion can be generated from the tool, check its help command. Nessie Server Admin tool is also available as a Docker image: docker run --rm ghcr.io/projectnessie/nessie-server-admin:0.94.1 --help.

The attached nessie-helm-0.94.1.tgz is a packaged Helm chart, which can be downloaded and installed via Helm. There is also the Nessie Helm chart repo, which can be added and used to install the Nessie Helm chart.

Changelog

Upgrade notes

• Helm chart: the logLevel configuration option now only sets the log level for the console and
  file appenders, but does not change the io.quarkus logger level anymore. To actually modify a
  logger level, use the advancedConfig section and set the
  quarkus.log.category."<category>".level configuration option, e.g.
  quarkus.log.category."io.quarkus".level=DEBUG would set the log level for the io.quarkus
  logger to DEBUG, effectively achieving the same as setting logLevel to DEBUG in previous
  versions.

Full Changelog (minus renovate commits):

• Quarkus: split out code from :nessie-quarkus into separate modules (#9189)
• Include LoggingConfigSourceInterceptor to help diagnose configuration issues (#9190)
• Helm chart: don't set quarkus.log.level (#9191)