-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge main to beta #9
Conversation
Merge Beta to Main
Remove license key
Merge some changes from Beta
All end-to-end (e2e) test-related files and configurations have been removed from the project in this commit. This includes the removal of bootstrap, bulma, material, and primeng demo application e2e assets. The modifications are part of an overall project restructuring for better maintenance and feature delivery.
This commit removes the redundant --dryRun flag from the release and pre-release commands in the GitHub Actions workflow file.
This commit includes a new setup step in the Github Actions release workflow. Specifically, it sets the git user to "NGB Email Release Bot" (noreply@ngb.email), which will be used to handle any git actions during the release process.
The @jscutlery/semver package is updated from version 4.0.0 to 4.1.0. In addition, a number of unnecessary packages are removed from the pnpm-lock file, including older versions of conventional-changelog, conventional-recommended-bump, git-raw-commits, and others.
This commit updates all Angular dependencies from v16.2.5 to v17.0.7. The related Angular libraries and packages, such as '@angular/animations', '@angular/cdk', '@angular/common', '@angular/compiler', '@angular/core' etc. are updated. The modifications in devDependencies are also included. This is an essential step in keeping the project updated with the latest patches and features released by Angular.
Several project.json files have been updated to include new "postTargets" options, along with new "github" and "npm" sections. These additions aim to enhance the execution process with additional deployment and tagging features, specifically for npm and GitHub. Now, tagging and notes for GitHub as well as access settings for npm can be easily managed within the project's configuration.
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
No description provided.