The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---On Monday, December 15th, 2025 at 22:06, Goetz Goerisch <[email protected]> wrote: > Hi all, > > Thank you all for catching those bugs. > > As discussed in IRC shortly the other day, 25.12 is build now by the > buildbots. > > To get significant and easy accessible testing we should make sure that these > builds are available in the firmware-selector and more specifically in the > ASU server to test automated upgrades with owut. > > Therefore my question also on the list, how to get 25.12-SNAPSHOT and > 25.12-rc? into https://downloads.openwrt.org/.versions.json > > Thank you, > Goetz Goetz, The -SNAPSHOTs never appear in the .versions.json file, only releases. The ASU server derives the branches from the entries in that file, then creates a big version list, into which it adds '<branch>-SNAPSHOT' for each active branch. So, the only thing that needs to happen is for 25.12.0-rc1 to be set as the value for 'upcoming_version' in https://downloads.openwrt.org/.versions.json and then we'll automatically get the 25.12-SNAPSHOT exposed. But, we don't want to do that until there is actually an RC1, so the 25.12-SNAPSHOT won't become available until then. (To change this behavior would require reworking a whole lot of pieces in several places, I don't think we want to do this.) In any case, I don't know where or what updates .versions.json Paul, Can you tell us when and where .versions.json, and the version-specific .overview.json and .targets.json files are created? https://openwrt.org/docs/guide-developer/releases/making-service-release#check_build_metadata Thanks, Eric
--- End Message ---
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
