-
Notifications
You must be signed in to change notification settings - Fork 6
Add April 13 changelog: guided onboarding and automatic setup #105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mintlify
wants to merge
1
commit into
production
Choose a base branch
from
mintlify/changelog-april-week2-1776039010
base: production
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+115
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,101 @@ | ||
| --- | ||
| title: "Changelog" | ||
| description: "New features, updates, and fixes." | ||
| --- | ||
|
|
||
| <Update label="April 13, 2026" description="Guided onboarding and automatic workspace setup" tags={["Feature", "Update", "Fix"]}> | ||
|
|
||
| ## New features | ||
|
|
||
| ### Guided onboarding experience | ||
|
|
||
| New workspaces now get a step-by-step onboarding flow. After installing the GitHub App, you'll see a real-time sync progress bar as Sweetr pulls in your repositories, pull requests, and code reviews. While data syncs, a getting-started checklist guides you through setting up teams and configuring DORA metrics. | ||
|
|
||
| [Onboarding guide](/get-started/onboarding) | ||
|
|
||
| ## Updates | ||
|
|
||
| ### Automatic application and incident detection setup | ||
|
|
||
| Sweetr now automatically creates an [application](/platform/applications) for each of your repositories during the initial sync, with merge-based deployment tracking pre-configured. [Incident detection](/automations/incident-detection) is also initialized out of the box — so you get DORA metrics from day one without any manual setup. | ||
|
|
||
| ## Bug fixes | ||
|
|
||
| - **Code review sync** — Fixed an issue where reviews without a submission timestamp could interrupt the sync process. | ||
|
|
||
| </Update> | ||
|
|
||
| <Update label="April 6, 2026" description="Sandbox mode, new login page, and macOS Docker support" tags={["Feature", "Fix"]}> | ||
|
|
||
| ## New features | ||
|
|
||
| ### Sandbox mode | ||
|
|
||
| You can now explore Sweetr without signing up. The new sandbox mode lets you browse the full interface with realistic mock data — metrics, pull requests, DORA charts, and more. Just visit the login page and click "Explore the sandbox instead." | ||
|
|
||
| ### Revamped login page | ||
|
|
||
| The login page has been redesigned with a cleaner layout and a quick overview of DORA elite benchmarks, so you know what you're working toward before you even sign in. | ||
|
|
||
| ## Bug fixes | ||
|
|
||
| - **Self-hosted Docker on macOS** — Docker images now support ARM64 architecture, fixing compatibility issues for self-hosted users running on Apple Silicon (M1/M2/M3/M4) machines. | ||
|
|
||
| </Update> | ||
|
|
||
| <Update label="March 2026" description="Self-hosting, incident detection, and more" tags={["Feature", "Update", "Fix"]}> | ||
|
|
||
| ## New features | ||
|
|
||
| ### Self-hosting support | ||
|
|
||
| You can now self-host Sweetr on your own infrastructure with a single command. The deploy script walks you through the full setup — from creating a GitHub App to generating your Docker Compose stack. | ||
|
|
||
| ```bash | ||
| curl -fsSL https://raw.githubusercontent.com/sweetr-dev/sweetr.dev/main/bin/deploy | bash | ||
| ``` | ||
|
|
||
| [Self-hosting guide](/get-started/self-host) | ||
|
|
||
| ### Incident detection automation | ||
|
|
||
| Sweetr now automatically detects incidents from your deployments. Three detection strategies are available out of the box: | ||
|
|
||
| - **Rollbacks** — detects when a deployment reverts to a previously deployed version. | ||
| - **Reverts** — detects GitHub revert PRs. | ||
| - **Hotfixes** — matches configurable patterns in PR titles, branch names, or labels. | ||
|
|
||
| Incident Detection is enabled by default for every workspace. Detected incidents feed directly into your [DORA metrics](/metrics-and-insights/dora) for more accurate change failure rate and mean time to recover. | ||
|
|
||
| [Incident detection docs](/automations/incident-detection) | ||
|
|
||
| ### People bio and location | ||
|
|
||
| Profile pages now show each person's bio and location, synced from GitHub. This makes it easier to get context on teammates across your organization. | ||
|
|
||
| [People directory](/platform/people) | ||
|
|
||
| ### DORA metrics in Slack digests | ||
|
|
||
| Your team's [Slack digest](/automations/digests) now includes all four DORA metrics — deployment frequency, lead time, change failure rate, and mean time to recover. If deployments aren't set up yet, the digest links directly to the setup guide. | ||
|
|
||
| ## Updates | ||
|
|
||
| ### Deployment setup guidance | ||
|
|
||
| Pages that depend on deployment data — like DORA metrics, incidents, and team alerts — now show a setup banner when deployments haven't been configured yet. The banner links you straight to the [deployment setup guide](/platform/deployments#setting-up-deployments-for-dora-metrics). | ||
|
|
||
| ### API rate limiting | ||
|
|
||
| The REST API now enforces a rate limit of 100 requests per minute per API key to ensure fair usage across all workspaces. | ||
|
|
||
| [API rate limit docs](/api-reference/rate-limit) | ||
|
|
||
| ## Bug fixes | ||
|
|
||
| - **PR timeline** — Fixed personal metrics date range calculations and resolved an issue where cycle time of zero was incorrectly hidden. | ||
| - **DORA team filtering** — Team filtering on DORA metrics now correctly uses deployment author team membership instead of application ownership. | ||
| - **First review calculation** — Fixed a bug where the first review timestamp used aggregated data instead of chronological review events. | ||
| - **Code review sync** — Resolved an issue where code reviews could fail to sync under certain conditions. | ||
|
|
||
| </Update> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Changelog tab uses
"group": "", which could produce an empty/blank section header in the Mintlify sidebar. Every other tab uses a descriptive group name. Since there's only one page here, you can either use a meaningful label or check whether Mintlify suppresses empty group titles entirely.