Release Notes
In one sentence
Release Notes was planned as an app that turns the changes between two points of a repository into end-user release notes; in the code I reviewed it is retired and not available as a hosted app.
What makes it unique
Nothing is live to compare against today, so this chapter is a status note rather than a how-to. The idea was a notes writer for end users: features, bug fixes and performance, without class names or file paths.
When to use it / when not to
- Do not look for it on the hosted pages: its page, controller, worker and task were removed from the codebase in the latest cleanup, and its slot in the plugin list is marked "Retired".
- Use these instead:
- Repo Docs for documentation generated from a repository.
- Code Graph for a structural map of the code at one commit (the file name carries the commit, so runs on two commits can be compared by you).
- Assembly Chat, Diff command, for "what changed in this package's public API between version A and B", with a report and diagrams.
Before you start
Nothing to prepare. If you saw a Release Notes page in a screenshot or an old link, it was an interface for repository, branch and range choices (since the last release, between two tags or commits, or unreleased changes) and an audience choice; it is no longer in the product tree (verify on the live app whether any such page is still online).
Step by step
- Do not rely on a hosted Release Notes page.
- For API changes of a .NET package, use Assembly Chat with the Diff command.
- For documentation of the current state of a repository, use Repo Docs.
Options explained
| Option | What it does | Default | Recommended |
|---|---|---|---|
| (none) | The app is retired | – | See the alternatives above |
What you get
Nothing from this app. A related internal tool exists in the company's scheduler for generating release notes from impact analysis, but it is not exposed as a page for readers of this book (verify before promising it to anyone).
Quality & limits
Not applicable. Any text you see claiming Release Notes support on the site should be treated as out of date until verified.
Works well with
- Use instead: Assembly Chat (Diff), Repo Docs.
- Recipes: none.
Common mistakes & fixes
- Looking for a Release Notes button on the AI home page → it is not offered.
- Expecting end-user notes from Repo Docs → Repo Docs writes technical documentation, not release notes.
Same thing elsewhere
Not verified. See channels.
Try it
Compare two versions of a NuGet package you use with Assembly Chat (Diff) and rewrite its report as three plain-language bullets for your users. That is the closest hosted equivalent today.