mirror of
https://github.com/certimate-go/certimate.git
synced 2026-04-25 20:55:52 +03:00
[GH-ISSUE #762] 🚨 v0.4.x Roadmap #514
Labels
No labels
announcement
backlog
bug
declined
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
invalid
pull-request
question
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/certimate#514
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 @fudiwei on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/762
v0.4.x 是一个与 v0.3.x 及更早版本不兼容的大版本。
我们将在首个 v0.4.0 正式版本发布时提供平滑迁移方案,以便用户保留已有数据。
路线图:
工作流迭代器节点,支持循环调用部署,大幅简化同一提供商批量部署的场景。(见评论)登录时支持 TOTP 等双重因子验证。(见评论)本路线图仅代表 v0.4.x 整个生命周期过程中的工作计划,但不保证首个 v0.4.0 正式版本发布时会全部完成,各项内容的展示顺序也并不代表实际的开发优先级。
在 v0.4.0 正式版本发布前,0.3.x 仍将继续迭代。
P.S. 此 Issue 仅用于公示信息,请勿在此 Issue 下反馈 Bug 或 Feature Request。如有需要请单独开启 Issue。
v0.4.x is a major version that is not backward compatible with v0.3.x and before.
We will provide a smooth migration solution when v0.4.0 is released, allowing users to retain their existing data.
Roadmap:
Workflow iterator node, enabling loop-based deployment calls, greatly simplifying batch deployment scenarios for the same provider.(comment)Supports MFA (such as TOTP) on logging-in.(comment)This roadmap represents the planned things for the entire v0.4.x life-cycle, but it does not guarantee that all of these will be available in the first stable v0.4.0 release. The order in which the items are displayed does not reflect the actual priority.
Before the release of v0.4.0, 0.3.x will continue to receive updates.
P.S. This issue is intended for public information only. Please do not report bugs or feature requests here. For those, please open a separate issue.
@fudiwei commented on GitHub (Nov 17, 2025):
自 v0.4.5 版本起,几乎所有部署提供商都已支持基于通配符或基于证书的域名匹配模式,已能满足绝大部分的批量部署场景。
因此,“工作流迭代器节点” 这一需求的优先级降低,不再作为 v0.4.x 的工作重点。但它仍然是我们的目标之一,在未来的某些时候仍会考虑实现它 —— 只是不是现在。
@fudiwei commented on GitHub (Feb 9, 2026):
基于当前版本的 PocketBase 来实现 MFA 并不容易,且与 PocketBase 的路线图可能存在冲突( https://github.com/orgs/pocketbase/projects/2/views/1?pane=issue&itemId=125610209 )。
因此,“登录时支持 TOTP 等双重因子验证”这一需求将被推迟到 PocketBase 支持该特性后重新排期。
现阶段你可以使用 Tinyauth 或其他方案。