Skip to content

Version v2.0

Marketplace
Marketplace

Choose a tag to compare

View all tags
@reactive-firewall reactive-firewall released this 26 Feb 04:07
· 5 commits to master since this release
v2.0
This tag was signed with the committer’s verified signature.
reactive-firewall Mr. Walls
GPG key ID: D5F9B77C48DE50FD
Verified
Learn about vigilant mode.
434ca8b
This commit was signed with the committer’s verified signature.
reactive-firewall Mr. Walls
GPG key ID: D5F9B77C48DE50FD
Verified
Learn about vigilant mode.

Patch Notes

  • This version enhances overall stability, and migrates several components to newer implementations.

Important

🔧 Breaking changes in v2.0

Due to the underlying implementation of GitHub's Code-Scanning Dashboard, some users will see warnings about shellcheck scan workflow configuration(s). These warnings are unavoidable when upgrading to the new v2.x series for the first time. See below for details and recommended resolution.

Impacted GHI

Included and Superseded PRs/MRs

  • Includes and supersedes #12
  • Includes and supersedes #13
  • Includes and supersedes #14
  • Includes and supersedes #15

v2.0 Migration Troubleshooting

Tip

Users who previously used v1 will need to migrate to using v2 to benefit from this, and future updates.

Previous tool "configuration" is "out of date" after upgrade

Warning

After initially upgrading from version v1 series of shellcheck-scan, users will see shellcheck-scan configuration warnings, namely about legacy ad-hoc configurations. New setups (including full remove-then-re-setup workflows) should not normally encounter these warnings

When encountering configuration "is out of date" warnings for shell-check, no historical data is destroyed by default. GitHub should continue to retain the scan data as normal according to your GitHub plan. However unless you named everything exactly shellcheck-scan in your workflow config, everything before upgrading will be marked as now being "out-of-date".

E.g., You will likly see the warning all over the GitHub Security tab in the Web UI.

Screenshot_GHI_16_Overview

Once you are ready to clear out historical results (e.g., after they have been fixed, or perhaps as soon as the latest scan, etc.)

  1. Navigate to the Code scanning tools, for example from the warning itself:
Screenshot_GHI_16_example_code_scan_warn
  1. Then navigate to the out-of-date shellcheck tool (note: in some cases, it may even have been called something other than "shellcheck-scan" before)
Screenshot_GHI_16_tools_config_warn
  1. Open the tool configuration
Screenshot_GHI_16_find_configs
  1. identify the legacy/ad-hoc v1 configuration(s) (e.g., the ones marked out-of-date)
Screenshot_GHI_16_Legacy_name_hint Screenshot_GHI_16_new_name_hint

Tip

You can also identify legacy configurations by the shellcheck version -- circa 2026 the version should be 0.9 (or 0.11 depending on the GitHub runner)

Screenshot_GHI_16_version_v1_hint
  1. You can safely delete the configurations that are out-of-date if you wish.

Important

Be sure preserve the actual repo yaml file (e.g., .github/workflow/shellcheck.yml etc.) file for the latest shellcheck-scan action)

Screenshot_GHI_16_delete_option

Full Changelog: v1.2...v2.0

Assets 2
Loading