Releases: ChrisCarini/intellij-platform-plugin-verifier-action
v2.0.1
v2.0.0
⚠️ 🎉 v2.0.0
is intended for IntelliJ platform versions 2022.3
and beyond. 🎉 ⚠️
v2.0.0
uses JDK 17 which is intended for IntelliJ platform versions 2022.3
and beyond. If your plugin still needs to run on multiple versions of the IDE prior to 2022.3
, continue to use the v1.x
series of versions of this GitHub Action. See IntelliJ Project Migrates to Java 17 for more information.
What's Changed
- Update Dockerfile to use Eclipse Temurin JDK 17 by @ChrisCarini in #39
Full Changelog: v1.2.3...v2.0.0
v1.2.3
What's Changed
- Switch to using Eclipse Temurin; AdoptOpenJDK is deprecated.
- See https://hub.docker.com/_/adoptopenjdk & https://github.com/AdoptOpenJDK/openjdk-docker - marked deprecated after 2021-08-25
Full Changelog: v1.2.2...v1.2.3
v1.2.2
What's Changed
- Migrating set-output to environment files per GitHub deprecation notice by @ChrisCarini in bd922a8
- Bump pyjwt from 2.3.0 to 2.4.0 in /bin by @dependabot in #36
- Adding GitHub CODEOWNERS by @ChrisCarini in #37
New Contributors
- @dependabot made their first contribution in #36
Full Changelog: v1.2.1...v1.2.2
Release v1.2.1
What's Changed
- Switch to using JetBrains Maven repository for
intellij-plugin-verifier
download URL. by @ChrisCarini in #31
WARNING: If you are specifying a
verifier-version
, you will need to use version1.255
or later when using this version of the GitHub Action (or later versions).
Full Changelog: v1.2.0...v1.2.1
Release v1.2.0
What's Changed
- Adding support for
GITHUB_TOKEN
for authenticated requests to resolve latest release ofJetBrains/intellij-plugin-verifier
. by @ChrisCarini in #28
NOTICE: In a future, major version release (following SemVer, we will require the usage of GITHUB_TOKEN
when setting the verifier-version
to LATEST
. Follow #30 for updates.
Full Changelog: v1.1.0...v1.2.0
Release v1.1.0
What's Changed
- #21 Update Java compatibility to 11 by @sadv1r in #22
- Fixing bug for non-latest verifier versions where the VERIFIER_DOWNLOAD_URL is missing the VERIFIER_JAR_FILENAME. by @ChrisCarini in #27
New Contributors
Full Changelog: v1.0.6...v1.1.0
Release v1.0.7
This release upgrades the Java compatibility to Java 11, and also fixes false signals when the verifier fails (non-zero exit code) and is not surfaced as a failure.
Added
- N/A
Upgrade
Fixed
- #22 - Raise errors when the verifier exit status fails (This was addressed in the same PR as the Java compatibility upgrade)
Release v1.0.6
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
Upgrade
- N/A
Fixed
- N/A
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
- #10 - Improved log output
- #11 - Support
failure-levels
to allow customization of what verifier failures trigger an action failure - #15 - Add a nice message for generic error capturing
Upgrade
- N/A
Fixed
- N/A