Repository navigation
sync: release/11.14.0 (sba-internal → sba-angular) - #326
Merged
Merged
Conversation
- Karma was the only remaining source of the brace-expansion advisory (GHSA-mh99-v99m-4gvg, 12 high) through glob@7/minimatch@3/rimraf@3. Only brace-expansion@5 is patched and it is API-incompatible with minimatch@3, so no override could fix it; dropping Karma was the way out. - karma is an optional peer of @angular/build, so removing it also clears the @angular/build and @angular-devkit/build-angular findings. npm audit at the workspace root now reports 0 vulnerabilities. - test-setup.ts installs a ProxyZone per spec: zone.js only patches Jasmine/Jest/Mocha, so waitForAsync fails under Vitest without it. It also restores what Jasmine did implicitly (spies reset between specs and stubbed rather than called through, en-US locale) and fills the matchMedia/scrollIntoView gaps left by jsdom. - The unit-test builder compiles templates AOT where Karma used JIT, hence the wider tsconfig.spec includes and three adjusted TestBed setups. - Same 254 specs as before, all passing.
- Replace docusaurus-lunr-search with @easyops-cn/docusaurus-search-local, configured with docsRouteBasePath '/' since the classic preset serves the docs at the site root. - Drop patch-package along with the gray-matter patch and the js-yaml override it needed. - Bump the docs deploy workflows to Node 20. - The remaining npm audit findings under docusaurus/ are all the same brace-expansion advisory, reported upstream as having no fix available.
…vulnerabilities ES-32972 #done ES-32915 #done ES-32914 #done ES-32913 #done ES-32912 #done ES-32857 #done ES-32856 #done ES-32855 #done ES-32992 #done ES-32991 #done ES-32989 #done ES-32987 #done ES-32984 #done ES-32983 #done
…elease/11.14.0 # Conflicts: # package-lock.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Synchronisation de la branche
release/11.14.0depuis le repo internesba-internal.Contenu
test: replace Karma with Vitest— suppression deskarma.conf.js/test.ts, ajout detest-setup.tsetvitest-globals.d.ts, migration des specschore(docs): upgrade docusaurus to 3.10DEVOPS-468— ajout de.gitlab-ci.ymlrelease/11.10.0→release/11.14.0Résolution de conflit
Le merge de
origin/release/11.14.0danspublic/release/11.14.0a produit un conflit surpackage-lock.json, résolu en retenant la version interne : lepackage.jsonissu du merge est strictement identique à celui desba-internal, le lock interne est donc le seul cohérent.docusaurus/package-lock.jsona été réaligné sur la version interne pour la même raison.Les
npm audit fixpropres à ce dépôt et postérieurs à la base commune sont écartés par ce choix — à rejouer côté public après merge si des vulnérabilités subsistent.🤖 Generated with Claude Code