Skip to content

merge queue: checking main (f5a4795), #3441 and #3430 together#3474

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/396c897525
Closed

merge queue: checking main (f5a4795), #3441 and #3430 together#3474
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/396c897525

Conversation

@mergify

@mergify mergify Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (f5a4795), #3441 and #3430 are queued together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #3430.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: c11078800deb5a056c3543b32ec38cc73daf169c
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 3430
    scopes: []
scopes: []
...

SyntaxSawdust and others added 4 commits July 2, 2026 12:57
The sync profiler defaulted page size to 100 and only read a pagination
limit param's default, never its maximum. APIs that cap page_size below 100
(e.g. Granola public API: maximum 30 on /v1/notes and /v1/folders) then get
every sync page rejected with HTTP 400. Capture the maximum on spec.Param and
clamp the resolved page size down to it.

- Normalize both OpenAPI encodings of an upper bound at parse time: inclusive
  maximum -> Param.Maximum; exclusive (3.1 numeric exclusiveMaximum, or 3.0
  maximum + exclusiveMaximum: true) -> Param.ExclusiveMaximum. In 3.1 both are
  independent assertions and may co-exist; the profiler takes the most
  restrictive, yielding floor(inclusive) or ceil(exclusive)-1.
- Apply the clamp on both sync paths: the cursor/page path
  (syncPaginationDefaultsFromEndpoint) and the ID-walk path
  (detectIDWalkParams), which resolves its page size independently.

Fixes #3440
@mergify mergify Bot closed this Jul 6, 2026
@mergify mergify Bot deleted the mergify/merge-queue/396c897525 branch July 6, 2026 18:04
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