IRC logs for #farmOS, 2026-01-27 (GMT)

2026-01-26
2026-01-28
TimeNickMessage
[09:13:40]<mstenta[m]>I think we need to fix this before we can make a first v4 release: https://github.com/farmOS/farmOS/pull/1028
[09:14:19]<mstenta[m]>See my comment: https://github.com/farmOS/farmOS/pull/1028#issuecomment-3805413241
[09:16:07]<symbioquine[m]>Sounds good to me
[09:17:09]<mstenta[m]>I'll need to dive in and get my head wrapped around the changes they made, and how that conflicts with the changes we made in https://github.com/farmOS/farmOS/pull/922
[09:17:22]<mstenta[m]>Maybe it will be something simple 🤞😅
[09:21:04]<mstenta[m]>I'm releasing v3.5.0 now...
[09:22:22]<mstenta[m]>This will be the last (hopefully) release of the 3.x branch, and it will be necessary to update to 3.5.0 before updating to 4.0.0
[09:23:11]<mstenta[m]>Should be a pretty safe update from 3.4.6. Two minor Drupal core version bumps, though, so follow proper backup/update/testing procedures, as always! :-)
[10:37:27]<mstenta[m]>Blast... I screwed up the 3.5.0 release :-(
[10:38:15]<mstenta[m]>I enabled immutable releases in the farmOS GitHub settings a little while ago... thinking that it would be nice, and was just a checkbox in the settings... but apparently that breaks our GitHub Action for creating the release tarball and attaching it to the release
[10:38:17]<mstenta[m]>So that failed
[10:39:05]<mstenta[m]>Then I tried disabling immutable releases, but that wouldn't let me edit the one that was created. So I deleted that one. And now I'm not allowed to create another release against the 3.5.0 tag, because it had an immutable release associated with it. 🙄
[10:39:22]<mstenta[m]>Makes sense... that's the point of immutable releases... but frustrating nevertheless...
[10:39:50]<mstenta[m]>So as of right now we have a 3.5.0 tag, but not a release on GitHub, and no packaged tarball
[10:40:03]<mstenta[m]>Everything else worked though.
[10:40:35]<mstenta[m]>This only affects folks who are self-hosting and using packaged tarballs... which we are no longer supporting in 4.x (but will still be providing).
[10:40:47]<mstenta[m]>So now I'm not sure what to do...
[10:41:30]<mstenta[m]>I could tag a new 3.5.1 release... but it would only be for this tarball
[10:41:35]<mstenta[m]>That feels wrong, but maybe it's the only option...