Release v1.0.5

This release brings 2 minor usability improvements, and one 'larger' feature to specify failure-levels. View the README.md section on failure-levels for details.

Added

1. #10 - Improved log output
2. #11 - Support failure-levels to allow customization of what verifier failures trigger an action failure
3. #15 - Add a nice message for generic error capturing

Upgrade

1. N/A

Fixed

1. N/A

Release v1.0.4

This release brings a bug fix where the regex to identify failures was too strict, causing plugin verification failures to not be surfaced as failures in the action.

Added

1. N/A

Upgrade

1. N/A

Fixed

1. #11 - Support different failure levels, similar to the Gradle IntelliJ Plugin (bugfix; see this comment in the issue for details

Release v1.0.3

This release brings the ability to pass a file for the input ide-versions to allow keeping the workflow file tidy and commit-free. It also fixes a bug where the verification check fails for invalid plugins.

Added

1. #5 - Allow configuration of IDE + versions via a file

Upgrade

1. Bumping major version to 1.0.3 since there have not been any major issues reported since the initial release.

Fixed

1. #8 - Add verification check for invalid (aka, "not valid") plugins output

Release v0.0.2

This release brings a new input value for verifier-version (LATEST) which automatically uses the latest released version of intellij-plugin-verifier. It also fixes a bug where the GitHub runner disk space runs out of storage when verifying against multiple IDEs.

Added

1. #3 - Provide "LATEST" option for verifier-version to automatically update to the latest version of intellij-plugin-verifier

Upgrade

1. N/A

Fixed

1. #2 - Action fails due to "No space left on device"

Release v0.0.1

Introducing the IntelliJ Platform Plugin Verifier GitHub Action!

This initial release (v0.0.1) includes the ability to:

1. specify the version of the JetBrains intellij-plugin-verifier
2. specify the path of the JetBrains plugin
3. specify multiple IDE/version combinations to verify
4. have access to the verification output log file for further processing in subsequent steps