Hi Hernán, On Tue, 08 Sep 2026 12:28:33 +0300 Hernán Ibarra Mejia <[email protected]> wrote:
> On Sat Sep 5, 2026 at 3:50 PM EEST, Mario Domenech Goulart wrote: >> FYI: the changes to make matchertext work with C6 broke the compilation >> for C5: > > Hmm... I'm not so interested in maintaining backwards compatibility with C5. > Would it be possible to either remove the egg from C5 coop, or rollback to the > previous version and freeze it for C5 only? We don't really support unreleasing eggs. One thing that can be done, though, is: 1. Create a branch for the C5 version of your egg 2. Check out a state of the code that worked with C5 3. Tag a new release (make sure the new version is greater than the one currently available for C5) 4. Send us the new egg location, which points to the new branch If you don't want to maintain the C5 code, you can just freeze that branch. Once the new version for C5 is cached, we can even remove the egg from egg-locations to stop looking for updates. It would also be good to explicitly state in the documentation that the egg is unmaintained for C5. All the best. Mario -- https://parenteses.org/mario
