|
1 | 1 | # @scope3/agentic-client |
2 | 2 |
|
| 3 | +## 2.0.0 |
| 4 | + |
| 5 | +### Major Changes |
| 6 | + |
| 7 | +- [#27](https://github.com/scope3data/agentic-client/pull/27) [`3ccaa7d`](https://github.com/scope3data/agentic-client/commit/3ccaa7d6799ff84034188851adb357ad3bb022ca) Thanks [@nastassiafulconis](https://github.com/nastassiafulconis)! - Generate SDK from OpenAPI specifications |
| 8 | + |
| 9 | + Major refactor to automatically generate TypeScript SDK from OpenAPI specs: |
| 10 | + |
| 11 | + **New Features:** |
| 12 | + - Separate `PlatformClient` and `PartnerClient` for different user types |
| 13 | + - Full code generation from OpenAPI YAML files (platform-api, partner-api, outcome-agent) |
| 14 | + - Automated schema updates from agentic-api repository with GitHub Actions |
| 15 | + - Custom SDK generator script that creates MCP-compatible resource classes |
| 16 | + |
| 17 | + **Breaking Changes:** |
| 18 | + - Removed manual resource files (now auto-generated) |
| 19 | + - Removed SimpleMediaAgent (not in use) |
| 20 | + - `Scope3AgenticClient` now extends `PlatformClient` (backwards compatible) |
| 21 | + |
| 22 | + **Infrastructure:** |
| 23 | + - Added `scripts/generate-sdk.ts` for SDK generation |
| 24 | + - Added `scripts/update-schemas.sh` for automated OpenAPI spec updates |
| 25 | + - GitHub workflow for daily automated type updates and PR creation |
| 26 | + - Updated build process to use generated types |
| 27 | + |
| 28 | + **Testing:** |
| 29 | + - All 84 tests passing |
| 30 | + - Verified with real API calls to production environment |
| 31 | + - Both PlatformClient and PartnerClient confirmed working |
| 32 | + |
| 33 | +- [#27](https://github.com/scope3data/agentic-client/pull/27) [`3ccaa7d`](https://github.com/scope3data/agentic-client/commit/3ccaa7d6799ff84034188851adb357ad3bb022ca) Thanks [@nastassiafulconis](https://github.com/nastassiafulconis)! - BREAKING CHANGE: Remove legacy Scope3AgenticClient |
| 34 | + |
| 35 | + The legacy `Scope3AgenticClient` class has been completely removed. Users must now explicitly choose between: |
| 36 | + - `PlatformClient` - for brand advertisers/buyers managing campaigns and creatives |
| 37 | + - `PartnerClient` - for DSPs/publishers/partners managing media buys and products |
| 38 | + |
| 39 | + **Migration Guide:** |
| 40 | + |
| 41 | + ```typescript |
| 42 | + // Before: |
| 43 | + import { Scope3AgenticClient } from 'scope3'; |
| 44 | + const client = new Scope3AgenticClient({ apiKey: '...' }); |
| 45 | + |
| 46 | + // After (for brand advertisers): |
| 47 | + import { PlatformClient } from 'scope3'; |
| 48 | + const client = new PlatformClient({ apiKey: '...' }); |
| 49 | + |
| 50 | + // After (for media partners): |
| 51 | + import { PartnerClient } from 'scope3'; |
| 52 | + const client = new PartnerClient({ apiKey: '...' }); |
| 53 | + ``` |
| 54 | + |
| 55 | + Both clients have the same configuration options and provide access to the appropriate API resources for their use case. |
| 56 | + |
| 57 | +### Patch Changes |
| 58 | + |
| 59 | +- [#25](https://github.com/scope3data/agentic-client/pull/25) [`976ca4a`](https://github.com/scope3data/agentic-client/commit/976ca4a16161fd037aa6c547fd8d36cd065b7630) Thanks [@nastassiafulconis](https://github.com/nastassiafulconis)! - Fix npm Trusted Publisher authentication by removing conflicting NPM_TOKEN |
| 60 | + |
| 61 | + The release workflow was failing because it had both OIDC Trusted Publishing configured (id-token: write) and the legacy NPM_TOKEN environment variable. This caused npm authentication to fail. Removed NPM_TOKEN to use only Trusted Publishing for secure, token-free npm publishing. |
| 62 | + |
3 | 63 | ## 1.1.0 |
4 | 64 |
|
5 | 65 | ### Minor Changes |
|
0 commit comments