Version naming changed after Dev Platform update - Removed Handle Config?

Hey,

After the Dev Platform update, I’ve noticed the “handle“ value is no longer used for naming versions?

Previously when we would deploy our app, the version would be automatically generated as:

[handle]-[deployment number]

Where as now after the dev platform update, the versions are named as:

app-[deployment number]

How can I get this working the way it did previously? Where instead of just saying “app“ it is the handle for my app?

Hi @Drew_Loynes,

What is the practical impact of this change for you? Note you can set this value yourself with the --version argument:

Hey thanks for getting back to me!

It’s not a massive practical impact. We liked using these version names as tags on our repo for different app releases (So its easy for us to refer to an app versions code and config).

Is there any other way we would be able to get the previous functionality?
Or has this changed permanently now?

p.s. Does the “handle” config variable do anything now?

Handle is primarily used for your app’s URL in admin:

Our intended mechanism for making this version name friendly or meaningful is the --version argument. You could use a custom name, a commit hash, or a date tag.

Are you saying though that the prefix on your version names is just app-? It should still reflect your own app.

Thanks for the info and helping out.

Yes exactly. The prefix on our version names are always “app-“ after the dev platform change. It does not reflect the app. Was partly wondering if this was an intentional change?

Can I ask what the value is of your app’s name field?

So all the name are the names of our app (not sure if I should be saying the actual name so lets just call it “My App“). But there’s also brackets to define which environment the app is for.

So the name for our dev environment looks like:
”My App (Dev)”

And test looks like

”My App (Test)”

So it contains spaces and brackets if thats an issue?

Hi @Drew_Loynes

We determined that on Dev Platform the version name is currently originating from the app name in the package.json, or the current folder name if that doesn’t exist. I’ve registered feedback on this change in behavior.

-Nick

Hi @Drew_Loynes

Just updating that this has been fixed in CLI v3.87.0, the default version naming is once again based on the app handle.

-Nick