Conversation
There was a problem hiding this comment.
Pull request overview
Prepares the monorepo for the v0.1.0-beta.1 release by bumping package versions and adding a corresponding release section to the changelog.
Changes:
- Bump
@microsoft/durabletask-jsversion to0.1.0-beta.1. - Bump
@microsoft/durabletask-js-azuremanagedversion to0.1.0-beta.1and update its peer dependency minimum for@microsoft/durabletask-js. - Add
v0.1.0-beta.1entries toCHANGELOG.md.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| packages/durabletask-js/package.json | Version bumped to 0.1.0-beta.1. |
| packages/durabletask-js-azuremanaged/package.json | Version bumped to 0.1.0-beta.1; peer dependency minimum updated to >=0.1.0-beta.1. |
| CHANGELOG.md | Adds a new v0.1.0-beta.1 (2026-02-10) section with PR-linked entries. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| } No newline at end of file | ||
| { | ||
| "name": "@microsoft/durabletask-js", | ||
| "version": "0.1.0-beta.1", |
There was a problem hiding this comment.
The monorepo uses npm workspaces and tracks package versions in package-lock.json. After bumping this package version, package-lock.json still contains the previous workspace version (e.g., 0.1.0-alpha.2), which will cause npm ci/CI to fail with an out-of-date lockfile. Regenerate and commit an updated package-lock.json (typically by running npm install from the repo root) so the workspace package entry matches 0.1.0-beta.1.
| { | ||
| "name": "@microsoft/durabletask-js-azuremanaged", | ||
| "version": "0.1.0-alpha.1", | ||
| "version": "0.1.0-beta.1", |
There was a problem hiding this comment.
This version bump also requires updating the root package-lock.json workspace entry for @microsoft/durabletask-js-azuremanaged (it currently reflects the previous version). Please regenerate and commit package-lock.json so npm ci remains reproducible.
| ## v0.1.0-beta.1 (2026-02-10) | ||
|
|
||
| ### Changes | ||
|
|
There was a problem hiding this comment.
The release section uses a "### Changes" heading, but the repo's documented changelog format (doc/release_process.md) and prior entries in this file use "### New" / "### Fixes" (and optionally "### Breaking Changes"). To avoid inconsistency and potential confusion for release note consumers/tools, please either follow the existing section headings here (split items accordingly) or update the documented process in the same PR.
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