2.4.0

[2.4.0] - 2021-11-22

Changed:

• Performance improvements around searching for flags and aliases in the code base. Including changing search to use Aho-Corasick algorithm to find flags in file.
• If --dryRun is set, extinctions will not be attempted.

Added:

• --allowTags which allows Code Refs to run against a tag instead of the branch.

Fixed:

• Bug where alias filepattern's were not being validated. This meant ld-find-code-refs would run but if that file did not exist no aliases were generated.

2.2.3

[2.2.1] - 2021-04-27

[2.2.2] - 2021-04-27

• repoName is now a supported configuration option for
  github action
  and bitbucket pipes 🎉.
  This is especially useful for a monorepo where multiple yaml configurations exist, each mapping to its own
  LD project key.
• repoName is now a supported configuration option for github action and bitbucket pipes 🎉. This is especially useful for a monorepo where multiple yaml configurations exist, each mapping to its own LD project key.

2.2.2

[2.2.2] - 2021-04-27

• repoName is now a supported configuration option for github action and bitbucket pipes 🎉. This is especially useful for a monorepo where multiple yaml configurations exist, each mapping to its own LD project key.

2.1.0

[2.1.0]

Added

• ld-find-code-refs will now scan for archived flags.

2.0.1

[2.0.1] - 2020-10-05

Fixed

• Fixes a bug causing ld-find-code-refs to scan non-regular files, like symlinks. Thanks @d3d-z7n!

2.0.0

[2.0.0] - 2020-08-13

ℹ️ This release includes breaking changes to the command line tool. If you experience errors or unexpected behavior after upgrading, be sure to read these changelog notes carefully to make adjustments for any breaking changes.

Added

• Most command line flags can now be specified in a YAML file located in the .launchdarkly/coderefs.yaml subdirectory of your repository. docs
  • The following options cannot be specified in YAML, and must be set using the command line or as environment variables:
    • --dir / LD_DIR
    • --accessToken / LD_ACCESS_TOKEN
• All command line flags can now be specified as environment variables. docs
• When flags with no code references are detected, ld-find-code-refs will search Git commit history to detect when the last reference to a feature flag was removed. Use the --lookback command line flag to configure the number of commits you would like to search. The lookback will start at the current commit and will review up to the last n commits to find the last reference of the flag. The default is 10 commits.
• Added support for scanning non-git repositories. Use the --revision flag to specify your repository version number.
• Added the prune sub-command to delete stale code reference data from LaunchDarkly manually by providing a list of branch names as arguments. example: ld-find-code-refs prune [flags] "branch1" "branch2"
• The GitHub actions wrapper now supports the pull_request event

Fixed

• Exclude negations in .ldignore (lines beginning with an exclamation mark) now correctly include files.

Changed

• Command line arguments names have been improved. Now, a flag specified with a single dash indicates a shorthand name, while 2 dashes indicate the longform name. Some existing configurations may be invalid, see ld-find-code-refs --help for details.
• The default delimiters (single quotes, double quotes and backticks) can now be disabled in the coderefs.yaml configuration. docs. Delimiters can no longer be specified using command line flags or environment variables. If you use additional delimiters, or would like to disable delimiters completely, use YAML configuration instead.

Removed

• The exclude command-line option has been removed. Use the .ldignore file instead.
• ld-find-code-refs no longer requires the silver searcher (ag) as a runtime dependency.

2.0.0-preview1

[2.0.0] - prerelease

Added

• Most command line flags can now be specified in a YAML file located in the .launchdarkly/coderefs.yaml subdirectory of your repository. The following options must be set using the command line or as environment variables:
  • --dir / LD_DIR
  • --accessToken / LD_ACCESS_TOKEN
• The default delimiters (single/double quotes and backticks) can now be disabled by setting the following YAML option in .launchdarkly/coderefs.yaml:

  delimiters:
    defaultsDisabled: true

• All command line flags can now be specified as environment variables.
• Added support for scanning non-git repositories. Use the --revision flag to specify your repository version number.
• Added the prune sub-command to delete stale code reference data from LaunchDarkly manually by providing a list of branch names as arguments. example: ld-find-code-refs prune [flags] "branch1" "branch2"

Fixed

• Exclude negations in .ldignore (lines beginning with an exlamation mark) now correctly include files.

Changed

• The command line tool has been changed for improved ergonomics when configuring options using the command line. Some existing configurations may be invalid, see ld-find-code-refs --help for details.

Removed

• The exclude command-line option has been removed. Use the .ldignore file instead.
• Additional delimiters can no longer be specified using command line flags or environment variables. If you use additional delimiters, or would like to disable delimiters completely, use the YAML configuration described above.
• ld-find-code-refs no longer requires the silver searcher (ag) as a runtime dependency.

1.5.1

[1.5.1] - 2020-05-22

Added

• Added support for specifying a custom default branch for the GitHub actions and Bitbucket pipes wrappers.

1.5.0

[1.5.0] - 2020-05-11

Added

• Added the ability to configure flag alias detection using a YAML configuration. See the README for instructions.

Fixed

• Improved logging around limitations.
• Fixed an edge case where false positives might be picked up for flag keys containing regular expression characters.

1.5.0-beta3

Support specifying multiple alias patterns (#119)

* allow for specifying multiple alias patterns

* update readme