2.1.1

What's Changed

Bug Fixes

• Fix race condition in cache implementation (@alexevanczuk, #183)

Full Changelog: v2.1.0...v2.1.1

2.1.0

What's Changed

New Features

• Add caching to speed up bin/packwerk check and bin/packwerk update-deprecations by 85-90% by @alexevanczuk in #169
• Memoize package_from_path to improve performance by @alexevanczuk in #175

Bug Fixes

• Correctly handle empty lambda in constant assigment (@exterm, #171)
• Reject ambiguous specification of private constants (@timbogit, #163)

New Contributors

• @timbogit made their first contribution in #163

Full Changelog: v2.0.0...v2.1.0

2.0.0

What's Changed

Breaking changes

• Removed all application config caches; inflections and load paths are now read directly from the application. This should make setting up and maintaining packwerk on your project much easier. See UPGRADING.md for details. (@alexevanczuk)
• Removed deprecated packwerk update command; use packwerk update-deprecations instead. (@alexevanczuk)

Thank you so much for pushing this through, Alex!

1.4.0

What's Changed

New Features

• add --packages= parameter to the check command to scan by package instead of by folder, ignoring nested packages (#134, @shageman)
• (re)introduced support for spring (#153, @alexevanczuk)

Bug Fixes

• allow running packwerk outside of application bundle (#152, @jordanstephens)
• Fix #103 - Packwerk.yml exclude option does not work (#155, @jordanstephens)

1.3.2

What's Changed

Bug fixes

• Fix bug in the update-deprecations command when the deprecation file has conflicts.
• Ignore duplicated load paths

1.3.1

What's Changed

Bug fixes

• Fix usage of Object#present? that was not present in the library

1.3.0

What's Changed

New features

• Booting changes. Should only boot the Rails application when needed. Check #128 for more info.
• Combined check and detect-stale-violations. Check #131 for more info.

Bug fixes

• Constants under the public path in the root package were not correctly identified as public.

Breaking changes

• Possibly breaking if spring was used with your project from the booting changes.
• packwerk check can fail if the violations are stale or the "No offenses detected" string was checked in the output.

1.2.0

What's Changed

New Features

• Execute Packwerk commands in parallel.
• Add support to CLI for specifying a custom offenses formatter.
• Lazy load constant only when needed to avoid doing unnecessary work when loading the gem.

1.1.3

What's Changed

Bug Fixes

• #106 Require fileutils to fix uninitialized constant error (#107, @jaydorsey)
• Support Ruby 3.0 and Rails 7 (#110)

1.1.2

What's Changed

New Features

• Give more helpful error message if privatized constant can not be resolved #89 (@exterm)

Bug Fixes

• Convert autoload paths to strings to resolve a Sorbet type violation #91 (@steve-low)
• Improve types on interface implementations for stronger Sorbet type checking #92 (@samuelgiles)
• Extract an interface out of PackWerk::OutputStyles and enforce stronger type checking #93 (@samuelgiles)