Hmm, I just noticed that the feed template seems to be broken on your yarnd instance, @kat@yarn.girlonthemoon.xyz. Looking at your raw feed file (and your mates as well), line 6 reads:

# This is hosted by a Yarn.social pod yarn running yarnd ERSION@OMMIT  go1.23.4
                                                         ^^^^^^^^^^^^

Looks like the first letters of the version and commit got somehow chopped off. I’ve no idea what happened here, maybe @prologic@twtxt.net knows something. :-? I’m not familiar with the templating, I just recall @xuu@txt.sour.is reporting in IRC the other day that he’s also having great fun with his custom preamble from time to time.

That “broken” comment doesn’t hurt anything, it’s still a proper comment and hence ignored by clients. It’s just odd, that’s all.

@lyse@lyse.isobeef.org This could just be a bugger Makefile or something. I’m not sure what version @kat@yarn.girlonthemoon.xyz built/deployed from? 🤔🤔 – Also I need to release v2.0 soon™

@prologic@twtxt.net so i did a mistake that i’ve done before and i think i just pulled from the main branch which is STUPID i KNOW and i don’t LEARN but whatever. i was having trouble with my go version and the makefile so i think i literally just ran it as my user with go in the path and redirected the binaries to go to a temporary directory i made and then moved them to /usr/bin lol. i’m not sure what could’ve caused this! probably something in the pipeline of weirdness i just wrote out

@kat@yarn.girlonthemoon.xyz Building from source and from the main branch is totally fine. In fact encouraged. I have a philosophy of main being stable anyway and making sure backwards compatibility is kept in mind when changing things. i.e: No database migrations to run by hand or what not.

Anyway… Sounds like there is a bug with the version logic. I’ll see if I can fix it.

@prologic@twtxt.net ah that’s good lol! i once pulled from main for a huge web app that i deployed and it haunts me because it will make upgrading so much harder lol