Repository navigation
chore(release): version 3.6.0 — consolidate changelog and migration - #80
Conversation
|
Droid finished @tyler5673's task —— View job Review summary (approved): Release plumbing looks correct overall. The only actionable issue I see is a changelog typo that documents a non-existent deprecated async shim name. |
![factory-droid[bot]](https://avatars.githubusercontent.com/in/358017?s=60&v=4){kind=small}
c488b67 to
df51a43
Compare
|
Droid finished @tyler5673's task —— View job Droid finished Review summary (approved): Release plumbing looks consistent overall. The only actionable fix is to tighten MIGRATION.md wording so it does not imply no types changed when |
df51a43 to
9498625
Compare
|
Droid encountered an error —— View job |
9498625 to
a64146e
Compare
tyler5673
changed the title
|
Droid encountered an error —— View job |
Bumps pyproject.toml and src/youdotcom/_version.py to 3.6.0 (uv.lock via uv lock). Consolidates the three unreleased CHANGELOG sections ([3.6.0] finance, [3.7.0] highlights cap, [3.8.0] the default flip) into one [3.6.0] - 2026-10-14 entry, and the two MIGRATION sections (3.5.0 -> 3.6.0 finance widening, 3.7.0 -> 3.8.0 flip) into one 3.5.0 -> 3.6.0 section covering both. All in-repo version references renumbered to match (pre-3.8.0 -> pre-3.6.0, 3.7.0+ -> 3.6.0+). Note: check_drift now reports a NEW unrelated gap — the live spec recently gained a strict_operators request param on POST /v1/search that the SDK does not model. It predates this branch (server-side change), needs its own feature PR.
a64146e to
d02145c
Compare
|
Droid finished @tyler5673's task —— View job Review summary (approved): LGTM. The 3.6.0 version bumps and the changelog/migration consolidation look internally consistent, and no new correctness or security issues stand out in this diff. |
What
The 3.6.0 release version commit, plus the changelog/migration consolidation that comes with shipping #75, #76, and #78 together.
pyproject.toml+src/youdotcom/_version.py→ 3.6.0 (uv.lockviauv lock, never hand-edited)output_schema+warnings), thetotal_max_tokenscap, and the default flip — consolidated into one[3.6.0] - 2026-10-14entry (Added × finance params/fields + cap; Changed × the flip + finance widenings + container history)3.5.0 → 3.6.0section: combined callout, one action-required table (5 rows incl. billing), both before/after examples, combined no-break notespre-3.8.0→pre-3.6.0,3.7.0+→3.6.0+in sdk.py docstrings, tests, examples); CHANGELOG↔MIGRATION anchors re-linkedVersioning call
Minor, not major: default responses change shape (snippets→highlights, knowledge cards appear) but every affected field was already
Optional— no model/signature break; the observable change + billing exposure are what the MIGRATION action table covers. Repo precedent: 2.4.0 shipped the same change class (researchcontentstr→Union) as a minor.Verification
pytest tests/ --ignore=test_live --ignore=test_performance— 476 passedmypy src/youdotcom/— clean;pylint --enable=E --disable=all— 10.00/10TestLiveSearch+TestLiveSearchDefaults— 5 passeduv run python -c "import youdotcom; print(youdotcom.__version__)"→3.6.0scripts/check_drift.py— reports one NEW, unrelated gap (see below), otherwise cleancheck_driftnow reportsPOST /v1/search: spec has params {'strict_operators'}. The live spec recently gained astrict_operatorsrequest param (bool, defaultfalse); it appeared server-side after #78's final green checks, so it exists on main today with or without this PR. It's a new feature (param + tests + docs), not release plumbing — should ship as its own PR once ticketed. This PR intentionally does not absorb it.After merge (the release ritual)
tag
v3.6.0on the merge commit → TestPyPI → clean-room verify → prod PyPI → GitHub Release (--latest, CHANGELOG notes) → docs parity.