Signal Forms graduating to public API — what's next for ng-forge #391

The Angular team has just announced that Signal Forms are graduating from experimental to public API in Angular v22. The PR (#68581) replaces @experimental with @publicApi 22.0 across all signal forms APIs under packages/forms/signals.

This is a significant milestone for the underlying foundation ng-forge is built on, so we wanted to share what it means for the library going forward.

The road to v1.0

1. Angular v22 release & port

Once Angular v22 lands and the tools we depend on (Nx, etc.) update to support it, we'll publish a release of ng-forge that targets the now-stable signal forms APIs.

2. Final stabilization period

Following the v22 port, we'll enter a final stabilization phase. The goal is to lock in the current ng-forge APIs ahead of v1.0. We expect this to run for roughly a couple of months — long enough to incorporate further feedback from the community and let adoption continue to grow.

3. v1.0

After stabilization, ng-forge hits 1.0. 🚀

Thank you

This is a good moment to pause and say it clearly: thank you to every contributor, every early adopter, and everyone who has taken the time to open an issue, send a PR, or share feedback in any form. The library's growth is entirely thanks to you, and the path to 1.0 is something we're walking together.

If you have feedback on the current API surface, now is the time — please open a discussion or an issue. The stabilization window is exactly when this input has the most impact.