+1

We will also optimize the verification process and version details.

Best Regards,
Delei

On Mon, Jan 26, 2026 at 10:58 AM Shuxin Pan <[email protected]> wrote:
>
> Hi everyone,
>
> I would like to propose the release of Apache Fesod (Incubating)
> 2.0.1-incubating.
>
> Context regarding 2.0.0-incubating: Although the vote for 2.0.0 passed
> and artifacts were synced to Maven Central, we identified a critical
> issue: the Maven dependency could not be correctly imported by users.
> The root cause was that in the fesod-shaded module, the published POM
> incorrectly kept the ${revision} variable due to maven-shade-plugin's
> behavior, leading to resolution failure.
>
> As Maven Central artifacts are immutable, we have abandoned
> 2.0.0-incubating and will move forward with 2.0.1-incubating.
>
> Key Changes in 2.0.1-incubating:
>
> Fix (Version Strategy): To prevent similar issues, we have decoupled
> the version of the shaded module. We have hardcoded the fesod-shaded
> version to 2.0.0-incubating. Since this module is stable and rarely
> changes, fixing it to this stable version ensures the published POM is
> always fully resolved and safe for users.
>
> Improvement: The release process now enforces a fresh git clone for
> every build to ensure a clean environment (no node_modules or empty
> folders), as requested in previous feedback.
>
> I have verified the fix locally. If there are no objections, I plan to
> start the official vote for 2.0.1-incubating RC1 later today.
>
> Best,
> Shuxin Pan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to