Repository navigation
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
bhabalan
marked this pull request as ready for review
November 19, 2026 04:48
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. |
akulakum
approved these changes
Nov 19, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
COMPLETES #CAI-8749
This pull request addresses
Deploy CDpublishes npm packages with a saved npm token. This change uses native Yarn trusted publishing through GitHub OIDC for all ten released workspaces. It is the Widgets repository change under CAI-8748.The npm owner can configure trusted publishers while this draft is reviewed. The first successful OIDC release is still required to complete CAI-8749.
by making the following changes
4.5.1to4.10.3, which includes the native OIDC fix for scoped packages. The lockfile changes only Yarn's built-in TypeScript patch hash and checksum; TypeScript remains5.7.2and dependency versions are unchanged.deploy:npm: yarn npm publishworkspace scripts and package selection. Grantid-token: writeonly topublish-npm, retaincontents: read, and remove the npm publish-token reference.--provenanceonly to the release command and repository metadata to the nine Contact Center manifests. Preserve version preparation, thenextdist-tag, public access, consumer build checks, workspace-content verification, and publication checks before release tags.ai-docs/RELEASING.md.Change Type
The following scenarios were tested
4.10.3install, production build, and development build passed.nexttag, public access, and no publication.next/public settings, and rejection before upload when exchange is denied. No real GitHub or npm authorization endpoint is used.actionlintand formatting checks passed.4.10.3. The suite retains seven existing skipped tests; styles reported six warnings in the unchanged Web Component sample.npm owner setup and merge gate
For each package listed in
ai-docs/RELEASING.md, add a GitHub Actions trusted publisher with organizationwebex, repositorywidgets, workflow filenamedeploy.yml, no environment, and Allow npm publish enabled.Keep this PR as a draft until these prerequisites are met. After the first successful token-free release, record the run and package results in CAI-8749 before removing obsolete Widgets secrets. Revoke a shared npm token only after all repositories and workflows that use it have migrated.
The GAI Coding Policy And Copyright Annotation Best Practices
OpenAI Codex prepared the configuration, tests, and documentation. The vendored Yarn CLI is the unmodified official distribution. Existing license declarations are retained. Maintainer review is required before merge.
Checklist before merging
Amplify validation does not apply to this release-tooling change.