chore: bump Workforce packages to 4.1.56 - #143
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
Upgrade the pinned Workforce packages, CLI, and overrides from 4.1.43 to 4.1.56 and regenerate the lockfile. This adopts the shared runtime provider-failure reporting from AgentWorkforce/workforce#336, including actionable quota errors and reported reset times.
Validation under Node 22: 372 tests passed, 2 skipped; full typecheck passed. An offline check using the installed npm artifact verifies that the runtime rejects a quota failure before a generic caller error, preserves the reset hint, makes only one harness call, and leaves successful/OS-killed results unchanged. The Workforce release and registry-install smoke workflow both passed.
Only package.json and package-lock.json change. The lockfile also includes transitive dependency changes introduced by the intervening Workforce releases. No agent-specific error parser or live customer review execution is added.