Skip to content

prepare 2.3.3 release - #256

Merged
cspath1 merged 1 commit into
mainfrom
cspath/prepare-release-2.3.3
Sep 30, 2026
Merged

cspath1 merged 1 commit into
mainfrom
cspath/prepare-release-2.3.3

Conversation

@cspath1

@cspath1 cspath1 commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Releases two changes that have been sitting on main:

#253 retry rate-limited flag requests, and preserve cancellation and
timeout errors while reading flag responses
#255 pelletier/go-toml/v2 to v2.4.3 (XRAY-1033007)

Patch rather than minor: #253 is retry and error-propagation behaviour, which the contributor filed under Fixed, and no inputs or outputs changed.

Two corrections to repository bookkeeping while here:

The version constant was still 2.3.1. v2.3.2 was tagged directly at the #254 merge commit without a prepare-release commit, so the constant and the metadata pins never moved. Both are now at 2.3.3.

The changelog had no 2.3.2 entry for the same reason, even though v2.3.2 was a real release that Gonfalon pins. Backfilled it from #254.

Also floats the docker/ entry point example on @v2 to match the two root Action examples above it, which already used @v2. That line no longer needs rewriting each release, and the "pin to a release that includes the docker/ entry point" caveat is obsolete now it floats. The dockerImage input keeps an exact tag.


Note

Overview
Prepares the 2.3.3 release by aligning repo metadata with changes already on main, without altering action inputs or outputs in this diff.

CHANGELOG.md adds a 2.3.3 Fixed section (rate-limit retries, preserving cancel/timeout errors on flag reads, go-toml/v2 bump for XRAY-1033007) and backfills 2.3.2 (Go 1.26.8 toolchain and dependency/image pins) after v2.3.2 was tagged without a prepare-release commit.

internal/version/version.go updates the version constant from 2.3.1 to 2.3.3. docker/action.yml default and example dockerImage tags move from 2.3.1 to 2.3.3.

README.md switches the docker entry-point example from a pinned @v2.3.1 to @v2 (matching root action examples) while keeping the mirrored-image example on tag 2.3.3.

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

Releases two changes that have been sitting on main:

  #253  retry rate-limited flag requests, and preserve cancellation and
        timeout errors while reading flag responses
  #255  pelletier/go-toml/v2 to v2.4.3 (XRAY-1033007)

Patch rather than minor: #253 is retry and error-propagation behaviour,
which the contributor filed under Fixed, and no inputs or outputs
changed.

Two corrections to repository bookkeeping while here:

The version constant was still 2.3.1. v2.3.2 was tagged directly at the
#254 merge commit without a prepare-release commit, so the constant and
the metadata pins never moved. Both are now at 2.3.3.

The changelog had no 2.3.2 entry for the same reason, even though
v2.3.2 was a real release that Gonfalon pins. Backfilled it from #254.

Also floats the docker/ entry point example on `@v2` to match the two
root Action examples above it, which already used `@v2`. That line no
longer needs rewriting each release, and the "pin to a release that
includes the docker/ entry point" caveat is obsolete now it floats. The
`dockerImage` input keeps an exact tag.

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:18
@cspath1
cspath1 merged commit 246356c into main Sep 30, 2026
11 of 12 checks passed
@cspath1
cspath1 deleted the cspath/prepare-release-2.3.3 branch September 30, 2026 16:11
@cchu-ld cchu-ld mentioned this pull request Oct 21, 2026
cchu-ld added a commit that referenced this pull request Oct 21, 2026
Prepares the 2.3.4 release, same approach as 2.3.3 in #256.

Ships the Go 1.26.10 toolchain and `golang:1.26.10-alpine` builder pin
from #258, so `crypto/x509` rejects chains through the distrusted
eMudhra intermediates (INC-289, golang/go#82345). No code changes: only
the version constant, the changelog and the `dockerImage` pins.

Users on `@v2` get this once `v2` moves to `v2.3.4`; GitHub builds the
root Action from the Dockerfile on each run.

The `docker/` entry point is still unaffected by this release: Publish
Docker image has failed on every run, and
`launchdarkly/find-code-references-in-pull-request` does not exist on
Docker Hub. The release notes should keep the 2.3.3 caveat.

Release steps after merge: [Releasing the Code References
tools](https://launchdarkly.atlassian.net/wiki/spaces/PD/pages/5437260080/Releasing+the+Code+References+tools).

via LD Research 🤖

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> **Prepares release 2.3.4** by bumping `internal/version.Version` and
aligning user-facing image pins from `2.3.3` to `2.3.4` in `README.md`
and the `docker/` Action’s default `dockerImage`.
> 
> The new **2.3.4** changelog entry documents that the release builds on
**Go 1.26.10** (toolchain and `golang:` builder) so `crypto/x509`
rejects chains through distrusted eMudhra intermediates (INC-289);
**this PR’s diff has no application or `go.mod`/`Dockerfile`
edits**—only version, changelog, and documentation pins.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
3b64368. 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: Claude Opus 5.5 <noreply@anthropic.com>
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