This repository was archived by the owner on Oct 7, 2025. It is now read-only.
Releases: Flow-Scanner/lightning-flow-scanner-vsce
Releases · Flow-Scanner/lightning-flow-scanner-vsce
3.31.0 | Community Release
3.30.0 | Community Release
Full Changelog: v3.29.0...v3.30.0
3.29.0 | Community Release
What's Changed
New & Changed Rules:
| Rule (Configuration ID) | Description |
|---|---|
Same Record Field Updates (SameRecordFieldUpdates) |
Much like triggers, before contexts can update the same record by accessing the trigger variables $Record without needing to invoke a DML. |
Trigger Order (TriggerOrder) |
Guarantee your flow execution order with the Trigger Order property introduced in Spring '22 |
Missing Fault Path (MissingFaultPath) |
At times, a flow may fail to execute a configured operation as intended. By default, the flow displays an error message to the user and notifies the admin who created the flow via email. However, you can customize this behavior by incorporating a Fault Path. |
- feat(core): udpate core to 4.7.0 by @junners in #140
- chore(log): add log manager for tracing purposes by @junners in #141
- chore(core): update core to 4.8.0 trigger order rule by @junners in #142
Full Changelog: v3.27.0...v3.29.0
3.28.0 | Community Release
What's Changed
New & Changed Rules:
| Rule (Configuration ID) | Description |
|---|---|
Same Record Field Updates (SameRecordFieldUpdates) |
Much like triggers, before contexts can update the same record by accessing the trigger variables $Record without needing to invoke a DML. |
Missing Fault Path (MissingFaultPath) |
At times, a flow may fail to execute a configured operation as intended. By default, the flow displays an error message to the user and notifies the admin who created the flow via email. However, you can customize this behavior by incorporating a Fault Path. |
- feat(core): udpate core to 4.7.0 by @junners in #140
- chore(log): add log manager for tracing purposes by @junners in #141
Full Changelog: v3.27.0...v3.28.0
3.27.0 | Community Release
3.26.0 | Community Release
3.25.0 | Community Release
3.24.0 | Community Release
What's Changed
Full Changelog: v3.23.0...v3.24.0
3.23.0 | Community Release
What's Changed
Housekeeping release and keep our application up-to-date with latest industry standards!
- fix(deps): bump typescript from 5.5.3 to 5.5.4 by @dependabot in #111
- fix(deps): bump postcss from 8.4.39 to 8.4.40 by @dependabot in #112
- fix(deps): bump rollup from 4.19.0 to 4.19.2 by @dependabot in #116
- chore: bump all dependencies to latest by @junners in #117
- chore: update core 3.22 by @junners in #118
Full Changelog: v3.22.0...v3.23.0
3.22.0 | Community Release
What's Changed
We're back again with another release! This time we're adding a new rule that was launched for summer 24 orgs
| Rule (Configuration ID) | Description |
|---|---|
Unsafe Running Context (UnsafeRunningContext) |
This flow is configured to run in System Mode without Sharing. This system context grants all running users the permission to view and edit all data in your org. Running a flow in System Mode without Sharing can lead to unsafe data access. |
Full Changelog: v3.21.0...v3.22.0