aurora-github 13.0.0

☕ Java

🚀 New actions

• setup-jvm-context - using SDKMAN to create a Java-oriented development environment based on Maven or Gradle.

🧨 Breaking changes

• for verify-jvm-project and publish-jvm-project:

  • it is now mandatory to include a .sdkmanrc file in the project directory

  • the following inputs have been removed:

    • java-version

    • tool-version

📦 NodeJS

🌟 Enhancements

• The corepack-version input now has a reasonable default value for all the NodeJS actions - and has become mandatory.

• publish-npm-package always uses npm publish to publish a package - no matter the package manager used by the project.

🧨 Breaking changes

• The .nvmrc file must not exist in a project directory.

• The package.json descriptor must exist, with the following mandatory fields:

  • engines/node - describing the required NodeJS version

  • packageManager or devEngines/packageManager - having different formats, as described in corepack's documentation.

🦀 Rust

🧨 Breaking changes

• the toolchain file is always mandatory in every Rust project.

• in setup-rust-context, the check-toolchain-file input has been removed - as it's pointless now.

🦀🌐 Rust web assemblies

🧨 Breaking changes

• A package.json descriptor must reside in the project directory, together with Cargo.toml - and must contain the following fields:

  • engines/node - describing the required NodeJS version

  • packageManager or devEngines/packageManager - having different formats, as described in corepack's documentation.

  Such file file will be merged with the package.json descriptor generated for the web assembly, if any.

• The following inputs have been removed from all Rust WASM actions:

  • node-version

  • package-manager

🐍 Python

🚀 New actions

• setup-python-context - creating a PDM-based environment for Python.

🌟 Enhancements

• for every Python action, the pdm-version input is now mandatory - but with a sensible default.

🧨 Breaking changes

• for both verify-python-package and publish-python-package, the pyproject.toml file is not only mandatory - but it must also contain the requires-python field.

😺 GitHub

🌟 Enhancements

• in publish-github-pages:

  • the corepack-version input is now mandatory but has a sensible default

🧨 Breaking changes

• in publish-github-pages:

  • the java-version and java-tool-version have been removed

  • stricter requirements, induced by setup-nodejs-context and setup-jvm-context.

🖥️ System tools

🚀 New actions

• setup-sdkman-context - uses the Elvish-oriented SDKMAN wrapper provided by ethereal to orchestrate SDKs described by a .sdkmanrc file.

❌ Deleted actions

• install-via-sdkman - replaced by setup-sdkman-context.

Full Changelog: v12.0.0...v13.0.0