You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Single source of truth for what's planned. Bug reports and feature requests should go into their own issues — this one stays high-level.
v1.x — ongoing (small fixes & features)
Released since project start: v1.7.0 → v1.17.4. Recent landings: container groups, maintenance mode, group/topic auth fix, BOT_LABEL, healthcheck improvements, /changelog command. See CHANGELOG.md for the full list.
💬 Interactive Discord bot — slash commands + components matching the current Telegram surface (own issue once requirements are clearer)
v2.0 will start when there's enough user feedback and momentum to justify the architectural refactor. If those features matter to you, ⭐ the repo or mention Docksentry to someone who'd benefit — that's the signal I'm watching.
How to participate
Bug? New issue with the bug label, reproduction steps, Docksentry version, container runtime info.
Feature idea? New issue with enhancement — describe the use case before suggesting a specific implementation.
Open discussion?#2 stays as the community discussion thread.
This issue gets edited as state changes — comments welcome but the top description is the canonical status.
Single source of truth for what's planned. Bug reports and feature requests should go into their own issues — this one stays high-level.
v1.x — ongoing (small fixes & features)
Released since project start: v1.7.0 → v1.17.4. Recent landings: container groups, maintenance mode, group/topic auth fix, BOT_LABEL, healthcheck improvements,
/changelogcommand. See CHANGELOG.md for the full list.Open v1.x topics being tracked individually:
v2.0 — the bigger release
Two large items planned to land together rather than be trickled out — they need a real release window, not a weekend hack.
v2.0 will start when there's enough user feedback and momentum to justify the architectural refactor. If those features matter to you, ⭐ the repo or mention Docksentry to someone who'd benefit — that's the signal I'm watching.
How to participate
buglabel, reproduction steps, Docksentry version, container runtime info.enhancement— describe the use case before suggesting a specific implementation.This issue gets edited as state changes — comments welcome but the top description is the canonical status.