feat: SDK update for version 16.0.0 - #111
Conversation
main received 15.7.0 as a squash merge (#108), so the same change exists under a different commit on each branch. main's tree is identical to dev's 15.7.0 commit, so dev's generated 15.8.0 tree is kept as-is.
Greptile SummaryThe PR updates the Console SDK to version 16.0.0 and introduces new services, models, enums, and organization-scoped client configuration.
Confidence Score: 4/5The dependency override must be fixed before merging because clean installs can fail on the package's advertised Node 18 runtime. The SDK additions are internally consistent, but brace-expansion 5.0.9 requires Node 20 or newer while the package promises Node 18 compatibility, causing engine-strict installations to fail. Files Needing Attention: package.json and package-lock.json Important Files Changed
Prompt To Fix All With AI### Issue 1
package.json:49
**Override excludes supported Node 18**
When dependencies are installed on the advertised Node 18 runtime with engine checks enabled, the override selects `brace-expansion@5.0.9`, which requires Node 20 or later, causing `npm install` to fail with an engine error.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "chore: merge main into dev for the 16.0...." | Re-trigger Greptile |
| }, | ||
| "overrides": { | ||
| "brace-expansion": "5.0.8" | ||
| "brace-expansion": "5.0.9" |
There was a problem hiding this comment.
Override excludes supported Node 18
When dependencies are installed on the advertised Node 18 runtime with engine checks enabled, the override selects brace-expansion@5.0.9, which requires Node 20 or later, causing npm install to fail with an engine error.
Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 49
Comment:
**Override excludes supported Node 18**
When dependencies are installed on the advertised Node 18 runtime with engine checks enabled, the override selects `brace-expansion@5.0.9`, which requires Node 20 or later, causing `npm install` to fail with an engine error.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
This PR contains updates to the SDK for version 16.0.0.
What's Changed
vectorsDB.createTextEmbeddings()to the newEmbeddingsserviceusage.listEvents()interval,dimensions,orderBy, andorderDirnow take enumsusage.listGauges()interval,dimensions,orderBy, andorderDirnow take enumsAffiliatesservice for referral links, referrals, and rewardsEmbeddingsservice withcreateTextEmbeddings()proxy.createInvalidation()with theProxyInvalidationmodel andInvalidationTypeenumClient.setOrganization()for organization-scoped requestsUsageInterval,UsageEventDimension,UsageGaugeDimension,UsageOrderBy,UsageOrderDirectionenumsQuerySuggestionResourceenumproxy.invalidations.writeto theProjectKeyScopesenumaffiliates.clicksas ausage.listEvents()metric