Skip to content

chore: update to ld-find-code-refs 2.18.3 - #68

Merged
cspath1 merged 1 commit into
mainfrom
cspath/update-to-2.18.3
Sep 30, 2026
Merged

cspath1 merged 1 commit into
mainfrom
cspath/update-to-2.18.3

Conversation

@cspath1

@cspath1 cspath1 commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

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.


Note

Overview
Bumps the underlying scanner container from 2.18.1 to 2.18.3 in the root Dockerfile and in the docker composite action’s default dockerImage (plus README mirror example).

README workflow samples now reference launchdarkly/find-code-references@v2 and …/docker@v2 instead of @v2.18.1, so copy-pasted workflows no longer point at a non-existent Action tag; mirrored-registry examples still use an explicit 2.18.3 image tag.

Reviewed by Cursor Bugbot for commit 358dbb9. Bugbot is set up for automated code reviews on this repo. Configure here.

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>
@cspath1
cspath1 requested a review from a team as a code owner September 30, 2026 15:17
@cspath1
cspath1 merged commit 5d95481 into main Sep 30, 2026
4 of 5 checks passed
@cspath1
cspath1 deleted the cspath/update-to-2.18.3 branch September 30, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants