[GH-ISSUE #417] Cut a release for Flatpak, etc. #267

Closed
opened 2026-02-28 14:31:46 +03:00 by kerem · 6 comments
Owner

Originally created by @jacksongoode on GitHub (May 13, 2023).
Original GitHub issue: https://github.com/jpochyla/psst/issues/417

In order for us to publish to Flathub #141 we need a real semantically versioned release, something that should have been tackled a while ago 😆.

My gut says we just start with 1.0.0 and increment the patch number from there? Maybe it would be good to have an action to do this automatically. @Insprill @TheEvilSkeleton @jpochyla

Originally created by @jacksongoode on GitHub (May 13, 2023). Original GitHub issue: https://github.com/jpochyla/psst/issues/417 In order for us to publish to Flathub #141 we need a real semantically versioned release, something that should have been tackled a while ago 😆. My gut says we just start with `1.0.0` and increment the patch number from there? Maybe it would be good to have an action to do this automatically. @Insprill @TheEvilSkeleton @jpochyla
kerem closed this issue 2026-02-28 14:31:46 +03:00
Author
Owner

@TheEvilSkeleton commented on GitHub (May 14, 2023):

I agree. Otherwise, if you think it's not production ready, then we could start with experimental releases.

<!-- gh-comment-id:1546777636 --> @TheEvilSkeleton commented on GitHub (May 14, 2023): I agree. Otherwise, if you think it's not production ready, then we could start with experimental releases.
Author
Owner

@Insprill commented on GitHub (May 14, 2023):

A major version > 0 indicates a stable application, which psst is not. If we switch to semantic versioning, we'll start at 0.1.0. I haven't used Flatpak before; does it not let us use a git hash for a version? If we are to switch to semantic versioning, I'd like to hear @jpochyla's thoughts.

<!-- gh-comment-id:1547013596 --> @Insprill commented on GitHub (May 14, 2023): A major version > 0 indicates a stable application, which psst is not. If we switch to semantic versioning, we'll start at `0.1.0`. I haven't used Flatpak before; does it not let us use a git hash for a version? If we are to switch to semantic versioning, I'd like to hear @jpochyla's thoughts.
Author
Owner

@jpochyla commented on GitHub (May 15, 2023):

Personally I'd prefer 0.1.0, yes.

<!-- gh-comment-id:1547523199 --> @jpochyla commented on GitHub (May 15, 2023): Personally I'd prefer `0.1.0`, yes.
Author
Owner

@TheEvilSkeleton commented on GitHub (May 15, 2023):

does it not let us use a git hash for a version?

Flatpak (the format) does, but Flathub (the store) prefers semantic versioning

<!-- gh-comment-id:1547802129 --> @TheEvilSkeleton commented on GitHub (May 15, 2023): > does it not let us use a git hash for a version? Flatpak (the format) does, but Flathub (the store) prefers semantic versioning
Author
Owner

@jacksongoode commented on GitHub (May 15, 2023):

I'm good with 0.1.0 - I can close this issue and we can go ahead?

<!-- gh-comment-id:1548265244 --> @jacksongoode commented on GitHub (May 15, 2023): I'm good with 0.1.0 - I can close this issue and we can go ahead?
Author
Owner

@TheEvilSkeleton commented on GitHub (May 15, 2023):

You have my approval

<!-- gh-comment-id:1548405226 --> @TheEvilSkeleton commented on GitHub (May 15, 2023): You have my approval
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/psst#267
No description provided.