Conversation
There was a problem hiding this comment.
Pull request overview
Prepares the monorepo for the v0.2.0-beta.1 release by bumping package versions and adding a new release section to the changelog.
Changes:
- Bump
@microsoft/durabletask-jsto0.2.0-beta.1. - Bump
@microsoft/durabletask-js-azuremanagedto0.2.0-beta.1and update its peer dependency range for@microsoft/durabletask-js. - Add
v0.2.0-beta.1 (2026-02-10)entries toCHANGELOG.md.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| packages/durabletask-js/package.json | Version bump to 0.2.0-beta.1. |
| packages/durabletask-js-azuremanaged/package.json | Version bump and peer dependency range update for the core package. |
| CHANGELOG.md | Adds a new v0.2.0-beta.1 release section with listed PRs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## v0.2.0-beta.1 (2026-02-10) | ||
|
|
||
| ### Changes | ||
|
|
There was a problem hiding this comment.
The new v0.2.0-beta.1 section uses a "### Changes" heading, but the existing changelog format (and the documented release process) uses headings like "### New" and "### Fixes" per version. Consider splitting this section into the standard headings to keep changelog structure consistent and easier to scan.
| "name": "@microsoft/durabletask-js", | ||
| "version": "0.2.0-beta.1", | ||
| "description": "A Durable Task Javascript SDK compatible with Dapr Workflow and its underlying Durable Task engine", |
There was a problem hiding this comment.
package-lock.json still records the workspace package versions as 0.1.0-alpha.2/0.1.0-alpha.1 (and the azuremanaged peerDependency range), so the lockfile is now out of sync with this version bump. Please regenerate/update the lockfile (e.g., via npm install in the repo root) and include it in this release PR to keep installs reproducible.
Summary
What changed?
Why is this change needed?
Issues / work items
Project checklist
CHANGELOG.mdAI-assisted code disclosure (required)
Was an AI tool used? (select one)
If AI was used:
AI verification (required if AI was used):
Testing
Automated tests
Manual validation (only if runtime/behavior changed)
1.
2.
3.
Notes for reviewers