Azure / Azure/azure-functions-durable-js
Release v3.5.0
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 66
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 4
Description
**Prep Release**
- [ ] Create a post in the Durable Functions Release Teams channel to let the team know that we are starting a DF Node SDK release.
- [x] Check that [package.json](https://github.com/Azure/azure-functions-durable-js/blob/v3.x/package.json) has the correct package version.
- [x] The [official pipeline](https://dev.azure.com/azfunc/internal/_build?definitionId=546) should automatically run after a PR is merged to v3.x so you don't have to run it manually. Check that the pipeline ran with the expected latest PR. Download the .tgz package from the drop folder.
- [x] Draft the release notes.
**Testing**
- To test the package from the official pipeline, run the following commands from your test app
1. Uninstall the current durable-functions package: `npm uninstall durable-functions`
2. Clear all npm cache (optional): `npm cache clean --force`
3. Install your local .tgz file: `npm install `
4. Verify the installation: `npm list durable-functions`
- [x] Test that a JavaScript Durable Functions app works with the .tgz that we created above. Run `func host start` and trigger an orchestration.
- [x] Test that a TypeScript Durable Functions app works with the .tgz that we created above. Run `func host start` and trigger an orchestration. If you see the error `Error: Worker was unable to load entry point "dist/src/{index.js,functions/.js}": Found zero files matching the supplied pattern`, then run `npm run build` and then try running `func host start`.
**SDK Release**
- [ ] Dry run (optional): Run the [release pipeline](https://dev.azure.com/azfunc/internal/_build?definitionId=848) with the "Dry Run" box checked so you can simulate the npm publish step. It won't actually publish, but it will let you know what version would have been published and list other metadata. Check that there are no errors or warnings in the npm publish step.
- [ ] Run the [release pipeline](https://dev.azure.com/azfunc/internal/_build?definitionId=848) from the v3.x branch without the "Dry Run" box checked. This should publish the durable-functions package to npm. If there is an error, check that the npm token hasn't expired. Currently, it's set to expire on 8/6/2026.
**Release Completion**
- [ ] Uninstall the existing durable-functions package from your test apps using `npm uninstall durable-functions`. Check that the package was uninstalled by running `npm list durable-functions`. Download the .tgz from the [durable-functions npm page](https://www.npmjs.com/package/durable-functions) by running `npm i durable-functions` from your test app. It should install the latest package with the new version. Test it in JS and TS apps and check that `func host start` and triggering an orchestration work.
- [ ] Publish the release notes.
Contributor guide
Research direction
Start with package.json on the v3.x branch, then check the official pipeline for the expected package artifact and review the release pipeline settings. Test the downloaded .tgz in JavaScript and TypeScript apps with npm and func host start; done means the package is published to npm, both apps work, and the release notes are published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, typescript
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100