Abp update with Volo.Abp.Cli does not upgrade to the correct version

[keremcep]

Is there an existing issue for this?

• I have searched the existing issues

Description

I am using version 9.1.0 and I am waiting for the update command to upgrade the packages to version 9.1.0 but it says 9.0.2 is up to date

Reproduction Steps

No response

Expected behavior

No response

Actual behavior

No response

Regression?

No response

Known Workarounds

No response

Version

9.1.0

User Interface

Common (Default)

Database Provider

EF Core (Default)

Tiered or separate authentication server

None (Default)

Operation System

Windows (Default)

Other information

No response

[maliming]

hi @skoc10

Should we update the https://github.com/abpframework/abp/blob/dev/latest-versions.json ?

[skoc10]

hi @skoc10

Should we update the https://github.com/abpframework/abp/blob/dev/latest-versions.json ?

After completed 9.1.0 release test @gizemmutukurt update this file with this pr https://github.com/abpframework/abp/pull/22284/files

[xxxJotaxxx]

@skoc10 Hello everyone, I hope you're doing well.

I've always had this question about Volo.Abp.Studio.Cli. For example, it's currently at version 0.9.23, but when I initialize or update a project, it uses release 9.0.4. However, in ABP's official repository, the latest version is already 9.1.0. Aren't they in sync?

I thought that whenever a new release was uploaded to the official repository, the ABP CLI would automatically sync with that version. However, it's now several versions behind.

Is there a way to know which release version (for example, 9.1.0) Volo.Abp.Studio.Cli is using before running it?

Thanks, and great to greet you all!

[hikalkan]

@xxxJotaxxx ABP Studio and ABP Framework (the core framework & modules) are versioned and deployed separately. This is because ABP Studio is in its early stages and we want to release it more frequently than ABP Framework.

So, when you create a new solution with ABP Studio, it may not use ABP's latest version. In every ABP release, we upgrade the startup templates (that you create solutions from), test it, migrate (make changes) if necessary. Then it is shipped with the next ABP Studio version. We do our best to keep them in sync (or close).

However, that is not a big problem. After creating a new solution with ABP Studio, you can immediately upgrade your solution to the latest stable ABP version. Just be careful if there are some changes you should do in your solution after the upgrade operation (You can check it in the migration guides: https://abp.io/docs/latest/release-info/migration-guides).

Is there a way to know which release version (for example, 9.1.0) Volo.Abp.Studio.Cli is using before running it?

No, just create a dummy project and see it :)

[berkansasmaz]

Is there a way to know which release version (for example, 9.1.0) Volo.Abp.Studio.Cli is using before running it?

As a small addition, you can refer to the version mapping document for this.

[JoelAuren]

Thank you all for the clarifications. As a small suggestion regarding Volo.Abp.Studio.Cli, it wouldn't hurt to add the release version on which the solution is being generated here.

[berkansasmaz]

Thank you all for the clarifications. As a small suggestion regarding Volo.Abp.Studio.Cli, it wouldn't hurt to add the release version on which the solution is being generated here.

Thanks for the suggestion. We have an internal issue similar to this, I am adding your suggestion there as an extra note.