Skip to content

v0.6.1 - Fix org slug resolution

Choose a tag to compare

View all tags
@emaxe emaxe released this 13 Sep 10:54
· 23 commits to main since this release
v0.6.1
70fcd87

Fixed

  • --org <team> (CLI) and orgId (REST/MCP) accept either a team's real id or its slug, per their own documentation — but passing the slug on an explicit request (anyone in more than one team, using --org/orgId to pick a non-default one) crashed with a 500: resolveOrgScope forwarded it straight into a UUID-typed database column instead of resolving it first. Affected POST/GET /artifacts and the org-scoped MCP tools; the single-team auto-selected case was never affected.

Found via an end-to-end check of the published npm package against a live server with more than one team.

Assets 2
Loading