-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(test): add bundle size limit #799
Conversation
Nice idea, but I don't think we should add it during the unit tests process, but in a separate test process, because this is not an unit test. We can create a new job during the Github action for it and have some measures:
|
Bumps [aquasecurity/trivy-action](https://github.com/aquasecurity/trivy-action) from 0.19.0 to 0.20.0. - [Release notes](https://github.com/aquasecurity/trivy-action/releases) - [Commits](aquasecurity/trivy-action@d710430...b2933f5) --- updated-dependencies: - dependency-name: aquasecurity/trivy-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* refactor: add new placeholders variables * refactor: get route description from strapi translations
this is a collapsible html tag
* refactor: remove SubflowState * test: add unit tests for navItemsFromDoneStates() + stepStates()
This reverts commit 841c141.
This reverts commit facaaaa.
This reverts commit ad038d2.
what happens to the commit messages Chris? @chohner :O |
Apparently I rebased instead of merge 😢 I'll fix this PR soon, we have way too many |
Quality Gate passedIssues Measures |
Issue: We sometimes bundle large dependencies or data chunks into our bundle. this adds a size limit for the bundle that is checked after unit tests: