design-system icon indicating copy to clipboard operation
design-system copied to clipboard

chore(deps): update v8 to Angular 19 (major)

Open gfellerph opened this issue 1 year ago • 7 comments

  • @angular-devkit/build-angular,
  • @angular-eslint/builder,
  • @angular-eslint/eslint-plugin,
  • @angular-eslint/eslint-plugin-template,
  • @angular-eslint/template-parser,
  • @angular/animations,
  • @angular/cli,
  • @angular/common,
  • @angular/compiler,
  • @angular/compiler-cli,
  • @angular/core,
  • @angular/forms,
  • @angular/localize,
  • @angular/platform-browser,
  • @angular/platform-browser-dynamic,
  • @angular/router

gfellerph avatar Dec 05 '24 08:12 gfellerph

On hold until cargo is live

gfellerph avatar Feb 20 '25 12:02 gfellerph

Try to add a major changeset on release/v8 and see what happens, main can be update manually later. Every push to main currently creates a release/v9 by mistake. That might have to be fixed before.

gfellerph avatar Feb 27 '25 12:02 gfellerph

Blocked until #4566 is merged,

alizedebray avatar Mar 04 '25 08:03 alizedebray

When can we expect the update to angular 19 for v8?

MonsieurBon avatar Apr 10 '25 11:04 MonsieurBon

We have quite a few dependency updates, that are being blocked by the dependency conflict of the Design System. As far as I understand, the Prime NG package is separate and independent - so would it be possible to add support for Angular 19 in the main packages and lift the Prime NG package when capacity is available, since most projects do not use it?

manuel-rw avatar Apr 28 '25 10:04 manuel-rw

@gfellerph @alizedebray What is the status of this issue?

MonsieurBon avatar May 07 '25 06:05 MonsieurBon

See also https://teams.microsoft.com/l/message/19:[email protected]/1737534314775?tenantId=3ae7c479-0cf1-47f4-8f84-929f364eff67&groupId=123c7c9e-052a-40e6-98d3-6cc6d46bad0a&parentMessageId=1737534314775&teamName=Design%20System&channelName=%F0%9F%9A%91%20Support&createdTime=1737534314775

srudin avatar May 07 '25 07:05 srudin

@alizedebray is working on it as a top priority. It's technically not the easiest feat due to internal repo structure hence the delay. We're sorry to keep you waiting and are looking forward to loosen the tight dependency on a specific Angular version in the future.

gfellerph avatar May 08 '25 15:05 gfellerph