Releases: angular-schule/angular-cli-ghpages
v1.0.0-rc.1
This release adds support for Angular v11. 🎉
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
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 theGH_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)
v0.6.1
This release has mainly improvements in error handling. It is now again possible to receive detailed logging messages using the --no-silent
option. Furthermore, the deployment is aborted if the previous build fails (thanks to @masaxsuzu).
Fixes
v0.6.0
First stable release after v0.5.3. Please update.
This is a big rewrite that will allow invoking angular-cli-ghpages
via ng deploy
.
Example:
ng new your-angular-project --defaults
ng add angular-cli-ghpages
ng deploy --repo=https://github.com/angular-schule/angular-cli-ghpages-testdrive.git
Features
- Implements an Angular CLI builder (PR #60, closes #59) -- many thanks to @mgechev
- Updated documentation about configuration via
angular.json
(PR #68, closes #67) -- many thanks to @dianjuar - Implements the conventions from ngx-deploy-starter RFC #1
Furthermore I thank @SoAsEr, @TrevorKarjanis and @fmalcher for their help.
0.6.0-rc.2
Docs fixed
- the example
--base-href
for a non-custom domain should be terminated with a slash. - no code changes
fixes #62
Many thanks to @TrevorKarjanis.
0.6.0-rc.1
0.6.0-rc.0
This is a big rewrite that will allow invoking angular-cli-ghpages
via ng deploy
.
Deployments via Angular CLI will be available in @angular@next
(v8.3.0-next.0 or greater)
Example:
ng new your-angular-project --defaults
ng add angular-cli-ghpages@next
ng deploy --repo=https://github.com/angular-schule/angular-cli-ghpages-testdrive.git
Please note: In the past this project was a standalone program (e.g npx angular-cli-ghpages
). This is still possible! See the documentation at README_standalone.
0.5.3
0.5.2
New feature:
- also adds the commit subject and body, when executed on Travis CI
v0.5.1
New Features:
- copies
index.html
to404.html
by default (avoids 404 errors on github pages), fixes #10 - new
--dry-run
option (gives detailed information about what would happen without doing anything)
Bugfix:
- the script exited with a warning:
Unhandled promise rejections are deprecated.
-- exits now with code 1 instead, fixes #11