prepare 2.3.1 release (#252)

Bump version and changelog for skip-comment fix, flag API pagination,
and CI/release workflow updates.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> **Prepares the 2.3.1 release** by bumping `internal/version` to
**2.3.1** and adding a **2.3.1** section to `CHANGELOG.md` (fixes and
CI/release notes that ship with this tag).
> 
> Docs and the **`docker/` composite action** now pin the default and
example **`dockerImage`** / action ref from **2.3.0 → 2.3.1** in
`README.md` and `docker/action.yml`.
> 
> The changelog records what 2.3.1 includes: corrected
**`skip-comment`** polarity, LaunchDarkly flag listing on API
**`20240415`** with pagination, Docker Hub publish credentials via
**`release-secrets`/SSM**, and fork PR unit tests on **`pull_request`**
instead of **`pull_request_target`**.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
d75922a. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: cspath1

CHANGELOG.md

@@ -4,10 +4,20 @@
 
 ### Changed
 
+### Fixed
+
+## 2.3.1
+
+### Added
+
+### Changed
+
 - Docker Hub image publish workflow loads credentials via `release-secrets` / SSM (same as other public LD images) instead of repo `DOCKERHUB_*` secrets
+- Run fork pull request unit tests on the unprivileged `pull_request` workflow instead of `pull_request_target`
 
 ### Fixed
 
+- `skip-comment` input had inverted behavior in v2.3.0 (`true` still posted PR comments; `false` skipped)
 - Update flag listing from deprecated REST API version `20220603` to the current version,
   [`20240415`](https://launchdarkly.com/docs/guides/api/api-migration-guide), including pagination support
   for active and archived flags

README.md

@@ -109,13 +109,13 @@ jobs:
       - name: Find flags
         id: find-flags
         # Pin to a release that includes the docker/ entry point and published image (see changelog).
-        uses: launchdarkly/find-code-references-in-pull-request/docker@v2.3.0
+        uses: launchdarkly/find-code-references-in-pull-request/docker@v2.3.1
         with:
           project-key: default
           environment-key: production
           access-token: ${{ secrets.LD_ACCESS_TOKEN }}
           repo-token: ${{ secrets.GITHUB_TOKEN }}
-          dockerImage: your.registry.example/launchdarkly/find-code-references-in-pull-request:2.3.0
+          dockerImage: your.registry.example/launchdarkly/find-code-references-in-pull-request:2.3.1
 ```
 
 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.

docker/action.yml

@@ -55,12 +55,12 @@ inputs:
     description: >-
       Container image to run. Defaults to the public Docker Hub runtime image.
       Set this to your mirrored/proxy image (for example
-      your.registry.example/launchdarkly/find-code-references-in-pull-request:2.3.0).
+      your.registry.example/launchdarkly/find-code-references-in-pull-request:2.3.1).
       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/find-code-references-in-pull-request:2.3.0"
+    default: "launchdarkly/find-code-references-in-pull-request:2.3.1"
 
 outputs:
   any-modified:

internal/version/version.go

@@ -1,3 +1,3 @@
 package version
 
-const Version = "2.3.0"
+const Version = "2.3.1"