Repository navigation
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ff53563215
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| }, | ||
| "dependencies": { | ||
| "@webex/contact-center": "3.12.0-next.159", | ||
| "@webex/contact-center": "3.13.0-next.9", |
There was a problem hiding this comment.
Update the module spec with the new SDK pins
The dependency pins change here and in the React sample, but packages/contact-center/store/ai-docs/store-spec.md:539-544 still explicitly identifies @webex/contact-center 3.12.0-next.159 and webex 3.12.0-next.249 as the installed pair; its Stack and Requires sections also retain the old SDK pin. This violates the root AGENTS.md Spec-currency rule and leaves the documented SDK compatibility baseline inconsistent with the manifests. Update the module spec’s current-version declarations and any affected compatibility guidance in this same change.
AGENTS.md reference: AGENTS.md:L68-L68
Useful? React with 👍 / 👎.
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
COMPLETES https://jira-eng-sjc12.cisco.com/jira/browse/CAI-8643
SDK pull request: webex/webex-js-sdk#5275
Vidcast link: https://app.vidcast.io/share/4735574a-ba84-4213-9fd4-68f2a9ffe823
This pull request addresses
When an invalid access token is still in the session, the postauth service catalog returns HTTP 401 or 403. The SDK used to hide that status, so the widget saw
service-interceptor: 'wcc-api-gateway' is not a known service.The SDK fix is merged. This pull request picks up that SDK in the Contact Center widget.
by making the following changes
@webex/contact-centerin the Contact Center store moves from3.12.0-next.159to3.13.0-next.9.webexin the Contact Center React sample moves from3.12.0-next.249to3.13.0-next.14.yarn.lockis updated for those versions.Both packages are published from SDK commit
b124d984, the merge of the SDK pull request above. They depend on@webex/webex-core3.13.0-next.5.A catalog 401 is now
invalid_access_tokenwith statusCode 401. A catalog 403 isaccess_deniedwith statusCode 403. This SDK change does not clear the access token.Change Type
The following scenarios were tested
The SDK behavior was verified before the SDK pull request was merged. A catalog 401 shows
Error: invalid_access_tokenon Register. A catalog 403 showsError: access_denied. This widget change is the version bump that consumes that SDK.The GAI Coding Policy And Copyright Annotation Best Practices
Checklist before merging