You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't need to get the latest version of each package of Volo.Abp.xxx, we just need to use the latest version of Volo.Abp, because we always release all packages.
This will save a lot of time.
[14:21:05 INF] Updating package "Volo.Abp.BackgroundJobs.Domain" from v2.8.0 to v2.9.0.
[14:21:06 INF] Updating package "Volo.Abp.AuditLogging.Domain" from v2.8.0 to v2.9.0.
[14:21:08 INF] Updating package "Volo.Abp.TenantManagement.Domain" from v2.8.0 to v2.9.0.
[14:21:09 INF] Updating package "Volo.Abp.FeatureManagement.Domain" from v2.8.0 to v2.9.0.
[14:21:10 INF] Updating package "Volo.Abp.SettingManagement.Domain" from v2.8.0 to v2.9.0.
[14:21:11 INF] Updating package "Volo.Abp.Identity.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:13 INF] Updating package "Volo.Abp.IdentityServer.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:14 INF] Updating package "Volo.Abp.BackgroundJobs.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:15 INF] Updating package "Volo.Abp.AuditLogging.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:16 INF] Updating package "Volo.Abp.TenantManagement.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:18 INF] Updating package "Volo.Abp.FeatureManagement.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:19 INF] Updating package "Volo.Abp.PermissionManagement.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:20 INF] Updating package "Volo.Abp.SettingManagement.Domain.Shared" from v2.8.0 to v2.9.0.
[14:21:21 INF] Updating package "Volo.Abp.EntityFrameworkCore.SqlServer" from v2.8.0 to v2.9.0.
[14:21:23 INF] Updating package "Volo.Abp.PermissionManagement.EntityFrameworkCore" from v2.8.0 to v2.9.0.
[14:21:24 INF] Updating package "Volo.Abp.SettingManagement.EntityFrameworkCore" from v2.8.0 to v2.9.0.
The text was updated successfully, but these errors were encountered:
@maliming, you are right, we generally publish all together. But, there are rare cases we only publish a single package patch. I don't want to restrict us and place such a strict rule for just this case. If we later dedice forbid publishing individual packages (because of some strong reasons), we revisit this case and update the CLI.
We don't need to get the latest version of each package of
Volo.Abp.xxx
, we just need to use the latest version ofVolo.Abp
, because we always release all packages.This will save a lot of time.
The text was updated successfully, but these errors were encountered: