Continuous release

[iTrooz]

Continuous release

[AkechiShiro]

Is the project abandoned currently ? There hasn't been much activity on the main branch since 2 years ago, @pd4d10 @shreyas1599

It could be however that the project is close to working all fine and so far it doesn't need much updates, but I'm not sure, I believe dependencies should be kept up to date, continuous release could help with that.

I'm not sure if @iTrooz is still interested and can work on his proposed idea

[DinuruSeniya]

I also support this. The current CI runner fails due to an outdated NodeJS version. However even after fixing that, I still get this error.
ERR : Because git_touch depends on antd_mobile from path which doesn't exist (could not find package antd_mobile at "../ant-design-mobile-flutter"), version solving failed.
It'd be helpful to have an updated app built on new versions of Flutter.

In the meantime, I'd suggest forking and working on it, so you don't need to wait for dev approval.

[iTrooz]

In the meantime, I'd suggest forking and working on it, so you don't need to wait for dev approval.
You mean, maintaining a fork ?

The problem is that

• I don't want to spend time continuously maintaining a project, even if it's just rebasing from time to time
• not many people would even be aware of the fork
• I don't want to work on something that maybe won't be used

Even if you meant just preparing the PR in advance, my last point still apply

[zen0bit]

I am interested...

[Nevarro]

I'd be interested as well. I'm looking for a way to manage Forgejo/Gitea issues on iOS, maybe with push notifications on due dates.

[Nevarro]

@pd4d10 Is there any chance for further development?