Skip to content

fix(tooling): adding a new workflow to uprade the SDK version every W… - #754

Open
Kesari3008 wants to merge 1 commit into
webex:nextfrom
Kesari3008:automated-version-upgrade-flow
Open

Kesari3008 wants to merge 1 commit into
webex:nextfrom
Kesari3008:automated-version-upgrade-flow

Conversation

@Kesari3008

Copy link
Copy Markdown
Contributor

COMPLETES #AD-HOC

This pull request addresses

Update SDK version weekly

by making the following changes

Add a new yl worflow to run in github actions weekly to update SDK version

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • The testing is done with the amplify link
    < ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document
  • I have tested the functionality with amplify link

Make sure to have followed the contributing guidelines before submitting.

@Kesari3008
Kesari3008 requested a review from a team as a code owner October 20, 2026 11:17
@Kesari3008 Kesari3008 added the validated Indicates that the PR is ready for actions label Oct 20, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-20T11:25:19.968232Z 18409ec PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@aws-amplify-us-east-2

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-754.d1b38q61t1z947.amplifyapp.com

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 18409ec19f

ℹ️ 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".

Comment on lines +43 to +45
yarn workspace @webex/cc-store test:unit
yarn workspace @webex/cc-store build
yarn workspace samples-cc-react-app build

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Build workspace dependencies before validation

On every fresh scheduled runner, this block runs the store test before any topological workspace build. test:unit type-checks imports from @webex/test-fixtures, and both that package and the sample's @webex/cc-* imports point at untracked dist/type outputs, so yarn install alone leaves the first tsc with unresolved modules and the create-PR step is never reached. Run yarn build:dev (or equivalent topological builds) before these checks.

AGENTS.md reference: AGENTS.md:L84-L85

Useful? React with 👍 / 👎.

run: |
version="$(npm view @webex/contact-center@next version)"
echo "version=$version" >> "$GITHUB_OUTPUT"
yarn workspace @webex/cc-store add "@webex/contact-center@$version"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep generated SDK updates spec-current

Whenever the next tag advances, this command changes the store manifest and lockfile, but the generated branch never updates the exact SDK versions recorded in packages/contact-center/store/ai-docs/store-spec.md:51,97,473 or ai-docs/CONTRACTS.md:29. Every automated PR therefore immediately leaves the repository's contract/spec documentation claiming the old SDK; update those claims as part of the automation (or remove the version snapshots).

AGENTS.md reference: AGENTS.md:L68-L68

Useful? React with 👍 / 👎.

version="$(npm view @webex/contact-center@next version)"
echo "version=$version" >> "$GITHUB_OUTPUT"
yarn workspace @webex/cc-store add "@webex/contact-center@$version"
yarn workspace samples-cc-react-app add "@webex/contact-center@$version"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the umbrella Webex package aligned

Whenever the fetched version differs from 3.12.0-next.159, this advances the sample's direct dependency while leaving its exact webex@3.12.0-next.249 dependency unchanged; that umbrella package's lockfile manifest itself pins @webex/contact-center@3.12.0-next.159. The generated lockfile therefore installs two contact-center versions, contrary to the single-copy alignment documented in store-spec.md:473-476, so the corresponding umbrella release should be resolved and updated (or the update deferred until it embeds the selected contact-center build).

Useful? React with 👍 / 👎.

- name: Create pull request
uses: peter-evans/create-pull-request@v7
with:
token: ${{ secrets.GITHUB_TOKEN }}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a token that triggers pull-request CI

For a PR opened with the repository GITHUB_TOKEN, GitHub suppresses workflow events generated by that token. The full CI in .github/workflows/pull-request.yml:4-7 listens only for pull_request_target opened/labeled/reopened events, so neither this PR creation nor its labels starts the lint and full unit-test jobs, leaving the dependency PR with only this workflow's partial validation. Use a GitHub App or PAT token that is allowed to trigger the PR workflow.

Useful? React with 👍 / 👎.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

validated Indicates that the PR is ready for actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant