mirror of
https://github.com/nextcloud/twofactor_gateway.git
synced 2026-04-27 01:55:52 +03:00
[GH-ISSUE #770] Nextcloud App Store Update #130
Labels
No labels
0. to triage
1. to develop
3. to review
blocked
bug
discussion
duplicate
enhancement
enhancement
gateway:signal
gateway:signal
gateway:signal
gateway:sms
gateway:telegram
hacktoberfest
help wanted
invalid
needs info
php
pull-request
question
technical debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/twofactor_gateway-nextcloud#130
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dora71 on GitHub (Nov 23, 2025).
Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/770
First of all, I am really happy to see a new stable release 2.0.0 of the 2FA Gateway which was released in Octobre 2025.
But when I look at the Nextcloud App Store, there is still only the old Version available, telling that the last activity has been 3 years and 4 months ago.
Are there any steps that have still to be done to get the actual release via the Nextcloud App Store? Is there anything left which stops the actual release being published in the App Store?
Would really love to see the updated version in the Nextcloud App Store.
@vitormattos commented on GitHub (Dec 17, 2025):
@ChristophWurst did you have any news about how to update the app at appstore?
@ChristophWurst commented on GitHub (Dec 17, 2025):
Sure! I've invited you to https://github.com/nextcloud-releases/twofactor_gateway.
Releases work like this
v2.0.0.I test-ran this with v2.0.0 already - worked as expected. If you like you can also do the v1.0.0 release because that one seems missing for Nextcloud 31.
@vitormattos commented on GitHub (Jan 28, 2026):
Hello @ChristophWurst !
I made the flow but the build and publish action didn't started. Could yo check if is this anything related with permissions?
I created the release v1.2.0 and didn't worked.
Also is necessary to publish the releases v2.2.0 and v3.0.0
@ChristophWurst commented on GitHub (Jan 28, 2026):
the v1.2.0 build did happen and it is showing on the app store.
Yes it is necessary that you create a release on the releases clone based on the tag you're pushing.
@vitormattos commented on GitHub (Jan 28, 2026):
I think that was a delay between the release creation and the start of Action. Worked fine now launching the release v2.2.0, thanks!