Summary

As of this writing, push proxy v5.25.0 was released 5 days ago, but the published assets on Github only include the source code.

Steps to reproduce

As per documentation,

wget https://github.com/mattermost/mattermost-push-proxy/releases/download/v5.25.0/mattermost-push-proxy.tar.gz

Expected behavior

Receive mattermost-push-proxy.tar.gz

Observed behavior (that appears unintentional)

404 Not Found

Hi @agriesser! Yeah, matthaios-easy-bi (who I assume is the OP in this thread too) had reported this on Github and it got fixed after I chimed in. I can confirm that the fix works too, i.e. after cherry-picking the change to my branch the build works again.

Thanks!

Summary

Release v1.47.2 was mentioned in another issue’s comments, and Play Store version has indeed been updated, but that release is missing from Github releases.

Steps to reproduce

Open Github releases page for the project.

Expected behavior

Find release v.1.47.2 (or later).

Observed behavior (that appears unintentional)

The current latest release on Github is 1.47.0.

Possible fixes

I don’t know if it’s related, but v.1.47.0 has been tagged ”changeme” instead of the usual vX.Y.Z pattern.

@FlexW I’ve now rebased and pushed the changes, hope this works for you. I don’t see a way for me to merge this myself here, ”Only those with write access to this repository can merge pull requests.”

I’m up for testing those packages. Would Github allow you to attach a deb to a comment here (perhaps wrapped in a Zip file)?

Confirming as fixed! (Sorry for not getting back sooner, looks like Github failed to notify me.)

Your service keeps asking me to verify my e-mail address over and over again. When I open the verification link from the email, the verification succeeds and the yellow notification goes away, but when I return to the site the next day, the notification has reappeared and I have to go through the whole process again. This has been going on for weeks if not months.

I found one Community Forum thread with the same issue, but the ”solution” there just tells the affected user to contact support. https://github.community/t5/How-to-use-Git-and-GitHub/Continual-repeated-requirement-to-verify-email-address-for-users/td-p/18085

@juliushaertl Is backporting for docs also done as per the manual? It seems pretty straightforward, so I think I can produce those pull requests too, if needed.

@PeterDaveHello done, hopefully right this time! Thanks for guiding me through this (it’s my first pull request, in case you couldn’t tell).

Hi @PeterDaveHello, the issues you mentioned should now be fixed. (I’m making this comment in case you’re not receiving notifications about the fix commits and test automaton pass, but do tell if more fixes are needed.)