Repository navigation
chore: release packages (beta) - #472
Conversation
Codex Review SummaryThis 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. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 29 minutes. View limit details
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 |
There was a problem hiding this comment.
🔵 Needs a closer look
Merging triggers a public npm beta publish, which is a release-timing decision the maintainer explicitly reserves ("merge this... when you're ready to do a release") and warrants final human sign-off despite the diff being mechanically correct.
0 open findings
What changed in this PR
This is an automated release PR opened by the Changesets GitHub action while main is in beta pre-release mode. It promotes the four published @temporal-contract/* packages from 8.0.0-beta.13 to 8.0.0-beta.14, folding in two already-merged changesets (the client/contract standalone-activity feature and the worker context.executeActivity feature, both tied to issue #452). No source code changes are involved — only version numbers, CHANGELOG entries, internal peer-dependency ranges, and the archival of the consumed changesets under .changeset/pre/.
Changes:
- Bump all four packages (
contract,client,worker,testing) to8.0.0-beta.14and update their internal peer-dependency ranges to^8.0.0-beta.14. - Append
8.0.0-beta.14sections to each package's CHANGELOG, matching the consumed changesets' bump types (client/workerMinor, contractPatch, testing dependency-only). - Archive the two released changesets (
client-standalone-activities.md,worker-execute-activity.md) under.changeset/pre/.
| File | Description |
|---|---|
| packages/contract/package.json | Version bump to beta.14 |
| packages/contract/CHANGELOG.md | Patch Changes entry for the standalone-activity changeset |
| packages/client/package.json | Version bump + contract peer dep → ^8.0.0-beta.14 |
| packages/client/CHANGELOG.md | Minor Changes entry + dependency update |
| packages/worker/package.json | Version bump + contract peer dep → ^8.0.0-beta.14 |
| packages/worker/CHANGELOG.md | Minor Changes entry for executeActivity + dependency update |
| packages/testing/package.json | Version bump + client/contract/worker peer deps → ^8.0.0-beta.14 |
| packages/testing/CHANGELOG.md | Dependency-update-only Patch Changes entry |
| .changeset/pre/client-standalone-activities.md | Archived released changeset (client minor, contract patch) |
| .changeset/pre/worker-execute-activity.md | Archived released changeset (worker minor) |
I verified that all four packages are in a Changesets fixed group (explaining the lockstep testing bump), that no unconsumed changesets remain in the .changeset/ root, that every internal peer-dependency range was bumped consistently, and that each CHANGELOG section's bump type and text exactly matches the source changeset front matter. No objective issues were found.
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@temporal-contract/client@8.0.0-beta.14
Minor Changes
29c8bc3: Run a contract's global activity as a standalone activity, with no workflow around it (Temporal Server ≥ 1.32):
ContractClientgainsstartActivity,executeActivityandgetActivityHandle. The task queue comes from the contract,argsis validated before the start, and the result is parsed against the output schema. The handle'sresult()decodes the activity's declared errors into typedContractErrors and reports the outcomes as first-class errors:ActivityCancelledError,ActivityTerminatedError,ActivityTimeoutError, otherwiseActivityFailedError.describe,cancelandterminateerr withActivityExecutionNotFoundError, and a duplicate start withActivityAlreadyStartedError. The activity's contract-levelactivityOptionsare the call's defaults, and the merged options need a per-attempt and a total bound. New pattern groups:ACTIVITY_START_PATTERNS,ACTIVITY_RESULT_PATTERNS,ACTIVITY_EXECUTE_PATTERNS.The worker side needs nothing new:
declareActivitiesHandleralready registers each activity under its name on the contract's queue.Patch Changes
@temporal-contract/worker@8.0.0-beta.14
Minor Changes
29c8bc3:
context.executeActivity(contract, activityName, { args, ...options })calls a global activity of any contract on that contract's task queue, typically an activity-only contract served by a dedicated worker pool:The queue name is written once, on the contract whose worker polls it, instead of in an
activityOptionsByNameentry per calling workflow (AllowtaskQueuein contract-levelactivityOptions#452). The call validates and classifies likecontext.activities.X. Options mergedeclareWorkflow'sactivityOptions→ the activity's contract-levelactivityOptions→ the per-call options, and must carry a per-attempt and a total bound.Patch Changes
@temporal-contract/contract@8.0.0-beta.14
Patch Changes
29c8bc3: Run a contract's global activity as a standalone activity, with no workflow around it (Temporal Server ≥ 1.32):
ContractClientgainsstartActivity,executeActivityandgetActivityHandle. The task queue comes from the contract,argsis validated before the start, and the result is parsed against the output schema. The handle'sresult()decodes the activity's declared errors into typedContractErrors and reports the outcomes as first-class errors:ActivityCancelledError,ActivityTerminatedError,ActivityTimeoutError, otherwiseActivityFailedError.describe,cancelandterminateerr withActivityExecutionNotFoundError, and a duplicate start withActivityAlreadyStartedError. The activity's contract-levelactivityOptionsare the call's defaults, and the merged options need a per-attempt and a total bound. New pattern groups:ACTIVITY_START_PATTERNS,ACTIVITY_RESULT_PATTERNS,ACTIVITY_EXECUTE_PATTERNS.The worker side needs nothing new:
declareActivitiesHandleralready registers each activity under its name on the contract's queue.@temporal-contract/testing@8.0.0-beta.14
Patch Changes