Is there an existing issue for this?
Description
Running abp new on many versions appears to not work currently.
The context is we're upgrading a project from ABP 7.3.3 to 9.X and as part of that, want to check for changes to the startup template, as per the instructions.
I looked at the source code on abp cli 7.3.3, and I see it checks the requested version against this list here:
https://abp.io/api/download/all-versions?includePreReleases=true
Right now, the most recent version on there is 5.4.0-rc.2.
Have all the 6.0 and beyond releases been removed from the all-versions endpoint?
Reproduction Steps
# ensure you're on abp cli 7.3.3 (for example)
dotnet tool uninstall -g volo.abp.cli
dotnet tool install -g volo.abp.cli --version "7.3.*"
# run abp new on version 7.3.3
abp new Test1 -ui angular --dbms sqlserver --separate-identity-server --version 7.3.3
Expected behavior
Creates the start up template
Actual behavior
Error creating start up template
ABP CLI 7.3.3
Creating your project...
Project name: Test1
Version: 7.3.3
DBMS: SQLServer
UI Framework: Angular
Output folder: <REDACTED>/2026-05-11-abp-template
There is no version found with given version: 7.3.3
System.Exception: There is no version found with given version: 7.3.3
at Volo.Abp.Cli.ProjectBuilding.AbpIoSourceCodeStore.GetAsync(String name, String type, String version, String templateSource, Boolean includePreReleases, Boolean skipCache) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\AbpIoSourceCodeStore.cs:line 93
at Volo.Abp.Cli.ProjectBuilding.TemplateProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\TemplateProjectBuilder.cs:line 66
at Volo.Abp.Cli.Commands.NewCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\NewCommand.cs:line 92
at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 169
at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 77
Regression?
Yes. This worked on exactly the same abp cli version before, but is no longer working, due to this all-versions endpoint appearing to not function as it used to.
Known Workarounds
No response
Version
7.3.3
User Interface
Common (Default)
Database Provider
EF Core (Default)
Tiered or separate authentication server
None (Default)
Operation System
MacOS
Other information
No response
Is there an existing issue for this?
Description
Running
abp newon many versions appears to not work currently.The context is we're upgrading a project from ABP 7.3.3 to 9.X and as part of that, want to check for changes to the startup template, as per the instructions.
I looked at the source code on abp cli 7.3.3, and I see it checks the requested version against this list here:
https://abp.io/api/download/all-versions?includePreReleases=true
Right now, the most recent version on there is
5.4.0-rc.2.Have all the 6.0 and beyond releases been removed from the
all-versionsendpoint?Reproduction Steps
Expected behavior
Creates the start up template
Actual behavior
Error creating start up template
Regression?
Yes. This worked on exactly the same abp cli version before, but is no longer working, due to this
all-versionsendpoint appearing to not function as it used to.Known Workarounds
No response
Version
7.3.3
User Interface
Common (Default)
Database Provider
EF Core (Default)
Tiered or separate authentication server
None (Default)
Operation System
MacOS
Other information
No response