help request: Has this repository been abandoned?

[Chivenh]

Description

It has been a long time since the last update

Environment

• APIPark version: 1.9.6-beta
• Operating system (run uname -a):

[Dot-Liu]

Yes, we are still planning the future development of the features. If you have any good ideas, please feel free to share them.

[daveCode-dot]

The 1.9.6-beta tag on the latest release makes it hard to assess stability for production deployments — the "beta" label without a visible path to 1.9.6 stable creates uncertainty beyond just activity concerns.

What would concretely address this for users evaluating adoption: a public milestone on GitHub showing what's blocking 1.9.6 stable, or a CHANGELOG entry noting which known issues remain open before GA. Without that, users building on APIPark can't distinguish "actively developed but slow" from "maintenance mode."

Since @Dot-Liu confirmed development is ongoing, the practical gap is between internal planning and public visibility. A GitHub Projects board or even a pinned issue listing the next release's scope would resolve most of the "is this abandoned?" questions without requiring a code change. That kind of transparency also tends to attract contributors who can accelerate the timeline — right now there's no clear surface for someone wanting to help to identify where effort is needed.

What's the expected timeline or remaining blockers for moving 1.9.6 from beta to stable?