Nessie 0.105.0

• 21 commits since 0.104.10
• Maven Central: https://search.maven.org/search?q=g:org.projectnessie.nessie+v:0.105.0
• 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.105.0-java
• PyPI: https://pypi.org/project/pynessie/ (See pynessie)
• Helm Chart repo: https://charts.projectnessie.org/

Try it

The attached nessie-quarkus-0.105.0-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.105.0/nessie-quarkus-0.105.0-runner.jar
java -jar nessie-quarkus-0.105.0-runner.jar

Nessie CLI is attached as nessie-cli-0.105.0.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.105.0.

Nessie GC tool is attached as nessie-gc-0.105.0.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.105.0 --help.

Nessie Server Admin tool is attached as nessie-server-admin-tool-0.105.0-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.105.0 --help.

The attached nessie-helm-0.105.0.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

Fixes

• A bug has been resolved in the OAuth2 Authorization Code grant type. This fix addresses an issue
  where the extra-params configuration option was not being properly included in the authorization
  URI. Consequently, users, particularly Auth0 users passing the audience parameter, were receiving
  opaque tokens instead of JWTs.

Full Changelog (minus renovate commits):

• OAuth2 (Authorization Code): Include extra parameters in authorization URI (#11239)