4.1.0 | Community Release

What's Changed

Breaking Change

We've doubled down on developer experience and made our app even easier to integrate! Engineers can now just import('lightning-flow-scanner-core') as a dependency, no more importing of out directory!

End users can now enjoy a snappier response from all the apps as the overall package size is reduced from ~1.4MB to ~400 KB that's a whole megabyte gone!

Tests are also now up-to-date with industry standards and runs on Mocha 10, Chai 5, Ts-node latest on a commonjs project!

Releases can now be done with 2 clicks from Github Actions

• feat: migrate to mocha 5 by @junners in #115
• Feature/v4.0.0 by @junners in #116
• chore: add push tag as an example by @junners in #117

Full Changelog: v3.22.0...v4.1.0

4.0.0 | Community Release

What's Changed

Breaking Change

We've doubled down on developer experience and made our app even easier to integrate! Engineers can now just import('lightning-flow-scanner-core') as a dependency, no more importing of out directory!

End users can now enjoy a snappier response from all the apps as the overall package size is reduced from ~1.4MB to ~400 KB that's a whole megabyte gone!

Tests are also now up-to-date with industry standards and runs on Mocha 10, Chai 5, Ts-node latest on a commonjs project!

• feat: migrate to mocha 5 by @junners in #115
• Feature/v4.0.0 by @junners in #116
• chore: add push tag as an example by @junners in #117

Full Changelog: v3.22.0...v4.0.0

3.22.0 | Community Release

What's Changed

Housekeeping release and keep our application up-to-date with the current industry standards!

• fix(deps): bump uglify-js from 3.19.0 to 3.19.1 by @dependabot in #111
• fix(deps): bump husky from 9.1.1 to 9.1.4 by @dependabot in #113
• fix(deps): bump typescript-eslint from 7.17.0 to 8.0.0 by @dependabot in #112
• fix(deps): bump eslint from 8.57.0 to 9.8.0 by @dependabot in #114

Full Changelog: v3.21.0...v3.22.0

3.21.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.

• test: refactor tests and improve compiler search without recursion by @junners in #107
• test: small changes to compiler to reduce complexity by @junners in #108
• build: update workspace repository configuration by @junners in #109
• feat: new rule unsafe running context by @junners in #110

Full Changelog: v3.20.0...v3.21.0

3.20.0 | Community Release

What's Changed

We're back with a new release! We've fixed an issue with our compiler not recognizing a connected path for asynchronous flows. Our approach includes a recursive tree traversal.

• fix(deps): bump @types/node from 20.13.0 to 20.14.9 by @dependabot in #101
• fix(deps): bump tslib from 2.6.2 to 2.6.3 by @dependabot in #102
• fix(deps): bump typescript from 5.5.2 to 5.5.3 by @dependabot in #103
• License Changes and Change Logic to visit elements by @junners in #105

Full Changelog: v3.19.0...v3.20.0

3.19.0 | Community Release

What's Changed

Housekeeping changes~ keeping all the packages up to date! Stay tuned for new rules and new releases!

• fix(deps): bump mocha and @types/mocha by @dependabot in #96
• fix(deps): bump typescript-eslint from 7.11.0 to 7.14.1 by @dependabot in #97
• fix(deps): bump typescript from 5.4.5 to 5.5.2 by @dependabot in #99

Full Changelog: v3.18.0...v3.19.0

3.18 | Lightning Flow Scanner Core Module Community Release

Version 3.18 minor fixes to Inactive Flow:

Rule (Configuration ID)	Description
Inactive Flow (InactiveFlow)	Like cleaning out your closet: deleting unused flows is essential. Inactive flows can still cause trouble, like accidentally deleting records during testing, or being activated as subflows within parent flows.

Thank you for your contribution and continuous support @k-capehart 🚀

Community Release | Lightning Flow Scanner Core Module Update - Version 3.17

We're excited to announce the latest update to the Lightning Flow Scanner Core Module. This is the first community-led release, which focuses on internal improvements and streamlining contributor's experience.

Here's what's new

• Internal improvements in readability and consistency: ✅ We've onboarded tools to standardize formatting across the files
• Automations automations automations: 🤖 🤖 Streamlined and consistent way to publish the core module to npm. Thank you so much @nvuillam for the wonderful contribution!
• Security Patches & Fixes: 📝 🔐 🙈 We've updated a significant amount of outdated dependencies to improve security, removed deprecated dependencies and lower the barrier to contribution by adding new documentation for e2e tests

Adds parse function

Lightning Flow Scanner Core Module Update - Version 3.16

We're excited to announce the latest update to the Lightning Flow Scanner Core Module, designed to streamline your development workflow. Here's what's new:

1. Consistent Parsing Across Platforms: We've unified parsing modules across platforms, ensuring consistent parsing of flows. This enhancement improves compatibility and developer workflows.
2. Improved Developer Experience: Say goodbye to xml2js! We've directly integrated xmlbuilder2 into the core module, enabling direct manipulation of Flow XML files. Utilize xmlbuilder2's convert function for seamless XML-to-JavaScript object transformation, simplifying parsing within the core module.
3. Robust Error Handling: Experience smoother development processes with our robust error handling. We've implemented resilient mechanisms for graceful handling of parsing errors.

Stay tuned:
These enhancements open possibilities for launching LWC components and GitHub Actions. Follow our project page to stay updated on their release.

New Rule: Inactive Flow

Version 3.11 now includes 1 New Default Rule:

Rule (Configuration ID)	Description
Inactive Flow (InactiveFlow)	Like cleaning out your closet: deleting unused flows is essential. Inactive flows can still cause trouble, like accidentally deleting records during testing, or being activated as subflows within parent flows.