Release v1.0.52 (BulkUpdateBillingGroup from Blue API #892)

[quantdale]

Request

Publish v1.0.52 of @alphauspkgs/blue-sdk-ts so the Ripple Bulk Invoice Settings + Update consumer chain can proceed.

Why

• Blue API #892 merged: e7485b2985bce78fa959b012ff773db8d30184ff.
• The post-merge main-branch pipeline already pushed the generated contract to blue-sdk-ts main:
  • main = a5cd4d4ee16603f56ebc3e75eb70f0b146947151 (commit message references the Blue API merge)
  • billing/v1/billing_pb.ts contains bulkUpdateBillingGroup + BulkUpdate request/metadata/row types + all 22 normalized fields.
• Latest published npm version is 1.0.51; latest tag is v1.0.51.
• Consumers (alupi apps/ripple-billinggroups-ui via @alphauslabs/ripple-ui-globals) cannot type-check blueApi.newBillingClient.bulkUpdateBillingGroup until this is published.

Exact action required (needs repo write access)

git clone https://github.com/alphauslabs/blue-sdk-ts
cd blue-sdk-ts
git checkout main && git pull
# ensure HEAD == a5cd4d4ee16603f56ebc3e75eb70f0b146947151
git tag v1.0.52
git push origin v1.0.52

The tag push triggers .github/workflows/tag.yaml (pushes v*.*.* → npm publish --access public → commits the package.json version bump back to main).

Notes

• Local validation from main a5cd4d4: npm ci + npm run build pass; npm pack tarball contains bulkUpdateBillingGroup and all normalized fields.
• The agent identity available for this release session has read-only access to this repository (push=false), so the tag could not be pushed automatically.

Related: alphauslabs/blueapi#892 (merged), alphauslabs/ripple-openspec#82 (merged).