Conversation
Options.AllowStale and the allow_stale URL parameter were parsed and validated but never copied into driver.Config, so stale reads were never requested. Forward the field through OpenVariable and add a public-API regression test. Closes #26 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The consecutive-failure counter driving exponential backoff was reset only on the returning paths, not on the poll-again paths that loop after a successful Get. A transport error following a healthy but unchanged poll therefore escalated the backoff instead of restarting at 1s. Reset the counter after any successful Get. Closes #27 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Repair the unbalanced code fences so the install snippet and command list render correctly; the `# task:` / `# git-cliff:` comments now live inside the install block (refs #30). - Point the golangci-lint install at v2.12.2 to match `.golangci.yml` (version: "2"), the `golangci-lint fmt` task, and CI (refs #29). - State the real Go floor (1.25, from the go.mod directive) instead of 1.26, and drop the false "dependencies pull the floor up" claim (refs #28). - Describe what `task ci` actually does rather than claiming it pins the toolchain to a minimum Go that nothing enforces (refs #31). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
go.mod declares go 1.25.0 and no dependency raises the floor; AGENTS.md claimed 1.26 in two places (refs #28). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…ff-reset fix: forward AllowStale and reset backoff after a successful poll
docs: fix Go version inconsistencies and README Development section
Tagged releases now package a deterministic source archive (runtimevar-consul-<tag>.tar.gz) plus SHA256SUMS, attach them to the GitHub Release, and generate Sigstore-signed SLSA v1.0 provenance for the archive via actions/attest-build-provenance. This satisfies SLSA Build L1 (scripted build + provenance); the hosted runner and signed, non-falsifiable provenance also cover the bulk of L2. Permissions are scoped per-job (id-token + attestations write added for keyless signing). SECURITY.md documents verification via `gh attestation verify`. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
ci: add SLSA build provenance to releases
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #35 +/- ##
=======================================
Coverage 98.08% 98.08%
=======================================
Files 6 6
Lines 157 157
=======================================
Hits 154 154
Misses 2 2
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
1 participant
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.
Release v0.2.1 — patch release (two
fix:commits since v0.2.0; nofeat:, no breaking changes).Changelog (user-facing)
Fixed
Also included (excluded from CHANGELOG per
cliff.toml)Notable
v0.2.0 advertised "Support AllowStale in Options", but that option never reached Consul. v0.2.1 is the release where stale reads actually work (#26).
Post-merge steps (per README release flow)
main: regenerateCHANGELOG.mdfor v0.2.1 and commit.v0.2.1onmainand push →release.ymlpublishes the release with the source archive +SHA256SUMS+ SLSA provenance.gh attestation verify.mainback intodevel.Merge with a merge commit titled
release: v0.2.1.