Skip to content

chore(contact-center): trigger next npm publish - #5183

Merged
mkesavan13 merged 1 commit into
webex:nextfrom
akulakum:chore/WXCC-6026-trigger-next-publish
Aug 21, 2026
Merged

chore(contact-center): trigger next npm publish#5183
mkesavan13 merged 1 commit into
webex:nextfrom
akulakum:chore/WXCC-6026-trigger-next-publish

Conversation

@akulakum

@akulakum akulakum commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

COMPLETES WXCC-6026

This pull request addresses

Deploy CD on next previously published npm packages successfully, but Publish - Tags failed because git tag v3.12.0-next.179 already existed on the remote (re-run collision). Answer on Webex SDK work is already on next; consumers need a fresh next publish and tag without re-running a failed pipeline.

Merging a minimal change under @webex/contact-center re-triggers Deploy CD: changed-package detection → version increment on the next dist-tag (e.g. 3.12.0-next.180) → npm publish for @webex/contact-center and the webex meta-package → new git tag.

by making the following changes

  • Update packages/@webex/contact-center/ai-docs/contact-center-spec.md
    • Bump spec updated_at metadata to 2026-08-21
    • Add Answer on Webex to the Overview feature list (Accept, Decline, Mute, DTMF via enableWxBetterTogether)

No runtime or API changes. Documentation-only touch to satisfy changed-package detection for the CC workspace.

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

  • Documentation-only change; no unit or integration test updates required.
  • Verified locally that only contact-center-spec.md is modified.
  • Post-merge verification (owner): confirm Deploy CD Publish - NPM and Publish - Tags succeed, then check:
    • npm view webex dist-tags.next
    • npm view @webex/contact-center dist-tags.next

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

I certified that

  • I have read and followed contributing guidelines
  • I discussed changes with code owners prior to submitting this pull request
  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the documentation accordingly

@akulakum
akulakum requested a review from a team as a code owner August 21, 2026 15:07
@akulakum akulakum added the validated If the pull request is validated for automation. label Aug 21, 2026
@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-5183.d3m3l2kee0btzx.amplifyapp.com

@mkesavan13
mkesavan13 merged commit 637d765 into webex:next Aug 21, 2026
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

validated If the pull request is validated for automation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants