[GH-ISSUE #376] Mailpit shows wrong version in about. #245

New issue

Closed

opened 2026-03-15 13:24:47 +03:00 by kerem · 4 comments

kerem commented

2026-03-15 13:24:47 +03:00

Owner

Originally created by @N6REJ on GitHub (Oct 20, 2024).
Original GitHub issue: https://github.com/axllent/mailpit/issues/376

we've verified that we are using 1.20.7 yet it says its 1.20.6

how can we see whats going on?

Originally created by @N6REJ on GitHub (Oct 20, 2024). Original GitHub issue: https://github.com/axllent/mailpit/issues/376 we've verified that we are using 1.20.7 yet it says its 1.20.6 ![image](https://github.com/user-attachments/assets/2214726b-50df-4c65-a1b5-58555317a94e) how can we see whats going on?

kerem closed this issue

2026-03-15 13:24:53 +03:00

kerem commented

2026-03-15 13:24:58 +03:00

Author

Owner

@axllent commented on GitHub (Oct 20, 2024):

Hey @N6REJ. This same thing happened to you before in #359. The release version numbers are set automatically as the release is being compiled and packaged, so this is not technically possible - if you downloaded and installed 1.20.7 then that is what it is.

You can verify on the commandline (in the directory with the mailpit.exe file) by running mailpit version. If that shows you the correct version but the web interface doesn't, then you need to restart your stack because you somehow still have the old version running in memory. If however that is showing you an older version, then you have downloaded the wrong version.

@axllent commented on GitHub (Oct 20, 2024): Hey @N6REJ. This same thing happened to you before in #359. The release version numbers are set automatically as the release is being compiled and packaged, so this is not technically possible - if you downloaded and installed 1.20.7 then that is what it is. You can verify on the commandline (in the directory with the mailpit.exe file) by running `mailpit version`. If that shows you the correct version but the web interface doesn't, then you need to restart your stack because you somehow still have the old version running in memory. If however that is showing you an older version, then you have downloaded the wrong version.

kerem commented

2026-03-15 13:25:04 +03:00

Author

Owner

@axllent commented on GitHub (Oct 20, 2024):

If you need additional support, please provide me the link to your version and I can then manually compare and verify with what's on GitHub in the releases. Thanks.

@axllent commented on GitHub (Oct 20, 2024): If you need additional support, please provide me the link to your version and I can then manually compare and verify with what's on GitHub in the releases. Thanks.

kerem commented

2026-03-15 13:25:09 +03:00

Author

Owner

@N6REJ commented on GitHub (Oct 21, 2024):

Sorry to have bothered you. I looked for the other ticket cause I remembered this happening once before.
I've no clue how but somehow we had the wrong version from your release.

@N6REJ commented on GitHub (Oct 21, 2024): Sorry to have bothered you. I looked for the other ticket cause I remembered this happening once before. I've no clue how but somehow we had the wrong version from your release.

kerem commented

2026-03-15 13:25:14 +03:00

Author

Owner

@axllent commented on GitHub (Oct 21, 2024):

No worries. Seeing as this is the second time this has happened (and assuming they were caused by the same issue), I'm curious as to how you are configuring your versions in the app - it is an automated or manual process?

@axllent commented on GitHub (Oct 21, 2024): No worries. Seeing as this is the second time this has happened (and assuming they were caused by the same issue), I'm curious as to how you are configuring your versions in [the app](https://bearsampp.com/) - it is an automated or manual process?

kerem referenced this issue

2026-03-15 14:22:04 +03:00

[PR #245] [CLOSED] Bump actions/cache from 3 to 4 #494