3.8.0 | Community Release

What's Changed

New Rule in beta!

Rule (Configuration ID)	Description
Get Record All Fields (GetRecordAllFields)	Following the principle of least privilege (PoLP), avoid using Get Records with 'Automatically store all fields' unless necessary.

• feat: new rule get record all fields beta by @junners in #156

Full Changelog: v3.7.0...v3.8.0

3.7.0 | Community Release

Full Changelog: v3.6.0...v3.7.0

3.6.0 | TrueNorthDreamin' Special Releae

What's Changed

• fix: trigger order to run only for record triggered flows by @junners in #155

Full Changelog: v3.5.0...v3.6.0

3.4.0 | Community Release

New Rule

This rule is opt-in only while running in beta

to opt-in, use modify your .flow-scanner.yml configuration with the ff:

rules:
  RecursiveAfterUpdate:
    severity: error

Rule (Configuration ID)	Description
Recursive After Update (RecursiveAfterUpdate)	After updates are meant to be used for record modifications that are not the same record that triggered the flow. Using after updates on the same record can lead to recursion and unexpected behavior. Consider using before save flows for same record updates.

What's Changed

• feat: add new rule on beta recursive after update opt in only by @junners in #153

Full Changelog: v3.3.0...v3.4.0

3.3.0 | Community Release

CVE and Security Fixes

Full Changelog: v3.2.1...v3.3.0

3.2.0 | Community Release

What's Changed

Rule Activation!

Rule (Configuration ID)	Description
Trigger Order (TriggerOrder)	Guarantee your flow execution order with the Trigger Order property introduced in Spring '22

• feat(rule): activate trigger order rule by @junners in #150

Full Changelog: v3.1.0...v3.2.0

3.1.0 | Community Release

What's Changed

• chore: update core version to 4.19.0 by @junners in #149

Full Changelog: v3.0.0...v3.1.0

3.0.0 | Community Release

New Rule

Cyclomatic Complexity developed by Thomas McCabe Sr, is one of the gold standard for measuring how complex your code is, at it's core, it's counting how many independent paths can your code take. This simple metric has existed on tools such as PMD which can be used on Java & Apex, and as of today, also Flows.

Rule	Description
Cyclomatic Complexity (CyclomaticComplexity)	The number of loops and decision rules, plus the number of decisions. Use a combination of 1) subflows and 2) breaking flows into multiple concise trigger ordered flows, to reduce the cyclomatic complexity within a single flow, ensuring maintainability and simplicity.

Breaking Change

• BREAKING: deprecate old source path option and replace with --files by @junners in #146

Full Changelog: v2.46.0...v3.0.0

2.46.0 | Community Release

What's Changed

• feat: expose flow api name and uri #143 by @junners in #144
  
  

Upcoming 3.0.0 Breaking changes

• --sourcepath | -p will be deprecated

Full Changelog: v2.45.0...v2.46.0

2.45.0 | Community Release

What's new?

• CORE is now an es module instead of common js
• Fix core dependencies and use to new types
• Finally remove oclif/semantic-release! No more failed pipes 🎉

Full Changelog: v2.44.0...v2.45.0