I guess that it's probably a good idea to release these changes. -- Josh Tynjala Bowler Hat LLC https://bowlerhat.dev/
On Fri, Apr 3, 2026 at 10:32 AM Yishay Weiss <[email protected]> wrote: > Hi all, > While preparing the 1.0.0 release, I found that both compiler-jburg-types > and compiler-build-tools have accumulated unreleased changes spanning > several years, despite multiple Royale releases shipping in that time. > compiler-jburg-types (last released: 1.1.0, September 2019) > > * 4 unreleased changes dating back to September 2022 > * Includes security updates (commons-lang3, commons-compress) and Java > 11 minimum > > compiler-build-tools (last released: 1.2.1, November 2020) > > * 15 unreleased changes dating back to November 2020 > * Includes security updates (Guava, commons-io, commons-compress, > commons-lang3, maven-core, plexus-utils) and Java 11 minimum > > Royale 0.9.10, 0.9.11, and 0.9.12 were all released while these changes > sat unreleased. The builds weren't broken — the compiler POM still > references the old released versions from Maven Central — but the security > fixes and improvements never made it into those releases. > Am I understanding this correctly? Should we release compiler-jburg-types > and compiler-build-tools before Royale 1.0.0 ? >
