v2.5 Improved version matching & PMD 7 Support

What's Changed

• Improved version matching & PMD 7 Support by @Clint-Chester in #12

Full Changelog: v2.4...v2.5

v2.4 Bug Fix

What's Changed

• fix: branch missing redirects to outputs + yaml lint by @sydneydf in #10

New Contributors

• @sydneydf made their first contribution in #10

Full Changelog: v2.3...v2.4

Update deprecated functions

What's Changed

• Update Action Outputs by @MattLoe in #9

Full Changelog: v2.2...v2.3

Bug Fixes

What's Changed

• Fix Script Issues by @MattLoe in #8

New Contributors

• @MattLoe made their first contribution in #8

Full Changelog: v2.1...v2.2

Push Behaviour Change & Using PMD Latest

Two major updates as part of this release:

• The push event behaviour is now changed (breaking change if you relied on how the push events were working when not analysing all code) so that it will compare the commit before a push to the last commit after to push. From a file diff perspective I'd say this makes more sense in comparison to the existing logic of comparing the latest commit on two different branches. This also means that we can make use of the SARIF uploader to get comments for pull request diffs.
• The ability to specify latest as the PMD version you'd like so you can pull straight from the PMD releases. This resolves #3

SARIF Reports and File Diff Options

This now produces SARIF reports that can be uploaded to GitHub rather than inline messaging on the pull requests. An additional feature was also added where the file diff options can either be done with a git diff or based on the files changed on a GitHub Pull Request.

Minor Fixes

There was minor code refactoring in this release, as well as a bug fix on the URL in the message provided.

Initial Release

This initial release of using PMD Analyser as a GitHub Action includes the following features:

• Analyse the whole code base or just files changed
• Specify which rules should create error notifications and failed GitHub Action runs