Activities of "rshapiro"

EntityChangeWithUsernameDto is not a custom Dto it's an ABP DTO that's part of the audit logging namespace and is the return from IAuditLogsAppService.GetEntityChangesWithUsernameAsync.

Yes, I know it's a bug but just wanted to make sure you're aware of the issue and can provide a permanent fix so that future ABP updates don't override my manual fix

Thanks for the help. Had already fixed things manually before my last response. Was just letting you know there is that issue.

Hi,

Yes, the packages are centrally managed. I did this based on your suggestion, after the 10.4 update, to resolve the issues of the vulnerabilites being reported by Scriban and AutoMapper. I've shared the files you requested below.

Directory.Packages.props Whitecap.COE.HttpApi.Host.csproj

Thanks that worked now. One thing I noticed though is that the update changed all the versions for every package in the abpmdl and abpsln to unknown. Now if I try to run the update again it throws an exception indicating that package was not found

I've tried several of the suggestions with no luck. More and more I'm thinking that the fact that I'm stuck on v5.1.1 of LeptonX is the issue because it's pretty old. Not sure how I get it to update

Thanks @maliming will take a look at the AutoMapper options you provided. However, even the 7.0 version of Scriban has security vulnerabilities see https://github.com/advisories/GHSA-24c8-4792-22hx

AI answer doesn't help as this is not two separate issues. Vulnerable nuget packages -> EF Migration / DB updates headache. The v10.5 roadmap says 3rd party updates just want to know if updating these packages is in that.

AI answer did not help but pointed me at table which helped me to answer myself

The browser builder is still supported, so you can keep it as is. After the upgrade, you should not face the build errors you mentioned. Let us know if you need further assistance!

Thanks. The update to Angular 19 did the trick. However, you should add the fact that the update to Angular 19 is required with the update to v9 into the migration guide and outline the actions to take on the couple of optional updates that are part of the Angular 19 updates.

Hello,

Since then ABP 9.1 uses Angular v19, you will need to update your application accordingly. You can follow this guide
https://angular.dev/update-guide

Thank you for your cooperation.

Hi,

Are you certain that updating to Angular 19 will correct this? One of the other forum posts I linked in my initial question indicates they had this issue even with Angular 19.

Going through the Angular 19 upgrade and it's indicating that there's an optional migration to migrate the project to the new build system. Is this something we should or should not do?