chore: update to ld-find-code-refs 2.16.0 - #64
Merged
Merged
Conversation
Point the action at the 2.16.0 image and update the pinned version in the README examples. Copied from build/metadata/github-actions in launchdarkly/ld-find-code-refs, which is the source of truth for these files. 2.16.0 includes the fix for out-of-memory failures when generating filepattern aliases on large repositories. Normally publish_gha does this during the release, but that target has been commented out since January 2026, so this release is being done by hand.
cspath1
approved these changes
Jul 28, 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
2 participants
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.
Summary
Points the action at
ld-find-code-refs2.16.0, which was released today: https://github.com/launchdarkly/ld-find-code-refs/releases/tag/v2.16.0The headline fix is out-of-memory failures when generating filepattern aliases on large repositories (ld-find-code-refs#604). On a repo with ~80MB of matched source and ~160 flags, the scan was OOM-killed before producing any output. Users pinned to
@v2or@v2.14.0are still hitting that until this merges.Requested in ld-find-code-refs#607.
What changed
DockerfileFROM launchdarkly/ld-find-code-refs-github-action:2.14.0→:2.16.0README.md@v2.16.0Both files were copied verbatim from
build/metadata/github-actions/inlaunchdarkly/ld-find-code-refs, which is the source of truth for them.action.ymlwas already identical and is untouched.Why this is a manual PR
scripts/release/targets/gha.shnormally does this automatically during the upstream release: it copies the metadata files here, commits, tags, force-movesv2, and creates the release. That target (publish_gha) has been commented out since ld-find-code-refs#593 in January 2026, so it's being done by hand.Direct pushes to
mainare rejected by rulesets, which is also why the upstream release workflow can't complete on its own — hence the PR rather than a bot push.After merge
v2.16.0at the merge commit.v2tag so@v2users get the fix.v2.16.0release.Note on version numbering
Jumps 2.14.0 → 2.16.0. 2.15.0 was never released — an incomplete release run in January 2026 published its Docker images and then failed, leaving no tag or release behind, so that number was already burned.