chore: update to ld-find-code-refs 2.18.3 - #68
Merged
Merged
Conversation
Picks up 2.18.3, which carries the pelletier/go-toml/v2 v2.4.3 bump (XRAY-1033007) on top of the toolchain pin and dependency work from 2.18.0. Scanner image ld-find-code-refs-github-action:2.18.3 is published on Docker Hub, and the 2.18.3 release binary was verified to report go1.26.8 with go-toml v2.4.3. Also switches the usage examples from an exact Action tag to `@v2`. The 2.18.1 sync rewrote those lines to `@v2.18.1`, but this repo was tagged v2.18.0, so the examples have been pointing at a tag that does not exist and 404 when copy-pasted. Floating on `@v2` fixes them and removes the need to rewrite them each release -- moving the v2 tag is what delivers a new scanner to consumers regardless. The prose in this README already described the root Action as `@v2`. The `dockerImage` input keeps an exact tag; there is no floating `:2` tag on Docker Hub for the scanner image. Synced from ld-find-code-refs build/metadata/github-actions. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
LindseyB
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Picks up 2.18.3, which carries the pelletier/go-toml/v2 v2.4.3 bump (XRAY-1033007) on top of the toolchain pin and dependency work from 2.18.0. Scanner image ld-find-code-refs-github-action:2.18.3 is published on Docker Hub, and the 2.18.3 release binary was verified to report go1.26.8 with go-toml v2.4.3.
Also switches the usage examples from an exact Action tag to
@v2. The 2.18.1 sync rewrote those lines to@v2.18.1, but this repo was tagged v2.18.0, so the examples have been pointing at a tag that does not exist and 404 when copy-pasted. Floating on@v2fixes them and removes the need to rewrite them each release -- moving the v2 tag is what delivers a new scanner to consumers regardless. The prose in this README already described the root Action as@v2.The
dockerImageinput keeps an exact tag; there is no floating:2tag on Docker Hub for the scanner image.Synced from ld-find-code-refs build/metadata/github-actions.
Note
Overview
Bumps the underlying scanner container from 2.18.1 to 2.18.3 in the root
Dockerfileand in thedockercomposite action’s defaultdockerImage(plus README mirror example).README workflow samples now reference
launchdarkly/find-code-references@v2and…/docker@v2instead of@v2.18.1, so copy-pasted workflows no longer point at a non-existent Action tag; mirrored-registry examples still use an explicit2.18.3image tag.Reviewed by Cursor Bugbot for commit 358dbb9. Bugbot is set up for automated code reviews on this repo. Configure here.