documentation publish failing

[shubhamparikh927]

Overview

• Updated the release.yml to remove the unwanted CP command for angular routing

How it was tested

• Tested the documentation publish job by temporarily updating the workflow to run on PR and commenting out npm publish job

Checklist

• The title contains a short meaningful summary
• I have added a link to this PR in the Jira issue
• I have described how this was tested
• I have included screen shots for changes that affect the user interface
• I have updated unit tests
• I have run unit tests locally
• I have updated documentation (including README)

[semicolin]

I don't think this is the right solution. If you run a build locally and look at the dist dir, the application is now under a /browser subdir. We will need to append /browser to the paths in build-docs job.

I think the cp command is still needed. The Angular 17 documentation for deploying to GitHub pages still has this step:

5. When the build is complete, make a copy of docs/index.html and name it docs/404.html.

[shubhamparikh927]

I don't think this is the right solution. If you run a build locally and look at the dist dir, the application is now under a /browser subdir. We will need to append /browser to the paths in build-docs job.

I think the cp command is still needed. The Angular 17 documentation for deploying to GitHub pages still has this step:

5. When the build is complete, make a copy of docs/index.html and name it docs/404.html.

I have tested it as you suggested, It's working, But now how should I have to publish the documentation as it runs on the new release. Should I have to release a new version for that?

[semicolin]

I don't think this is the right solution. If you run a build locally and look at the dist dir, the application is now under a /browser subdir. We will need to append /browser to the paths in build-docs job.
I think the cp command is still needed. The Angular 17 documentation for deploying to GitHub pages still has this step:

5. When the build is complete, make a copy of docs/index.html and name it docs/404.html.

I have tested it as you suggested, It's working, But now how should I have to publish the documentation as it runs on the new release. Should I have to release a new version for that?

No need to release a new version. Just deploy it from this branch like you did before and verify that the documentation site is working.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud