Releases: launchdarkly/ld-find-code-refs
Releases · launchdarkly/ld-find-code-refs
Release list
1.5.0-beta2
check for yaml configuration when initializing cli options (#116) * check for yaml configuration when initializing cli options * return err
1.5.0-beta1
alias fixes for command line wrappers (#112) * update makefile and instructions * make sure alias options are configured for wrappers
1.4.0
[1.4.0] - 2020-03-16
Added
- Added a
--ignoreServiceErrorsoption to the CLI. If enabled, the scanner will terminate with exit code 0 when the LaunchDarkly API is unreachable or returns an unexpected response.
Changed
- ld-find-code-refs now requires go1.13 to build.
1.3.1
[1.3.1] - 2019-09-24
Fixed
- Fixed a regression causing no references to be found when a relative path is supplied to
dir
1.3.0
[1.3.0] - 2019-09-19
Added
- Added a
--outDiroption to the CLI. If provided, code references will be written to a csv file inoutDir. - Added a
--dryRunoption to the CLI. If provided,ld-find-code-refswill scan for code references without sending them to LaunchDarkly. May be used in conjunction with--outDirto output code references data to a csv file instead of sending data to LaunchDarkly.
Fixed
ld-find-code-refsnow supports scanning repositories with a large number of flags using a pagination strategy. Thanks @cuzzasoft!- 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.
1.2.0
[1.2.0] - 2019-08-13
Added
- Added a
--branchoption to the CLI. This lets a branch name be manually specified when the repo is in a detached head state. - Github actions v2 support: the github actions wrapper reads the branch name from
GITHUB_REFand populates thebranchoption with it.
1.1.1
1.1.0
1.0.1
[1.0.1] - 2019-03-12
Changed
- Fixed a potential bug causing
.ldignorepaths to not be detected in some environments. - When
.ldignoreis found, a debug message is logged.