feat: [REL-8033] Prepare release of version 2.14.0 (#563)

Our release.yml GHA has managed to successfully release the Homebrew
Formula and our three CI coderefs tools (Github Action, CircleCI Orb and
BitBucket Pipe), but it's consistently having issues with the Github
release. Those newly-released CI tools point to the `v2.14.0` tag of
this repo, which doesn't exist yet. So there is some urgency to get the
Github release out as quickly as we can. Since we can't seem to get
around the branch protection issues we've run into, we've decided to
release version 2.14.0 manually, and then rework the GHA to make use of
Release Please, which doesn't require pushes to the main branch. This PR
will prepare the necessary updates for the release, and I'll create the
binaries locally and create the tag and the release manually once this
is merged.
<!-- ld-jira-link -->
---
Related Jira issue: [REL-8033: Release a new version of
`ld-find-code-refs` and `find-code-references`
GHA](https://launchdarkly.atlassian.net/browse/REL-8033)
<!-- end-ld-jira-link -->

Author: blaqbern

CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to the ld-find-code-refs program will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
 
+## [2.14.0] - 2025-08-12
+### Added:
+- `--skipArchivedFlags` option to instruct the tool to ignore any flag keys it finds from archived flags
+
+### Changed:
+- replaced the stdlib `regexp` with `go-re2` for improved regexp compilation and pattern matching
+- now using caching to optimize file globbing and regex compilation
+- move off of legacy `olekukonko/tablewriter` and onto `v1.x`
+- updated to the latest version of the LaunchDarkly API (17.2.0)
+
+### Fixed:
+- `subdirectory` option now works with `projects[*].dir` configuration, and produces correct "View in source" links in the LD UI
+
 ## [2.13.0] - 2024-12-18
 ### Added:
 - `subdirectory` option to set path to `.launchdarkly/coderefs.yaml` config file if not located in the root, in order to support monorepo subdirectories.

build/metadata/bitbucket/README.md

@@ -5,7 +5,7 @@ Job for finding and sending feature flag code references to LaunchDarkly
 Add the following snippet to the script section of your `bitbucket-pipelines.yml` file:
 
 ```yaml
-- pipe: launchdarkly/ld-find-code-refs-pipe:2.13.0
+- pipe: launchdarkly/ld-find-code-refs-pipe:2.14.0
   environment:
     LD_ACCESS_TOKEN: "<string>"
     LD_PROJ_KEY: "<string>" # Required unless using 'projects' block in configuration file then it must be omitted.
@@ -51,7 +51,7 @@ A LaunchDarkly personal access token with writer-level access, or access to the
 Minimal configuration:
 ```yaml
 script:
-  - pipe: launchdarkly/ld-find-code-refs-pipe:2.13.0
+  - pipe: launchdarkly/ld-find-code-refs-pipe:2.14.0
     environment:
       LD_ACCESS_TOKEN: $LD_ACCESS_TOKEN
       LD_PROJ_KEY: $LD_PROJ_KEY
@@ -60,7 +60,7 @@ script:
 Configuration sending 3 context lines to LaunchDarkly:
 ```yaml
 script:
-  - pipe: launchdarkly/ld-find-code-refs-pipe:2.13.0
+  - pipe: launchdarkly/ld-find-code-refs-pipe:2.14.0
     environment:
       LD_ACCESS_TOKEN: $LD_ACCESS_TOKEN
       LD_PROJ_KEY: $LD_PROJ_KEY

build/metadata/bitbucket/pipe.yml

@@ -1,5 +1,5 @@
 name: LaunchDarkly Code References
-image: launchdarkly/ld-find-code-refs-bitbucket-pipeline:2.13.0
+image: launchdarkly/ld-find-code-refs-bitbucket-pipeline:2.14.0
 category: Feature flagging
 description: Job for finding and sending feature flag code references to LaunchDarkly
 repository: https://bitbucket.org/launchdarkly/ld-find-code-refs-pipe

build/metadata/github-actions/Dockerfile

@@ -1,4 +1,4 @@
-FROM launchdarkly/ld-find-code-refs-github-action:2.13.0
+FROM launchdarkly/ld-find-code-refs-github-action:2.14.0
 
 LABEL com.github.actions.name="LaunchDarkly Code References"
 LABEL com.github.actions.description="Find references to feature flags in your code."

build/metadata/github-actions/README.md

@@ -28,7 +28,7 @@ jobs:
       with:
         fetch-depth: 11 # This value must be set if the lookback configuration option is not disabled for find-code-references. Read more: https://github.com/launchdarkly/ld-find-code-refs#searching-for-unused-flags-extinctions
     - name: LaunchDarkly Code References
-      uses: launchdarkly/find-code-references@v2.13.0
+      uses: launchdarkly/find-code-references@v2.14.0
       with:
         accessToken: ${{ secrets.LD_ACCESS_TOKEN }}
         projKey: LD_PROJECT_KEY
@@ -71,7 +71,7 @@ jobs:
       with:
         fetch-depth: 11 # This value must be set if the lookback configuration option is not disabled for find-code-references. Read more: https://github.com/launchdarkly/ld-find-code-refs#searching-for-unused-flags-extinctions
     - name: LaunchDarkly Code References
-      uses: launchdarkly/find-code-references@v2.13.0
+      uses: launchdarkly/find-code-references@v2.14.0
       with:
         accessToken: ${{ secrets.LD_ACCESS_TOKEN }}
         projKey: LD_PROJECT_KEY

build/package/circleci/orb.yml

@@ -9,7 +9,7 @@ examples:
     usage:
       version: 2.1
       orbs:
-        launchdarkly: launchdarkly/ld-find-code-refs@2.13.0
+        launchdarkly: launchdarkly/ld-find-code-refs@2.14.0
       workflows:
         main:
           jobs:
@@ -23,7 +23,7 @@ examples:
     usage:
       version: 2.1
       orbs:
-        launchdarkly: launchdarkly/ld-find-code-refs@2.13.0
+        launchdarkly: launchdarkly/ld-find-code-refs@2.14.0
       workflows:
         main:
           jobs:
@@ -38,7 +38,7 @@ examples:
     usage:
       version: 2.1
       orbs:
-        launchdarkly: launchdarkly/ld-find-code-refs@2.13.0
+        launchdarkly: launchdarkly/ld-find-code-refs@2.14.0
       workflows:
         main:
           jobs:
@@ -107,7 +107,7 @@ jobs:
         type: integer
         default: 10
     docker:
-      - image: launchdarkly/ld-find-code-refs:2.13.0
+      - image: launchdarkly/ld-find-code-refs:2.14.0
         entrypoint: sh
     steps:
       - checkout:

internal/version/version.go

@@ -1,3 +1,3 @@
 package version
 
-const Version = "2.13.0"
+const Version = "2.14.0"