Version 0.7.1 - Release Notes

Version 0.7.1 adds the new CubeForge community roadmap.

This is a smaller release than 0.7.0, but it should make a meaningful difference to how CubeForge is developed from here. I want the project to be easier to follow, easier to influence, and easier to give feedback on without everything needing to happen through scattered messages.

The new roadmap is meant to become the central place for feature requests, bug reports, and visible development progress.

🗺️ The community roadmap is now live

CubeForge now has a public community roadmap.

The roadmap gives everyone a clearer view of what is open, planned, in progress, completed, or declined. Instead of feature ideas living only in Discord conversations, private notes, or one-off messages, they can now be collected in one place and discussed over time.

This should make development more open. You can see which ideas are already being considered, follow changes as they move through the roadmap, and avoid wondering whether a suggestion has disappeared into a void.

👍 Vote on what matters most

The roadmap also adds voting for open and planned items.

This is important because CubeForge has a lot of possible directions: drafting improvements, cube management tools, better sharing, card workflows, analytics, export options, and more. Not every idea can be built at once, so votes give me a better signal for what users actually care about most.

Votes will not be the only thing that decides priority. Some work is foundational, some bugs are urgent, and some features depend on other pieces landing first. But having a public priority signal should make those decisions better and more transparent.

🐛 Bug reporting is simpler now

Bug reports now go through the roadmap as well.

You can create a bug report directly from the roadmap page, add a short description, categorize it, and keep the discussion attached to that item. This should be easier than using a separate report form and better for issues that need follow-up questions or status updates.

It also means bugs can move through the same visible statuses as feature requests, so it should be clearer when something is acknowledged, in progress, fixed, or closed.

💬 Better discussion around ideas

Roadmap items have their own detail pages with comments.

That gives each feature request or bug report a dedicated place for extra context: examples, edge cases, reproduction steps, or design tradeoffs. For larger ideas, this should make it easier to build the right version of the feature instead of just the first version that comes to mind.

There are also moderation tools for keeping the roadmap useful as it grows, including item status management, pinned items, locked discussions, reports, edits, and deletes.

🔍 A clearer way to follow progress

The roadmap can be filtered by feature requests or bug reports, searched, and sorted by trending activity, votes, newest items, or recently updated items.

There is also a summary of open, planned, in-progress, and completed work. Over time, this should make it easier to see both what is coming next and what has already shipped because of community feedback.

You can check it out here: CubeForge Roadmap.

If you notice anything off, please create a bug report here: Report a bug. You can also ask me directly in the CubeForge Discord.