@silverpill you should indicate dev builds in the version number
Conversation
Notices
-
Embed this notice
Fox Ritch :fjoxicon:🇩🇪 (fox@social.hostnetwork.xyz)'s status on Monday, 03-Nov-2025 07:18:47 JST
Fox Ritch :fjoxicon:🇩🇪
-
Embed this notice
silverpill (silverpill@mitra.social)'s status on Monday, 03-Nov-2025 07:18:46 JST
silverpill
@fox Why? I don't need that
-
Embed this notice
silverpill (silverpill@mitra.social)'s status on Tuesday, 04-Nov-2025 01:26:08 JST
silverpill
@fox What is a dev build anyway? If you're developing mitra you can change the version.
-
Embed this notice
Fox Ritch :fjoxicon:🇩🇪 (fox@social.hostnetwork.xyz)'s status on Tuesday, 04-Nov-2025 01:26:09 JST
Fox Ritch :fjoxicon:🇩🇪
@silverpill its usefull information to know if a instance is running a dev build
-
Embed this notice
Fox Ritch :fjoxicon:🇩🇪 (fox@social.hostnetwork.xyz)'s status on Tuesday, 04-Nov-2025 16:01:56 JST
Fox Ritch :fjoxicon:🇩🇪
@silverpill dev builds are builds that are compiled with code thats not in a release yet. its a pretty common to have them labled after the latest commit or just -dev
-
Embed this notice
silverpill (silverpill@mitra.social)'s status on Friday, 14-Nov-2025 04:24:03 JST
silverpill
@phnt @fox I added the -dev suffix. Commit / branch could also be added, but I think that for now -dev is enough.
By the way, according to the SemVer spec build information should be added by appending a plus sign:
https://semver.org/#spec-item-10
Hyphens are for pre-releases.
-
Embed this notice
Phantasm (phnt@fluffytail.org)'s status on Friday, 14-Nov-2025 04:24:04 JST
Phantasm
@fox @silverpill Branch information would make more sense, but then it gets ugly when people can't name things (me):
"software": {
"name": "pleroma",
"repository": "https://git.fluffytail.org/phnt/pleroma",
"version": "2.9.1-854-g139a2fc7-fluffytail-dev-url-encode-pt2"
},
-
Embed this notice