Comparable List keeps a public changelog so you can see real progress on the tool without guessing what's live.
This is a product record, not a marketing promise. We publish a release here when a visitor can use it on the public site. Planned work is kept separate so a feature is never presented as available before it is ready. For a small browser-based tool, that distinction matters: a change to parsing, sharing, or privacy can affect the result a person sees, even when the interface looks familiar.
Each release note explains the practical behaviour rather than just naming a feature. If we fix an edge case, we will say what input was affected and what a user should expect now. If we change a privacy-related behaviour, we will link to the relevant policy update. This gives returning users a clear place to check what changed before they rely on the tool for a repeated workflow.
The initial release focuses on a dependable line-based comparison. You can paste values, upload a supported text file, adjust common formatting rules, and inspect each result group without creating an account. The comparison runs in the browser. That means a list does not need to make a round trip to a server just to calculate the overlap, and closing or refreshing the page clears the in-page working state unless you deliberately use a share link.
A share link is designed for a user who chooses to send a comparison to someone else. Because the input is represented in the link itself, anyone who receives the full URL may be able to read that comparison. Do not use share links for confidential material, and remove sensitive values before sharing a link in a ticket, message, or public document. This limitation is intentional and documented so that convenience does not create a misleading privacy expectation.
We also consider accessibility and device support part of a release. The tool is usable with keyboard navigation, preserves readable result groups on smaller screens, and does not require a download. When we add new formats, we will test them against the same basics: clear labels, visible results, no account requirement, and a description of how the data is handled.
If a result looks wrong, include a small, non-sensitive example of the two inputs, the settings you selected, the browser you used, and the result you expected. Please remove email addresses, customer information, tokens, and other confidential data before sending an example. A minimal example helps us reproduce a parsing issue without asking you to disclose a complete working list. We will describe confirmed fixes in a future release note when the change affects normal use.
Each workflow is live only after it is public and tested. The guides explain the practical checks that make the current tools more reliable.