Support for pre-release version numbers

Photoshop UXP Plugin API
,
1

Hi everyone,

is there any way to use pre-release numbers in the manifest?
For example:

{
  "name": "com.test.plugin",
  "version": "1.0.0-build0",

For what I’ve seen in the docs and doing some tests, Photoshop only accepts plugins that have a version number with the format <MAJOR>.<MINOR>.<PATCH>; but having pre-release versions would be quite helpful.

Regards,
A

1 Like
2

May I ask what’s the use case?

I don’t think plugin would pass the approval on the marketplace while it’s not ready to be released anyway :thinking:

3

It’s for internal use, mainly. We are deploying quite often a development version of the plugin for testing.

The pre-release number would help to keep track of what worked/broke in each dev deploy, instead of having to increase the patch number (for example) to have unique version numbers.

2 Likes
4

Just checked, and at least Dev Tools allow you to load such version. But yes, it wouldn’t allow to install via CCD

5

You’re right, it does load. However it seems that Photoshops cuts that part from the version number.

With 1.0.0-build0 as the version, the following code prints 1.0.0:

import { versions } from "uxp";
console.log(versions.plugin);
6

I have “customData” property in manifest and i put build details inside. No problems.

3 Likes
7

Thanks for sharing this workaround, @Jarda.

We have a similar need as @AAA - rapid development and deployment of internal studio tools that go through an alpha and beta test cycle. The pre-release versions are deployed, but only to our testers.

It seems to me that the UXP manifest and the host apps should support full Semantic Versioning.

1 Like
8

@Jarda thanks for the tip!
@joshy Yeah, we have the same situation. That’s why full support of semantic versioning as you suggest would be a huge help.