Releases: launchdarkly/find-code-references
Releases · launchdarkly/find-code-references
v2.2.2-rc.1 (previously v10)
[v10] - 2021-05-07
Added
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.
v2.2.2 (previously v12)
[v12] - 2021-08-24
Removed
- Removed
githubToken
config option and any documentation mentioning it. This config option was obsolete. This action doesn't require a github token. It should always be used in combination with thecheckout
github action.
v2.1.0 (previously v9)
[v9] - 2021-01-13
Added
ld-find-code-refs
will now scan for archived flags.
v2.0.1 (previously v8)
[v8] - 2020-10-05
Fixed
- Fixes a bug causing
ld-find-code-refs
to scan non-regular files, like symlinks.
[v2.0.0] (previously v7) - 2020-08-13
ℹ️ This release includes breaking changes to the GitHub action. 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
- When flags with no code references are detected, the action will search Git commit history to detect when the last reference to a feature flag was removed. Use the
lookback
parameter 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. Your Git checkout must include thefetch-depth
parameter (see the example) for this new functionality to work. - The
pull_request
event is now supported.
Fixed
- Exclude negations in
.ldignore
(lines beginning with an exclamation mark) now correctly include files.
Removed
- The
exclude
configuration option has been removed. Use the.ldignore
file instead. https://github.com/launchdarkly/ld-find-code-refs/blob/master/docs/CONFIGURATION.md#ignoring-files-and-directories - The
delimiters
configuration option has been removed. Use the.launchdarkly/coderefs.yaml
configuration file instead. https://github.com/launchdarkly/ld-find-code-refs/blob/master/docs/CONFIGURATION.md#delimiters
v1.5.0 (previously v6)
[v6] - 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.
v1.4.0-rc.1 (previously v4)
[v4] - 2020-03-19
Added
- Added a
LD_IGNORE_SERVICE_ERRORS
option to the CLI. If enabled, the scanner will terminate with exit code 0 when the LaunchDarkly API is unreachable or returns an unexpected response.
v1.4.0 (previously v5)
[v5] - 2020-03-19
Added
- All configuration options for
ld-find-code-references
are now available as inputs
Changed
- Existing inputs have been renamed to be camelCased.
GITHUB_TOKEN -> githubToken
LD_ACCESS_TOKEN -> accessToken
LD_PROJ_KEY -> projKey
v1.3.0 (previously v3)
[v3] - 2019-09-20
Fixed
ld-find-code-refs
now supports scanning repositories with a large number of flags using a pagination strategy.- Delimiters will now always be respected when searching for flags referenced in code. This fixes a bug causing references for certain flag keys to match against other flag keys that are substrings of the matched reference.
v1.2.0 (previously v2)
[v2] - 2019-08-13
Fixed:
- Fixes an issue where the code references tool would break because of being in a detached head state from the checkout action (#1).