[Snyk] Security upgrade @angular/build from 18.0.7 to 18.1.0

[DaveSkender]

This PR was automatically created by Snyk using the credentials of a real user.

 ### Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project. #### Snyk changed the following file(s): - `Client/package.json` - `Client/package-lock.json` #### Vulnerabilities that will be fixed with an upgrade: | | Issue | Score | :-------------------------:|:-------------------------|:-------------------------  | Access of Memory Location After End of Buffer
[SNYK-JS-UNDICI-7361667](https://snyk.io/vuln/SNYK-JS-UNDICI-7361667) |   **62**   --- > [!IMPORTANT] > > - Check the changes in this PR to ensure they won't cause issues with your project. > - Max score is 1000. Note that the real score may have changed since the PR was raised. > - This PR was automatically created by Snyk using the credentials of a real user. --- **Note:** _You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs._ For more information: 🧐 [View latest project report](https://app.snyk.io/org/facioquo/project/0736e56e-478e-498b-8d24-679d3ee5401e?utm_source=github&utm_medium=referral&page=fix-pr) 📜 [Customise PR templates](https://docs.snyk.io/scan-using-snyk/pull-requests/snyk-fix-pull-or-merge-requests/customize-pr-templates) 🛠 [Adjust project settings](https://app.snyk.io/org/facioquo/project/0736e56e-478e-498b-8d24-679d3ee5401e?utm_source=github&utm_medium=referral&page=fix-pr/settings) 📚 [Read about Snyk's upgrade logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Learn about vulnerability in an interactive lesson of Snyk Learn.](https://learn.snyk.io/?loc=fix-pr) [//]: # 'snyk:metadata:{"customTemplate":{"variablesUsed":[],"fieldsUsed":[]},"dependencies":[{"name":"@angular/build","from":"18.0.7","to":"18.1.0"}],"env":"prod","issuesToFix":[{"exploit_maturity":"Proof of Concept","id":"SNYK-JS-UNDICI-7361667","priority_score":62,"priority_score_factors":[{"name":"confidentiality","value":"low"},{"name":"integrity","value":"none"},{"name":"availability","value":"none"},{"name":"scope","value":"unchanged"},{"name":"exploitCodeMaturity","value":"proofOfConcept"},{"name":"userInteraction","value":"none"},{"name":"privilegesRequired","value":"none"},{"name":"attackComplexity","value":"high"},{"name":"attackVector","value":"network"},{"name":"epss","value":0.01055},{"name":"isTrending","value":false},{"name":"publicationDate","value":"Tue Jun 25 2024 07:31:25 GMT+0000 (Coordinated Universal Time)"},{"name":"isReachable","value":false},{"name":"isTransitive","value":true},{"name":"isMalicious","value":false},{"name":"businessCriticality","value":"high"},{"name":"relativeImportance","value":"medium"},{"name":"relativePopularityRank","value":98},{"name":"impact","value":2.35},{"name":"likelihood","value":2.61},{"name":"scoreVersion","value":"V5"}],"severity":"medium","title":"Access of Memory Location After End of Buffer"}],"prId":"7fa7ca89-db3e-4b5f-9839-227791d3cc30","prPublicId":"7fa7ca89-db3e-4b5f-9839-227791d3cc30","packageManager":"npm","priorityScoreList":[62],"projectPublicId":"0736e56e-478e-498b-8d24-679d3ee5401e","projectUrl":"https://app.snyk.io/org/facioquo/project/0736e56e-478e-498b-8d24-679d3ee5401e?utm_source=github&utm_medium=referral&page=fix-pr","prType":"fix","templateFieldSources":{"branchName":"default","commitMessage":"default","description":"default","title":"default"},"templateVariants":["updated-fix-title","priorityScore"],"type":"auto","upgrade":["SNYK-JS-UNDICI-7361667"],"vulns":["SNYK-JS-UNDICI-7361667"],"patch":[],"isBreakingChange":false,"remediationStrategy":"vuln"}'

[cloudflare-pages[bot]]

Deploying stock-charts with    Cloudflare Pages

Latest commit:	6a22923
Status:	🚫  Build failed.

View logs

[github-actions[bot]]

Hey there and thank you for opening this pull request! 👋🏼

It looks like your proposed Pull request title needs to be adjusted.

🚩 Error » No release type found in pull request title "[Snyk] Security upgrade @angular/build from 18.0.7 to 18.1.0". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

  Pull request title naming convention

  Our PR title name taxonomy is type: Subject, where type is typically feat, fix, or chore, and subject is a phrase (proper noun) that starts with a capitalized letter. The chore type usually has a subject that starts with an action verb like Add or Update. Examples:

  • feat: Admin portal login - fix: Divide by zero in X calculation - chore: Update packages - docs: Improve setup guidance See the Conventional Commits specification for more information.