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

v1.0.0-rc.2

This release adds support for Angular v12. 🎉

Features

• support for Angular 12, many thanks @icepeng and @dianjuar fixes #131 via #132

v1.0.0-rc.1

This release adds support for Angular v11. 🎉

---

⚠️ 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.

Features

• support for Angular 11, many thanks goes to @beeman 🐝, see PR #118 and PR #120, fixes #119

Fixes

• fix(engine): remove extraneous slash from extended commit message for GitHub Actions, see PR #91 by @EdricChan03
• fix(tooling): fix jest types (24d9922), as explained in angular-schule/ngx-deploy-starter#7 (comment) by @dianjuar
• fix(tooling): improve prettier formatter (891ee8c), as reported in angular-schule/ngx-deploy-starter#10

v0.6.2

With this release, GitHub Actions becomes a first citizen alongside Travis CI and CircleCi.

Learn everything you need to know in the following article.

Everything GitHub: Continuous Integration, Deployment and Hosting for your Angular App

In this article we show several tools from the GitHub universe to launch a website with Angular. We will establish a professional pipeline, including version management, continuous deployment and web hosting. Best of all, for public repositories, this will not cost you a single cent! Read more...

---

tl;dr

The token GITHUB_TOKEN is now supported. When using any token (GH_TOKEN / PERSONAL_TOKEN / GITHUB_TOKEN), it is no longer necessary to specify the --repo parameter if the directory already has a remote repository. This is the case for GitHub actions. Please note that for GitHub actions git config user.name and git config user.email are not set. You still have to provide them.

ℹ️ Note

The GITHUB_TOKEN (installation access token) will only trigger a release of a new website if the action runs in a private repository. In a public repo, a commit is generated, but the site does not change. See this GitHub Community post for more info. If your repo is public, you must still use the GH_TOKEN (personal access token).

Special thanks goes out to @shhdharmen and @EdricChan03 who pushed this release forward! 👍

Example

A valid main.yml for GitHub Actions in a private repository could look like this:

name: Deploy to GitHub Pages via angular-cli-ghpages

on: [push]

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest

    steps:
    - name: Checkout
      uses: actions/checkout@v2

    - name: Use Node.js 10.x
      uses: actions/setup-node@v1
      with:
        node-version: 10.x

    - name: Prepare and deploy
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      run: |
        npm install
        npm run ng -- deploy --base-href=/the-repositoryname/ --name="Displayed Username" [email protected] --no-silent

A valid main.yml for GitHub Actions in a public repository could look like this:

name: Deploy to GitHub Pages via angular-cli-ghpages

on: [push]

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest

    steps:
    - name: Checkout
      uses: actions/checkout@v2

    - name: Use Node.js 10.x
      uses: actions/setup-node@v1
      with:
        node-version: 10.x

    - name: Prepare and deploy
      env:
        GH_TOKEN: ${{ secrets.GH_TOKEN }}
      run: |
        npm install
        npm run ng -- deploy --base-href=/the-repositoryname/ --name="Displayed Username" [email protected] --no-silent

Features

• chore: extended commit message also for GitHub Actions (4925bc8, fixes #73)
• chore: always discover remote URL (if not set) (c5f7b36, fixes #73, fixes #88)
• chore: support for PERSONAL_TOKEN & GITHUB_TOKEN env vars (1066240, fixes #73, fixes #88)
• chore: adds text: "Uploading via git, please wait" (f9bcf1c, fixes #78)