Skip to content

Release v0.6.2 - #31

Merged
jbrazda merged 4 commits into
mainfrom
dev
Nov 2, 2026
Merged

jbrazda merged 4 commits into
mainfrom
dev

Conversation

@jbrazda

@jbrazda jbrazda commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Patch release v0.6.2: fixes release plan reporting every non-Connection asset as missing in a target (regression since v0.5.5), and adds API retries for rate limits and dropped connections.

Merge method: fast-forward (dev pushed to main, all commits kept).

Changed

  • API requests rejected with HTTP 429 are retried up to 3 times. The wait
    comes from the Retry-After or ratelimit-reset header (capped at 60
    seconds), or is an exponential backoff of 2, 4 and 8 seconds plus jitter
    when the response has neither. In release plan, an asset whose lookup is
    still rate limited is reported missing with an APIRateLimitError
    warning, so it stays in the package.
  • Read-only API requests (GET, and the Lookup POST) are resent up to 2 times
    when the connection drops (EOF or connection reset). In long
    release plan runs these drops left assets with status unknown.
    Requests that change data are never resent.

Fixed

  • fix(release-plan): batch lookup error V3API_LookupError_012 no longer marks
    all assets missing. Since 0.5.5, release plan reported every
    non-Connection asset as missing in a target when any one asset was
    missing there, which also kept transitive dependencies that already exist
    in the target. The assets named in the error are now marked missing and
    the rest of the batch is looked up again (the batch is split in half when
    the error cannot be matched), with batches capped at 200 assets. A
    200-asset batch usually takes one or two Lookup calls.

🤖 Generated with Claude Code

jbrazda and others added 4 commits October 23, 2026 20:16
The main ruleset requires linear history and CI checks instead of pull
requests, so a fast-forward release needs no bypass unless dev contains
merge commits. Merging main back into dev after a squash added one
(1314e20) and made the v0.6.1 push need the admin bypass.
… marks all assets missing

The V3 Lookup API fails a whole batch with V3API_LookupError_012 when any
item is missing. Since 0.5.5 release plan sent all non-Connection assets in
one batch and treated that error as "everything missing", so only
Connections were reported found and the missing-transitive filter kept
transitive assets that already exist in the target.

A failed batch is now bisected until the missing assets are isolated,
lookups are chunked at 200 assets, other errors stay "unknown", and each
target logs found/missing/unknown counts and the Lookup call count. The
test fake now fails batches the way the real API does.
… connections

Bisecting a failed Lookup batch took more calls than one per asset when
many assets were missing (906 calls for 761 assets against tst). The
V3API_LookupError_012 message lists every missing object, so those are
marked missing and the rest is looked up again; bisection remains the
fallback. On ClaimCenter_Conversion (1311 assets) target checks now take
21 calls and 36 s, against about 17.5 min in v0.5.3, with the same plan.

HTTP 429 responses are retried up to 3 times, waiting as Retry-After or
ratelimit-reset says, or 2/4/8 s with jitter. An asset still rate limited
is reported missing with an APIRateLimitError warning so it stays in the
package.

Read-only requests (GET, Lookup) are resent up to 2 times on EOF or
connection reset, which left assets unknown in long runs. Requests that
change data are never resent.
@jbrazda
jbrazda merged commit 61e9101 into main Nov 2, 2026
16 checks passed
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.

1 participant