ci(release): per-package prepare-release workflow + changelog script

[YunchuWang]

Splits the substantive release-tooling change out of #335 so it can be reviewed and merged on its own.

What

• Reworks .github/workflows/prepare-release.yaml into the per-package release model: a required package choice input (durabletask-js, durabletask-js-azuremanaged, azure-functions-durable), per-package tag prefixes (v, azuremanaged-v, durable-functions-v), and per-package changelog paths.
• Updates scripts/update-changelog.js to accept the per-package changelog path as a 4th argument.

Why these two files ship together

The workflow invokes node scripts/update-changelog.js "$NEW_VERSION" "$RELEASE_DATE" "$CHANGELOG_FILE" "$CHANGELOG_PATH"; that 4th argument only exists in the updated script, which has no other caller. Splitting them apart would break the release workflow.

Provenance

Content is byte-identical to the CI-green #335 branch at 8501bc0 — a pure re-partition, no behavior change. npm run lint exits 0.

---

Part of the #335 split

#335 is being decomposed into four mutually independent PRs that can merge in any order:

• ci(release): per-package prepare-release workflow + changelog script #337 — per-package prepare-release workflow + changelog script
• build(release): npm publishConfig for all three packages #338 — npm publishConfig (smallest; most urgent for publishing)
• docs(release): changelog, README, and copilot-instructions updates #339 — changelog / README / copilot-instructions docs
• docs(release): rewrite release_process.md for the per-package model #340 — release_process.md runbook rewrite

Together these carry every one of #335's 10 files with no overlap. #335 stays open until the file→PR mapping posted there is confirmed; these PRs neither merge nor close it.

[Copilot]

Pull request overview

This PR updates the repo’s release tooling to support per-package release preparation (rather than bumping/tagging multiple packages together), while extending the changelog update script to target a package-specific changelog file.

Changes:

• Updates prepare-release GitHub Actions workflow to require a package input and thread per-package metadata (dir, npm name, tag prefix, changelog path) through versioning/tagging/changelog steps.
• Scopes changelog generation to commits affecting the selected package directory and uses per-package tag namespaces.
• Extends scripts/update-changelog.js to accept an optional 4th argument to update a specified changelog file in place.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/prepare-release.yaml	Converts release preparation to a per-package model with package-scoped tags, changelog paths, and publish guidance.
scripts/update-changelog.js	Adds support for updating a caller-specified changelog file (instead of always CHANGELOG.md).

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

.github/workflows/prepare-release.yaml:269

• The run summary’s publish command omits --access public for the two scoped packages (@microsoft/durabletask-js*). In this repo state there’s no publishConfig.access in those package.json files, so npm publish will default to restricted access (or fail), which is easy to miss when following the workflow summary. Since this PR is intended to be independently mergeable, it’d be safer for the workflow to add --access public when npm_name is scoped.

          # Derive the npm dist-tag from the version string. A prerelease (contains "-") must
          # publish under a non-default tag so it does NOT move the "latest" dist-tag.
          if [[ "$NEW_VERSION" == *-* ]]; then
            PUBLISH_CMD="npm publish --registry https://registry.npmjs.org/ --tag preview"
          else
            PUBLISH_CMD="npm publish --registry https://registry.npmjs.org/"
          fi