You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: eliminate all 'as any' casts and implement audit findings
Critical fixes:
- Fixed prerenderTarget bug in builder.ts (was checking non-existent options.prerender)
- Eliminated ALL 'as any' type casts from entire codebase (0 remaining)
- Added proper type interfaces (AngularOutputPath, DeployUser, etc.)
- Replaced type casts with proper type guards and jest.spyOn mocking
Type safety improvements:
- deploy/actions.ts: Added type guard for outputPath validation
- ng-add.spec.ts: Added AngularJson interface, removed (as any) cast
- edge-cases.spec.ts: Replaced (as any) with DeployUser interface
- All commander-fork tests: Replaced manual mocking with jest.spyOn
Documentation fixes:
- Fixed typos: Github→GitHub in all documentation
- Updated Angular version compatibility (v2.x = 17+, v1.x = 9-16)
- Added workflow comment explaining GITHUB_TOKEN is for CI testing only
Testing improvements:
- Added 3 negative test cases for builder error handling
- Fixed gh-pages mock signature in builder-integration.spec.ts
- Added MockChildProcess interface to gh-pages-shell.spec.ts
All 213 tests passing, build successful, zero type violations.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -190,7 +190,7 @@ ng deploy --repo=https://github.com/<username>/<repositoryname>.git --name="Your
190
190
191
191
> **ℹ️ Note for GitHub Actions**
192
192
>
193
-
> 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](https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/m-p/26869) for more info. If your repo is public, you must still use the `GH_TOKEN` (personal access token).
193
+
> 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](https://github.community/t5/GitHub-Actions/GitHub-action-not-triggering-gh-pages-upon-push/m-p/26869) for more info. If your repo is public, you must still use the `GH_TOKEN` (personal access token).
Copy file name to clipboardExpand all lines: docs/README_contributors.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,8 +31,12 @@ Follow the instructions for [checking and updating the Angular CLI version](#ang
31
31
### 1. Optional: Latest Angular version
32
32
33
33
This builder requires the method `getTargetOptions()` from the Angular DevKit which was introduced [here](https://github.com/angular/angular-cli/pull/13825/files).
34
-
All Angular projects with Angular 9 and greater are supposed to be compatible. (Actually it works with some versions of 8.x too, but you want to be up to date anyway, don't you?)
35
-
Execute the next three steps, if your test project is still older.
34
+
35
+
**Version compatibility:**
36
+
-**v2.x:** Supports Angular 17 and higher (current version)
37
+
-**v1.x:** Supported Angular 9-16 (now deprecated for new projects)
38
+
39
+
Execute the next three steps to update your test project to the latest Angular version.
Copy file name to clipboardExpand all lines: docs/README_environment_github_actions.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# angular-cli-ghpages: README for setting up deployment with GitHub Actions
2
2
3
-
As Github has introduced [Github Actions](https://github.com/features/actions), I would prefer to run all my CI tasks in it only, rather than going to some other CI providers. This guide is aimed to help out developers, who want to deploy their Angular app in Github Page using [angular-cli-pages](https://github.com/angular-schule/angular-cli-ghpages).
3
+
As GitHub has introduced [GitHub Actions](https://github.com/features/actions), I would prefer to run all my CI tasks in it only, rather than going to some other CI providers. This guide is aimed to help out developers, who want to deploy their Angular app in GitHub Pages using [angular-cli-pages](https://github.com/angular-schule/angular-cli-ghpages).
4
4
5
5
## Prerequisites
6
6
@@ -25,9 +25,9 @@ You can use the `GITHUB_TOKEN` to authenticate in a workflow run.
Copy file name to clipboardExpand all lines: docs/README_standalone.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,7 +169,7 @@ Run through without making any changes. This can be very usefull, because it out
169
169
- Example:
170
170
- `npx angular-cli-ghpages --cname=example.com`
171
171
172
-
A CNAME file will be created enabling you to use a custom domain. [More information on Github Pages using a custom domain](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).
172
+
A CNAME file will be created enabling you to use a custom domain. [More information on GitHub Pages using a custom domain](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).
0 commit comments