v0.3.12

Patch Changes

• Updated dependencies [16ed7f3]
  • pgbeam@0.4.18

v0.3.11

Patch Changes

• a9c235e: feat(api): anomaly rules, the authoring surface (roadmap item 4, slice 3)
• Updated dependencies [a9c235e]
  • pgbeam@0.4.17

v0.3.10

Patch Changes

• Updated dependencies [40af2fb]
  • pgbeam@0.4.16

v0.3.9

Patch Changes

• Updated dependencies [631f106]
  • pgbeam@0.4.15

v0.3.8

Patch Changes

• Updated dependencies [a5fbfca]
  • pgbeam@0.4.14

v0.3.7

Patch Changes

• 3342c65: feat(policy): content_scan_mode and content_scan_max_bytes on the policy profile
• Updated dependencies [3342c65]
  • pgbeam@0.4.13

v0.3.6

Patch Changes

• 3f33063: fix(sdk,cli): read the API's RFC 9457 problem documents

  ApiError now exposes code, type, title, detail, instance, requestId and errors, and its message comes from the document's detail rather than falling through to the status text. Branch on code: two conditions can share a status, and a 403 is either a permissions problem or a billing one. The CLI puts the code on the error line, lists field errors under it, and carries both in --json output.

• Updated dependencies [3f33063]

• Updated dependencies [022577d]

• Updated dependencies [eca3f27]

• Updated dependencies [c1fa878]

• Updated dependencies [9818ecf]

• Updated dependencies [3f33063]

  • pgbeam@0.4.12

v0.3.5

Patch Changes

• 43acb8e: feat(api): publish organization membership endpoints, split out of #2079

• 379b817: feat(webhooks): publish delivery contract and validate event types

• 43acb8e: fix(api): the member API contract claimed two things the server refuses

  UpdateOrgMemberRoleRequest.role and CreateOrgInvitationRequest.role now use a new AssignableOrgRole enum, which is OrgRole without owner. The server has always rejected owner on both paths with a 400, so every generated client, the CLI help and the reference pages were advertising a call that never works. Responses keep the full OrgRole, because a member really can be an owner. role is also no longer required on an invitation, matching the server, which defaults an absent role to member.

  listOrgMembers and listOrgInvitations now enforce the page_size range they declare. They read the query string directly and clamped anything outside 1 to 100 back to the default of 20, so ?page_size=500 was a documented 400 everywhere else in the API and a silent 20 here.

  listOrgInvitations now enforces the status enum it declares. Anything outside pending, accepted, rejected and canceled went to the database as a literal filter and came back as an empty page with a 200, so a caller who mistyped the status was told the organization has no invitations. It is a 400 now, as the contract has always said. ?status= with no value is also a 400 rather than the unfiltered list; omit the parameter to list everything.

  removeOrgMember's published description said "An owner cannot be removed; demote them first", and the server does neither half of that. It refuses only when the organization is down to its last owner, so removing any other owner returns 204, and demoting the last owner hits the same guard and returns the same 409. The description now says what the guard does: the last remaining owner cannot be removed or demoted, so transfer ownership first, which is the advice the 409 itself gives.

  Go SDK callers: nothing to migrate. OrgRole and AssignableOrgRole are both new types in go.pgbeam.com/sdk as of this release, which is what the minor bump is for.

• 43acb8e: fix(cli): the new organization member commands could not show a role

  pgbeam orgs members list, orgs members set-role, orgs invitations list and orgs invitations create rendered a table with no role column, so the command that changes a member's role could not show the role it had just set. role points at the OrgRole enum, and until #2122 the manifest generator dropped every column whose schema is a named type. This branch now builds on that fix, and the column appears in all four. On the member list it takes the slot image had, which was an avatar URL.

• Updated dependencies [bd2d132]

• Updated dependencies [58d0ed0]

• Updated dependencies [43acb8e]

• Updated dependencies [379b817]

• Updated dependencies [7a26954]

• Updated dependencies [8deebf2]

• Updated dependencies [43acb8e]

  • pgbeam@0.4.11

v0.3.4

Patch Changes

• e1229b0: fix(cli): tables dropped every field whose schema is a named type

  pgbeam db list did not show which databases are replicas, pgbeam db inspect did not show ssl_mode, and pgbeam projects list did not show whether a project is running. All three are fields the contract declares and the API returns.

  The manifest generator keeps a column only when it can read a scalar type off the response property, and a property that points at a named schema is a $ref carrying no type. Nothing failed: the manifest is generated and checked in, so a column that never appeared looked like a column nobody wanted. Both the parameter and the response paths now resolve one level of $ref before deciding.

  db list and projects list are at the eight-column limit, so each drops its lowest-priority column to make room: project_id on a project-scoped database list, and cloud on the project list.

v0.3.3

Patch Changes

• Updated dependencies [8b04b38]
  • pgbeam@0.4.10