Skip to content

Releases: launchdarkly/ld-find-code-refs

1.4.0

16 Mar 23:06
68d6d49
Compare
Choose a tag to compare

[1.4.0] - 2020-03-16

Added

  • Added a --ignoreServiceErrors 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.

Changed

  • ld-find-code-refs now requires go1.13 to build.

1.3.1

24 Sep 20:56
6d23f01
Compare
Choose a tag to compare

[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

19 Sep 21:56
Compare
Choose a tag to compare

[1.3.0] - 2019-09-19

Added

  • Added a --outDir option to the CLI. If provided, code references will be written to a csv file in outDir.
  • Added a --dryRun option to the CLI. If provided, ld-find-code-refs will scan for code references without sending them to LaunchDarkly. May be used in conjunction with --outDir to output code references data to a csv file instead of sending data to LaunchDarkly.

Fixed

  • ld-find-code-refs now 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

13 Aug 17:16
c8460a5
Compare
Choose a tag to compare

[1.2.0] - 2019-08-13

Added

  • Added a --branch option 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_REF and populates the branch option with it.

1.1.1

11 Apr 21:30
f68e960
Compare
Choose a tag to compare

[1.1.1] - 2019-04-11

Fixed

  • ld-find-code-refs will no longer exit with a fatal error when Git credentials have not been configured (required for branch cleanup). Instead, a warning will be logged.

1.1.0

11 Apr 21:28
ec95a0b
Compare
Choose a tag to compare

[1.1.0] - 2019-04-11

Added

  • ld-find-code-refs will now remove branches that no longer exist in the git remote from LaunchDarkly.

1.0.1

12 Mar 20:41
Compare
Choose a tag to compare

[1.0.1] - 2019-03-12

Changed

  • Fixed a potential bug causing .ldignore paths to not be detected in some environments.
  • When .ldignore is found, a debug message is logged.

1.0.0

21 Feb 22:38
c59cd70
Compare
Choose a tag to compare

[1.0.0] - 2019-02-21

Official release

0.7.0

15 Feb 18:50
d89f53b
Compare
Choose a tag to compare

Master

[0.7.0] - 2019-02-15

  • The command-line docker image now specifies ld-find-code-refs as the entrypoint. The docker image may now be run as docker run launchdarkly/ld-find-code-refs -accessToken="api-xxx"...
  • The command-line docker image now specifies ld-find-code-refs as the entrypoint. See our documentation for instructions on running ld-find-code-refs via docker.

0.6.0

11 Feb 23:43
24bed11
Compare
Choose a tag to compare

[0.6.0] - 2019-02-11

Added

  • Added a new command line argument, version. If provided, the current ld-find-code-refs version number will be logged, and the scanner will exit with a return code of 0.
  • The debug option is now available to the CircleCI orb.
  • Added support for parsing .ldignore files specified in the root directory of the scanned repository. .ldignore may be used to specify a pattern (compatible with the .gitignore spec: https://git-scm.com/docs/gitignore#_pattern_format) for files to exclude from scanning.

Changed

  • The internal API for specifying the default git branch (defaultBranch) has been changed. The defaultBranch argument on earlier versions of ld-find-code-refs will no longer do anything.

Fixed

  • ld-find-code-refs will no longer error out if an unknown error occurs when scanning for code reference hunks within a file. Instead, an error will be logged.