Package Details: standardnotes-bin 3.195.13-1

Git Clone URL: https://aur.archlinux.org/standardnotes-bin.git (read-only, click to copy)
Package Base: standardnotes-bin
Description: Free, open-source encrypted notes app.
Upstream URL: https://github.com/standardnotes/app
Keywords: electron encrypted-notes encryption journal note-taking notes standard-notes
Licenses: AGPL3
Conflicts: standardnotes-desktop
Provides: standardnotes-desktop
Submitter: plague-doctor
Maintainer: dataprolet
Last Packager: dataprolet
Votes: 21
Popularity: 0.38
First Submitted: 2020-12-07 23:34 (UTC)
Last Updated: 2024-11-11 17:00 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

yochananmarqos commented on 2023-08-24 15:46 (UTC)

@proledatarian: No, the AppImage is updated along with the Pre-Releases. I only update when there is a Release on GitHub which is currently 3.169.32.

They also mentioned one can use the GitHub API to fetch it in a script as documented here. All that is a little over my head.

dataprolet commented on 2023-08-24 14:50 (UTC) (edited on 2023-08-24 14:58 (UTC) by dataprolet)

@yochananmarqos Thanks for investigating. So the release on the website is indeed the latest and Github is lacking behind.
EDIT: I don't like it, that behavior totally defeats the purpose of enabling notifications for releases of the Github repo. I was wondering why I only get mails about pre-releases, but never for releases. I guess I will also write the devs a mail, because there must be a better way for package maintainers that to blindly package pre-releases without really knowing whether those are actual releases or not.

yochananmarqos commented on 2023-08-15 15:01 (UTC)

@proledatarian: Follow up email reply:

If you need to know which one is marked as the latest release, you can also use the desktop app itself for reference. Whenever the desktop app notifies you of a new update, the version marked as the latest there is also the one marked as the latest on our repository.

yochananmarqos commented on 2023-08-14 21:32 (UTC)

@@proledatarian: Not much of an answer, but this is the response I received:

Apologies for the confusion! We do not immediately mark each new release as the latest on Github, because if we did, the updates would be much too frequent on the user's end. Similarly, this would mean that you'd have to constantly pull in a new version as we push new changes. However, if you do download the app from our website, it will immediately direct to the latest build that is live with the latest changes on the web app.

yochananmarqos commented on 2023-08-12 00:46 (UTC)

@proledatarian: That's a very good question. Upstream issues are disabled, so I sent them an email.

dataprolet commented on 2023-08-11 08:32 (UTC)

@yochananmarqos Thanks, but why are they releasing other versions on their website?
Here the latest version is .23 and it was .21 yesterday: https://standardnotes.com/download.

yochananmarqos commented on 2023-08-10 21:35 (UTC) (edited on 2023-08-10 22:47 (UTC) by yochananmarqos)

@proledatarian: Again, I only update my standardnotes-desktop to Release tags, not Pre-Release tags. I also only flag this package out of date when there is a Release to help you follow them as well. Today, 3.169.20 and 3.169.22 were Releases while 3.169.21 was a Pre-Release.

dataprolet commented on 2023-06-03 09:11 (UTC) (edited on 2023-06-03 09:12 (UTC) by dataprolet)

@yochananmarqos Thanks, will do.

yochananmarqos commented on 2023-06-02 22:53 (UTC)

@proledatarian: Ignore the Pre-Releases, just watch for when a Pre-Release graduates to a Release. 3.160.19 is the current Release.

dataprolet commented on 2023-05-25 10:17 (UTC) (edited on 2023-05-25 10:18 (UTC) by dataprolet)

This application gets updated upstream regularly and I will only update this package for major versions e. g. from v3.159.X to v3.160.X, but e. g. not from v3.159.1 to v3.159.2.
This results in this package being flagged out-of-date quite often.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »