bump(main/salty-chat): 0.0.22-p20251006#26796
Conversation
robertkirkman
force-pushed
the
salty-chat-git-source
branch
from
20d9766 to
0349488
Compare
|
A strange error occurred that did not happen in my local test. I will try to find out what happened. |
robertkirkman
force-pushed
the
salty-chat-git-source
branch
3 times, most recently
from
e4aa007 to
85d0e92
Compare
- For some reason, the release archive URL does not work anymore, but downloading the release tag using the git protocol does work. - However, for some reason the current release fails to build in termux-packages GitHub Actions with error ` ../../_cache/go1.25.0-r1/src/os/user/lookup.go:22:41: undefined: current`, but not locally, but the current master branch is not affected by that error, so bump to the newest commit.
robertkirkman
force-pushed
the
salty-chat-git-source
branch
from
85d0e92 to
745c06a
Compare
robertkirkman
changed the title
|
I don't understand exactly what happened, but it was consistently reproducible only in termux-packages GitHub Actions and I discovered that it goes away if the newest version in the master branch of saltyim is used, and it would probably take a really long time to bisect which exact commit fixes that in GitHub Actions, so I am just bumping it to the newest commit to resolve that. |
|
I'm guessing it's some hiccup between our CI and their Gitea backend. |
|
Logically, it couldn't have been since it was passing the |
|
I'm rebasing the Golang PR against 1.25.2 right now. |
|
sure, merging now |
2 participants
For some reason, the release archive URL does not work anymore, but downloading the release tag using the git protocol does work.
However, for some reason the current release fails to build in termux-packages GitHub Actions with error
../../_cache/go1.25.0-r1/src/os/user/lookup.go:22:41: undefined: current, but not locally, but the current master branch is not affected by that error, so bump to the newest commit.