chore: prepare release 2.18.3

CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to the ld-find-code-refs program will be documented in this
 
 ## [Unreleased]
 
+## [2.18.3] - 2026-09-25
+
+### Fixed:
+- the v2.18.2 release archives were published with `2.18.1` filenames, because `make products-for-release` passes `--skip-validate` and goreleaser fell back to the newest visible tag when naming artifacts. The binaries themselves were correct, but the Homebrew formula pointed at `2.18.2` filenames that did not exist, and the misnamed archives collided with the genuine v2.18.1 assets. This release republishes the same code under correctly named artifacts. There are no code changes from 2.18.2 -- the go-toml v2.4.3 bump released there is unchanged
+
 ## [2.18.2] - 2026-09-25
 
 ### Fixed:

build/metadata/github-actions/Dockerfile

@@ -1,4 +1,4 @@
-FROM launchdarkly/ld-find-code-refs-github-action:2.18.2
+FROM launchdarkly/ld-find-code-refs-github-action:2.18.3
 
 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.18.2
+      uses: launchdarkly/find-code-references@v2.18.3
       with:
         accessToken: ${{ secrets.LD_ACCESS_TOKEN }}
         projKey: LD_PROJECT_KEY
@@ -64,11 +64,11 @@ jobs:
         password: ${{ secrets.REGISTRY_TOKEN }}
     - name: LaunchDarkly Code References
       # Pin to a release that includes the docker/ entry point (see changelog).
-      uses: launchdarkly/find-code-references/docker@v2.18.2
+      uses: launchdarkly/find-code-references/docker@v2.18.3
       with:
         accessToken: ${{ secrets.LD_ACCESS_TOKEN }}
         projKey: LD_PROJECT_KEY
-        dockerImage: your.registry.example/launchdarkly/ld-find-code-refs-github-action:2.18.2
+        dockerImage: your.registry.example/launchdarkly/ld-find-code-refs-github-action:2.18.3
 ```
 
 Mirror the public image `launchdarkly/ld-find-code-refs-github-action` into your registry (pin `dockerImage` to the scanner image tag you mirrored; it can lag the Action tag). This entry point requires a Docker CLI on the runner (included on GitHub-hosted `ubuntu-*` runners). Existing workflows that use the root Action do not need to change.
@@ -104,7 +104,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.18.2
+      uses: launchdarkly/find-code-references@v2.18.3
       with:
         accessToken: ${{ secrets.LD_ACCESS_TOKEN }}
         projKey: LD_PROJECT_KEY

build/metadata/github-actions/docker/action.yml

@@ -52,12 +52,12 @@ inputs:
     description: >-
       Container image to run. Defaults to the public Docker Hub image used by
       the root Action. Set this to your mirrored/proxy image (for example
-      your.registry.example/launchdarkly/ld-find-code-refs-github-action:2.18.2).
+      your.registry.example/launchdarkly/ld-find-code-refs-github-action:2.18.3).
       Authenticate to private registries with docker/login-action (or equivalent)
       in a prior step. Requires a runner with a Docker CLI (GitHub-hosted
       ubuntu-* runners include one).
     required: false
-    default: "launchdarkly/ld-find-code-refs-github-action:2.18.2"
+    default: "launchdarkly/ld-find-code-refs-github-action:2.18.3"
 runs:
   using: composite
   steps:

internal/version/version.go

@@ -1,3 +1,3 @@
 package version
 
-const Version = "2.18.2"
+const Version = "2.18.3"