Thanks. I will fix it. 👍
hi
The design of CreatorId is nullable. Because when you create an entity, there may not be a valid user in the context here
error Error: ENOENT: no such file or directory, open '/home/runner/.cache
Maybe this error is related to setup-node and yarn in pipeline.
https://github.com/actions/setup-node/issues/443
hi
The package name should be @abp/ng.theme.shared, we will fix it in next patch version.
hi
https://abp.io/docs/latest/modules/setting-management#angular-ui
hi
Ok, I will ask our angular team to confirm this.
Is dotnet tool install -g Volo.Abp.Cli still a valid command or obsolete?
You can continue to use Volo.Abp.Cli for 8.x project.
If you use the new 9.0 you can use Volo.Abp.Studio.Cli
Is it necessary to run abp install-libs?
Yes, you need to run it whatever using Volo.Abp.Cli or Volo.Abp.Studio.Cli
Why install-libs used to have 4 successful steps, but not it only has 2?
Beacuse you are using the Volo.Abp.Studio.Cli right now.
Is it still recommended to use yarn (v1.22) or npm?
We recommend using yarn
How can I rollback to Volo.Abp.Cli version '8.3.4'?
You can install the Volo.Abp.Cli in your pipeline.
dotnet tool install --global Volo.Abp.Cli --version 8.3.4
This error will happen if you have multiple SDKs installed; it seems you are using the GitHub pipeline. Can you invite me to join to check?
https://github.com/maliming
Tool 'volo.abp.cli' failed to update due to the following:
The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package.
Tool 'volo.abp.cli' failed to install. Contact the tool author for assistance.
hi
I have checked the source code, It doesn't support your case. : (
hi
Can you share a test project with these entities?
I will download it and try to check the event.
Thanks
liming.ma@volosoft.com
hi
Can you try to remove all docker volumes and re-create docker-dependency again?