angular/devtools/docs/release.md

# Publish Angular DevTools

To publish Angular DevTools, run the following command and follow the prompts:

```shell
pnpm run devtools:release
```
docs(devtools): update README to be more clear for extension reviewers (#55406) Mozilla requires add-ons to have reproducible builds and this is managed directly by human reviewers and need to understand how to build Angular DevTools correctly. This commit defines a reproducible way of building Angular DevTools which is useful for reviewers and contributers. The actual changes I made include: 1. Moving local development content into `devtools/README` (deleting `devtools/DEVELOPING.md`) and explicitly stating the Node version as well as global Yarn install to be clear about the correct way to build the extension. This should make it easier for reviewers to understand and reproduce builds. 2. Moving release instructions to a separate doc to reduce noise as well as making some minor clean ups there. I briefly considered pointing reviewers at a new `devtools/docs/reviewers.md` doc, but decided against it because I want these instructions to be maintained in a single location where contributors and reviewers use the same content. This way any changes don't miss one of these sets of users. If reviewers have trouble with this format (dev builds isn't useful to reviewers and some content is repeated from other docs for contributors) then we can consider splitting out to a separate `reviewers.md` file. But until then, I'd like to try sharing this content and see how it works out in practice. PR Close #55406 2024-04-18 19:29:11 +00:00			`# Publish Angular DevTools`

build: introduce and document `pnpm run devtools:release` command (#63599) This commit introduces a new `pnpm run devtools:release` command to streamline the Angular DevTools release process. The command automates the entire release workflow, including checking for new commits, updating version numbers, creating a release commit, and guiding the user through the publishing steps for both Chrome and Firefox extensions. The `devtools/docs/release.md` documentation has been updated to reflect the use of this new command, providing a single entry point for the release process. A new script `devtools/tools/release.mts` has been added to implement the release logic, and `package.json` has been updated to include the new script. PR Close #63599 2025-09-04 14:32:44 +00:00			`To publish Angular DevTools, run the following command and follow the prompts:`
docs(devtools): update README to be more clear for extension reviewers (#55406) Mozilla requires add-ons to have reproducible builds and this is managed directly by human reviewers and need to understand how to build Angular DevTools correctly. This commit defines a reproducible way of building Angular DevTools which is useful for reviewers and contributers. The actual changes I made include: 1. Moving local development content into `devtools/README` (deleting `devtools/DEVELOPING.md`) and explicitly stating the Node version as well as global Yarn install to be clear about the correct way to build the extension. This should make it easier for reviewers to understand and reproduce builds. 2. Moving release instructions to a separate doc to reduce noise as well as making some minor clean ups there. I briefly considered pointing reviewers at a new `devtools/docs/reviewers.md` doc, but decided against it because I want these instructions to be maintained in a single location where contributors and reviewers use the same content. This way any changes don't miss one of these sets of users. If reviewers have trouble with this format (dev builds isn't useful to reviewers and some content is repeated from other docs for contributors) then we can consider splitting out to a separate `reviewers.md` file. But until then, I'd like to try sharing this content and see how it works out in practice. PR Close #55406 2024-04-18 19:29:11 +00:00
			```shell
build: introduce and document `pnpm run devtools:release` command (#63599) This commit introduces a new `pnpm run devtools:release` command to streamline the Angular DevTools release process. The command automates the entire release workflow, including checking for new commits, updating version numbers, creating a release commit, and guiding the user through the publishing steps for both Chrome and Firefox extensions. The `devtools/docs/release.md` documentation has been updated to reflect the use of this new command, providing a single entry point for the release process. A new script `devtools/tools/release.mts` has been added to implement the release logic, and `package.json` has been updated to include the new script. PR Close #63599 2025-09-04 14:32:44 +00:00			`pnpm run devtools:release`
docs(devtools): update README to be more clear for extension reviewers (#55406) Mozilla requires add-ons to have reproducible builds and this is managed directly by human reviewers and need to understand how to build Angular DevTools correctly. This commit defines a reproducible way of building Angular DevTools which is useful for reviewers and contributers. The actual changes I made include: 1. Moving local development content into `devtools/README` (deleting `devtools/DEVELOPING.md`) and explicitly stating the Node version as well as global Yarn install to be clear about the correct way to build the extension. This should make it easier for reviewers to understand and reproduce builds. 2. Moving release instructions to a separate doc to reduce noise as well as making some minor clean ups there. I briefly considered pointing reviewers at a new `devtools/docs/reviewers.md` doc, but decided against it because I want these instructions to be maintained in a single location where contributors and reviewers use the same content. This way any changes don't miss one of these sets of users. If reviewers have trouble with this format (dev builds isn't useful to reviewers and some content is repeated from other docs for contributors) then we can consider splitting out to a separate `reviewers.md` file. But until then, I'd like to try sharing this content and see how it works out in practice. PR Close #55406 2024-04-18 19:29:11 +00:00			```