Open N4M3Z opened 9 years ago
I’ve seen the same behavior; sometimes it seems to correspond to what might be a misinterpretation of version numbers as decimals, but otherwise it just seems random.
Sorry about that. It does some weird things sometimes. The problem was the initial design between the server and the updater. The server uses timestamps rather than the version numbers, and people forget to update them, and then the metadata gets a bit weird. I had written a corrective script that runs on the server, but it seems to have stopped working.
I'm doing a complete rewrite of both the server as well as the updater itself. Both are about 90% complete, and so I'll push an update for this workflow when the new server is up and running. The new architecture should be much more stable.
Thanks for the update Shawn, we really appreciate that.
Has there been any progress? Can we help with testing?
Progress has been made. It's in co-development with the new version of the server (as noted), so both are co-evolving.
Both are much more complex but much better code. Public testing will be available soon, and I'll definitely ping anyone who is interested.
Hi Shawn Any progress on this?
I also experience this problem. Has any progress been made on this? Also, would there be any issues using this with the new Alfred version 3?
I would really love a nice workflow package manager to exist but this doesn't seem to be working for me :(
Hi @shawnrice, can you share with us the status of the project? Has the project been abandoned?
I am not sure what the problem is, but for the past 7 months packal updater has been reporting updates only for 4 packages and it seems to be updating them to a wrong version. Is there something wrong with how I am using this plugin?