v3.0.0

Summary

Major release with Angular 20 and Angular 21 compatibility, security fixes, and comprehensive test coverage.

• BREAKING: Require Angular 18+ (drops Angular 17 and earlier)
• Security: Upgrade gh-pages 3.1.0 → 6.3.0 (fixes #185)
• Compatibility: Fix Angular 20+ outputPath handling (fixes #196, #199)
• Stability: Fork commander v3.0.2 to preserve --no- flag behavior
• Quality: >400 tests with near-complete coverage

Closes

• Fixes #199 - Not compatible with Angular 20
• Fixes #198 - Remove the angular-devkit/* in dependencies (switched to >=18.0.0 ranges)
• Fixes #196 - deploy error if outputPath.browser is not set
• Fixes #185 - Critical severity vulnerability (gh-pages upgrade)
• Replaces #186 - Fixing critical vulnerabilities (superseded by this PR)

Breaking Changes

• Minimum Angular version is now 18.0.0
• browserTarget is actively rejected with helpful error message ("Use buildTarget instead")

Key Changes

Angular 20+ Compatibility

• Handle missing outputPath in Angular 20+ projects
• Default browser to 'browser' when outputPath object omits it
• CI tests against Angular 18, 19, 20, and 21

gh-pages v6 Upgrade (Security)

• Fixes critical vulnerability reported in #185
• Native CNAME and .nojekyll file creation (delegated to gh-pages)

Commander Fork

We forked commander v3.0.2 to preserve critical --no- flag behavior that broke in newer versions:

• Angular CLI passes --no-dotfiles as { noDotfiles: true }, NOT { dotfiles: false }
• Modern commander versions changed this behavior
• Our fork maintains backwards compatibility while stripping unused features (subcommands, action handlers)

npm Trusted Publishers

This package now uses provenance statements with OIDC. Every published version includes cryptographic provenance attestation. You can verify that the npm package was built from this exact GitHub repository, from a specific commit, through a transparent CI pipeline. Deployed by @JohannesHoppe.

Improved CI Metadata

• GitHub Actions: Now includes build URL (/actions/runs/{id}) - parity with Travis/CircleCI
• Travis CI: Uses TRAVIS_BUILD_WEB_URL (works for .com and enterprise)

Documentation

• Added --no-notfound and --no-nojekyll to standalone CLI docs
• Various improvements to all documentation files

v2.0.3

This release fixes a bug that was introduced in v2.0.1

Many thanks to @fmalcher for PR #194 (fix: provide default value for remote option) which fixes #193 (issue trying to deploy)
Deployed by @JohannesHoppe.

v2.0.1

This release adds one new feature:

Feature

• Adds --remote option via #191
  Provide the remote name. If no value is provided, origin is used. Has no function if --repo is set.
  Many thanks to @colinvh0!

Deployed by @JohannesHoppe.

v2.0.0

This release adds support for Angular v18. 🎉

Features

• support for Angular 18 (no support for earlier versions! use v2.0.0-beta.1 for Angular 17)
• support for the add parameter. This will only add, and never remove existing files. By default, existing files in the target branch are removed before adding the ones from the dist folder. If you want to add new files but leave existing ones untouched, set the --add parameter.

Installation

ng add [email protected]

Thanks

• Thanks to @isalcedo for PR #188 (support for "add" parameter) 👍
• Deployed by @JohannesHoppe.

2.0.0-beta.1

This release adds support for Angular v17. 🎉

Features

• support for Angular 17 (no support for earlier versions) → support for various buildTargets (similar to angularfire) and recognises different output path configurations (see angular/angular-cli#26675 and angular/angular-cli#26304 (comment))
• completely removes the --no-silent option, error messages will be shown by default now (modern CI systems don't expose secrets anymore)
• adds the --dir option, this overrides the directory for all published sources, relative to the current working directory. The normal logic with buildTargets and conventions is ignored in this case.
• adds the --no-notfound option to not create a 404.html which should work great with Cloudflare pages, see #178 and see the Cloudflare pages docs
• adds a .nojekyll file by default, can be disabled via --no-nojekyll

Install this beta version via

ng add [email protected]

Thanks

• Thanks to @fmalcher for reviewing the PR #179
• Deployed by @JohannesHoppe.

v1.0.6

This release adds support for Angular v16. 🎉

Features

• Compatible with Angular v16 (fixes #167)
• Deploy command should now also run in an Nx repo (fixes #145 via #166)
  Many thanks to @tinesoft for fixing the invalid schema.json file that caused the issue.

Deployed by @JohannesHoppe.

v1.0.5

This release adds support for Angular v15. 🎉

Many thanks to @EdricChan03 for fixing a peer dependency issue. (fixes #158 via #159)
Deployed by @JohannesHoppe.

v1.0.3

This release adds support for Angular v14. 🎉

• many thanks to @fmalcher, this closes #148
• please don't use v1.0.1 or v1.0.2 – both packages are broken
• Deployed by @JohannesHoppe.

v.1.0.0

This release adds support for Angular v13. 🎉

Features

• support for Angular 13, many thanks to @fmalcher, this fixes #138 & #137 via #139
• fix: yarn installs incorrect version, because dist-tag is ignored, fixes #140 via 1c375f9

The code of this version is 100% identical to v1.0.0-rc.3. Only the version number was changed to work around the version resolution of yarn, which ignores npm dist-tags.

---

⚠️ BREAKING CHANGE (v1)

Starting with version 1 the option --configuration was renamed to --build-target.

BEFORE (does not work):

ng deploy --configuration=test

NOW:

ng deploy --build-target=test

If you use the old syntax, you will probably receive the following error:

An unhandled exception occurred: Configuration 'test' is not set in the workspace.

Deployed by @JohannesHoppe.

v1.0.0-rc.3

This release adds support for Angular v13. 🎉

Features

• support for Angular 13, many thanks to @fmalcher, this fixes #138 & #137 via #139