Skip to content

chore(release): release 0.82.0 - #1006

Merged
dougborg merged 4 commits into
mainfrom
release-please--branches--main
Sep 20, 2026
Merged

chore(release): release 0.82.0#1006
dougborg merged 4 commits into
mainfrom
release-please--branches--main

Conversation

@dougborg-release-please

@dougborg-release-please dougborg-release-please Bot commented Jul 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

client: 0.82.0

0.82.0 (2026-09-20)

⚠ BREAKING CHANGES

  • client: the search request models change shape. SalesOrderSearchRequest / SalesOrderRowSearchRequest now take filter, order, limit and page at the top level; order/limit/ page are no longer nested inside filter, and the where level is gone. SalesOrderSearchWhere / SalesOrderRowSearchWhere are renamed to SalesOrderSearchFilter / SalesOrderRowSearchFilter, replacing the former envelope schemas of those names. No working call can break — the previous shape was rejected with 422 by the API.

Features

  • audit: compare inline request bodies and nested request sub-objects (#1049) (01d0f95)
  • client: add inventory-signals and MO production-ingredients list endpoints (#1039) (d915ae2), closes #1032
  • client: add manufacturing-order and sales-order rerank endpoints (#1037) (2b0e31c), closes #1032
  • client: fix broken search request shape and add 4 search endpoints (#1041) (8964472)
  • client: model traceability on manufacturing-order request DTOs (#1052) (8dd7a16)
  • client: sync spec with 2026-09-18 upstream refresh (#1034) (b810da4)
  • release: migrate to release-please manifest-mode release automation (#1005) (ec4a0d0)

Bug Fixes

  • ci: realign zizmor artipacked ignores after App-token migration (#1003) (ee97394)
  • client: use batch-id-only allocations for production requests (#1054) (153aa7f), closes #1042
  • deps: clear 23 transitive CVEs from uv.lock (#1036) (534ed4f)
  • tests: align MCP package asyncio_mode with the root (#1004) (27ee3a1)
mcp: 0.116.0

0.116.0 (2026-09-20)

Features

  • client: model traceability on manufacturing-order request DTOs (#1052) (8dd7a16)
  • release: migrate to release-please manifest-mode release automation (#1005) (ec4a0d0)

Bug Fixes

  • tests: align MCP package asyncio_mode with the root (#1004) (27ee3a1)

This PR was generated with Release Please. See documentation.

@dougborg-release-please
dougborg-release-please Bot force-pushed the release-please--branches--main branch 5 times, most recently from 832cb3b to 75d5aaf Compare September 18, 2026 19:14
@dougborg-release-please dougborg-release-please Bot changed the title chore(release): release 0.82.0 chore(release): release 1.0.0 Sep 18, 2026
@dougborg-release-please
dougborg-release-please Bot force-pushed the release-please--branches--main branch 2 times, most recently from aacb50a to ccef791 Compare September 18, 2026 22:25
@dougborg dougborg mentioned this pull request Sep 18, 2026
Merged
dougborg added a commit that referenced this pull request Sep 18, 2026
@dougborg @claude
chore(release): stay pre-1.0 on breaking changes (#1050)
be76e0f 
The breaking change in #1041 made release-please propose **1.0.0** in
#1006 — a narrow request-model fix (two search DTOs whose previous shape
the API rejected with 422) taking the client from 0.81.0 straight to a
major.

That is release-please's documented default: with no
`bump-minor-pre-major`, the first breaking change on a 0.x version goes to
1.0.0. Both packages here are pre-1.0 (client 0.81.0, MCP 0.115.0) and
breaking the API is still fine at this stage, so the default is wrong for
this repo.

Setting the flag at the top level (it applies to both packages) makes a
breaking change bump MINOR instead: 0.81.0 -> 0.82.0.

This deliberately does *not* change how commits are written. Breaking
changes still get `!` and a `BREAKING CHANGE:` footer — the changelog
needs them, and #1041's entry is accurate. The flag only decouples "this
commit is breaking" from "this project is now 1.0", which is a stability
statement that should be made on purpose rather than inherited from a
commit footer.

`docs/RELEASE.md` said breaking -> MAJOR, which is what produced the
surprise, so its bump table is corrected with a footnote explaining the
flag and how to undo it when 1.0 is actually wanted.

Merging this re-runs release-please, which will regenerate #1006 as
0.82.0.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@dougborg-release-please dougborg-release-please Bot changed the title chore(release): release 1.0.0 chore(release): release 0.82.0 Sep 18, 2026
@dougborg-release-please
dougborg-release-please Bot force-pushed the release-please--branches--main branch 2 times, most recently from 44c10c8 to b36c0dc Compare September 18, 2026 22:54
@dougborg-release-please
dougborg-release-please Bot force-pushed the release-please--branches--main branch from 92bf364 to b301922 Compare September 20, 2026 19:08
dougborg-release-please Bot and others added 3 commits September 20, 2026 19:08
@dougborg-release-please
chore(release): sync uv.lock and MCP client pin
96c30bc
@dougborg
fix(release): format generated changelog before CI
b9f6ee1 
Normalize the client changelog and include formatting in release PR
preparation so regenerated notes satisfy the existing mdformat gate.
@dougborg
fix(release): install formatter extras in preparation job
28c68c7
@dougborg
dougborg merged commit 4cd4bc7 into main Sep 20, 2026
22 checks passed
@dougborg
dougborg deleted the release-please--branches--main branch September 20, 2026 19:50
@dougborg-release-please

dougborg-release-please Bot commented Sep 20, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

1 participant

@dougborg