httpware 0.12 + opt-in patch bump for non-merge commits (branch-prefix)#24
Merged
Merged
Conversation
Raise the dependency floor from >=0.8.2 to >=0.12.0 and collapse the two Link-header pagination call sites from send_with_response(build_request(...)) to the 0.12.0 get_with_response shortcut. No behavior change; picks up 0.11.0 security/correctness hardening via the version move. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Spec (design.md) and implementation plan (plan.md) for an opt-in branch-prefix flag that patch-bumps plain (non-merge) commits. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Drop the nonexistent test-branch / test-branch-strategies / test-cc-strategies recipes; document that just test already runs --cov-branch with a project-wide fail_under=100 gate, and reference just docs-build for the strict docs gate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Mark both bundles shipped (status: shipped, pr: 24, outcome filled), move them from changes/active/ to changes/archive/, and move their Index lines from Active to Archived. architecture/ conclusions were already promoted in their respective commits. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Open the deferred register with two real-but-unscheduled items surfaced in the PR #24 review, each with a revisit trigger: conventional-commits parity for the non-merge/non-conforming fallback flag, and httpware max_error_body_bytes adoption. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lesnik512
added a commit
that referenced
this pull request
Jun 16, 2026
…26) * docs(planning): add httpware max-error-body-bytes change bundle Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * providers: cap provider error-body reads at 1 MiB Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * providers: translate ResponseTooLargeError to ProviderAPIError Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: note the 1 MiB provider error-body cap Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: correct stale send_with_response reference in providers.md Pagination moved to get_with_response in the httpware 0.12 bump (#24); the HTTP-client section still named the old helper. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(planning): archive httpware max-error-body-bytes bundle (#26) Mark the bundle shipped (status: shipped, pr: 26, outcome filled), move it to changes/archive/, move its Index line to Archived, and clear the now-resolved httpware item from deferred.md. architecture/providers.md was promoted in this PR's earlier commits. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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
Two independent changes bundled on one branch:
get_with_response, collapsing the two Link-header pagination call sites fromsend_with_response(build_request("GET", ...))to a single call. No behavior change; also picks up 0.11.0's security/correctness hardening (URL secret redaction, RetryBudget fix) via the version move.patch_on_non_merge_commitflag (branch-prefix). NewBranchPrefixConfigfield (defaultFalse). When enabled, a plain (non-merge) HEAD commit on the default branch bumps patch instead of producing no bump — so teams that allow direct pushes can auto-tag a patch release. Settable viaSEMVERTAG_BRANCH_PREFIX__PATCH_ON_NON_MERGE_COMMIT=true. Affects only the non-merge exit; a merge commit with an unrecognized prefix still produces no bump. Default-off preserves existing behavior exactly.Planning bundles:
planning/changes/active/2026-06-16.01-httpware-0.12-get-with-response/(lightweight) andplanning/changes/active/2026-06-16.02-branch-prefix-patch-on-non-merge/(full: design.md + plan.md).Test Plan
just test— 438 passed, 100% branch coveragejust lint-ci— eof-fixer, ruff format, ruff check, ty all cleanmkdocs build --strict— clean🤖 Generated with Claude Code