Changelog
Browse the public Devpilot changelog to see new features, fixes, and improvements released in each version.
Changelog
The Devpilot Changelog is the authoritative record of what shipped, when, and in which category. It is a public page you can read without signing in, so anyone on your team — or a customer watching your deployments — can stay aligned with new capabilities, deprecations, and bug fixes.
Opening the changelog
Go to the public page
Visit /changelog in your browser. No Devpilot account is required. The page lists every published entry, newest first.
Scan the latest release
The entry at the very top is the most recent Devpilot release. Each entry shows its title, category badge, author, and publish date so you can see at a glance what changed.
Drill into the details
Click an entry to expand its full Markdown body, which usually explains the change, how to use it, and any action you need to take.
Bookmark /changelog or pin it in team chat so everyone has a direct link to the most recent Devpilot releases.
What each entry contains
Every changelog entry on the page exposes the following details:
| Field | What it means |
|---|---|
| Title | A short summary of the change, for example "Zero-downtime deploys for Laravel apps". |
| Content | The full body of the note, written in Markdown. It usually includes context, how to use the new behaviour, and any migration steps. |
| Category | The kind of change — see the next section for the default set. |
| Author | The Devpilot team member who published the entry. |
| Published date | The timestamp when the entry became visible. |
Only entries with a status of published and a published date in the past are shown. Drafts and scheduled-future entries stay hidden until their publish time arrives.
Categories
Each entry can be tagged with a category so you can skim the list by the type of change you care about. A category has:
- A name you see in the UI (for example "Feature", "Bug fix", "Improvement").
- A slug used to filter the feed.
- A colour used as the visual badge on the entry.
Typical categories include:
- Feature — a brand-new capability.
- Improvement — an enhancement to an existing capability.
- Bug fix — a defect resolved in this release.
- Security — a security-related change you may need to be aware of.
- Breaking change — something that requires action on your side.
The exact set of categories is maintained by the Devpilot team, so you may see additions or refinements over time. Reach out via the Contact page if you have feedback on how releases are categorised.
Filtering by category
You can scope the feed to a single category by clicking a category chip at the top of the Changelog page. The URL updates with a category filter, so you can share a link to a filtered view (for example, only Security releases) with teammates.
Searching
A search field on the page matches against both the title and the content of each entry. Use it to find a specific release when you remember a keyword but not the date.
Latest-release indicator
The entry at the top of the list is the latest published release. Because the feed is ordered by publish date descending, it always reflects the most recent Devpilot version deployed to the platform. Use it as a quick way to confirm you are on a release that includes the fix or feature you are expecting.
Devpilot ships updates continuously. If you do not see a recent entry that you were expecting, check the Status page for ongoing rollouts or use Contact to ask the team directly.
Pagination
The feed returns entries in pages of 15. Use the pagination controls at the bottom of the Changelog page to walk back through older releases. Scrolling through history is a handy way to audit what changed after you last used a feature or to prepare release notes for your own users that depend on Devpilot.
How to use the changelog effectively
- Read every Breaking change entry before upgrading your project's Devpilot configuration.
- Filter by Feature after a long break to catch up on what is new.
- Share a deep link to a specific release in code review if it changes how a team member should ship.
- Cross-reference an entry with the Status page to confirm a release rolled out cleanly.
- Keep tabs on the Security category so you can roll out coordinated changes on your side.
- Use Bug fix entries to close out known issues in your internal tracker.
- Skim the Feature category before customer reviews to show off what Devpilot delivered recently.
- Use the page as evidence for your own release cadence and platform investment story.