> ## Documentation Index
> Fetch the complete documentation index at: https://docs.navigara.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> New features, improvements, and important changes to Navigara, newest first.

New features, improvements, and important changes to Navigara. Newest first.

<Update label="v0.13.2" description="July 20, 2026" tags={["patch"]}>
  ### Highlights

  #### Bitbucket Cloud connections

  Adding a Bitbucket Cloud connection with an API token now validates and syncs pull requests, including for workspace-scoped tokens.

  #### Consistent status colors everywhere

  Objective status, roles, and other status indicators use the same colors and badge style across every page. A status looks the same wherever you see it.

  #### Also in this release

  * Percentages and change values across the app display with consistent formatting.
  * Currency and large-number values display with consistent formatting throughout the app.
  * Terminology across the app is more consistent, covering developer, organization, issue, email, and AI spend labeling.

  ### Fixes

  * Mark retry and dismiss actions now include more detail in their audit history.
</Update>

<Update label="v0.13.1" description="July 17, 2026" tags={["patch"]}>
  ### Highlights

  #### Live AI efficiency in quarterly reports

  The AI efficiency card in the quarterly report now shows a live figure for spend per unit of output. It clearly shows when there is no AI usage yet, when usage exists but has no cost attached, and when spend exists but no output was delivered.

  #### Redesigned executive summary

  The dashboard executive summary card has a refreshed look. It includes a clearer loading state, a draft label for briefings covering a period still in progress, and a one-click way to generate a briefing on demand.

  #### Consistent filters and toolbars

  Filters and search on the Repositories, Developers, and Teams pages, and the global top bar, now follow one consistent style and layout. This makes them easier to find and use.

  #### Also in this release

  * In-app setup is now available to everyone, guiding new organizations through connecting their tools.
  * The "How is performance evolving" dashboard card was redesigned with clickable views.
  * Navigara now measures tool calls per message to give a clearer picture of AI tool usage.
  * The Aliases table in Settings now keeps its row actions visible within the page.
  * We strengthened the security of account sign-in.

  ### Important changes

  | What changed                                                                                                                  | What you will notice                                                                                         | What you can do                                                                                  |
  | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
  | The quarterly report's team activity, average headcount, and role breakdown now use a more precise, week-by-week calculation. | These figures for past quarters can shift slightly. "All Developers" now always shows a full role breakdown. | Compare quarters inside the app. All quarters use the same calculation.                          |
  | The Add Repository dialog no longer offers a manual URL entry option.                                                         | You can add repositories only from the Discovered list. This keeps them linked to a connected integration.   | Use the Discovered tab to add repositories. Connect a provider first if none are discovered yet. |

  ### Fixes

  * Analysis of code changes now keeps paired test information intact when a repository is re-analyzed.
</Update>

<Update label="v0.13.0" description="July 16, 2026" tags={["minor"]}>
  This release makes it easier to get started with Navigara on your own and to understand your delivery at a glance. New executive briefings and on-demand reports bring your objectives, work, and costs together in one place.

  ### Highlights

  #### Self-serve signup and free trials

  New organizations can now sign up and start using Navigara on their own, without waiting for manual activation. The setup flow guides you through connecting your code and task management. Each step advances automatically as it completes. If your plan includes a free trial, an in-app banner shows how many days remain, and a reminder email arrives before the trial ends.

  #### Executive briefings and on-demand reports

  The dashboard now opens with an executive briefing. It leads with your objectives, then shows aligned and untracked work, costs, and notable team activity. Each repository, developer, and team has a redesigned Reports section in the same briefing style, with a period navigator to browse every completed period. You can generate any report on demand with a single click. Briefings also refresh automatically after you connect a task management tool, so new objectives appear right away.

  #### Also in this release

  * A new usage view shows your plan and how much of your commit-analysis limit you have used, with a trial countdown and a page that lists exactly which developers count toward billing.
  * The Checks page now uses one consistent layout and links each finding to its source commit, pull request, or issue.
  * Chart legends are now interactive: select an item to show or hide that series.
  * Developer aliases let you group several email addresses under one developer profile.

  ### Important changes

  | What changed                                              | What you will notice                                                                                        | What you can do                                                                       |
  | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
  | Trial and paid plans now include a commit-analysis limit. | When your organization reaches its limit, new commit analysis pauses. The rest of Navigara stays available. | Upgrade your plan to raise the limit. Your existing data and dashboards stay visible. |

  ### Fixes

  * The Add Repository dialog now closes automatically after you add repositories, and lists newly discovered repositories as they are found.
  * Developer detail pages now list only repositories with activity.
  * Objective charts now include periods that have no activity.
  * You can now connect Asana and load your workspaces during setup.
</Update>

<Update label="v0.12.5" description="July 13, 2026" tags={["patch"]}>
  ### Highlights

  #### Redesigned AI spend insights

  The AI spend view now matches weekly cost against weekly performance across developers, teams, tools, and models. You can see cost and value side by side. Developers get a dedicated detail view. Rows are fully clickable, and tools share a consistent legend across charts.

  #### Light theme for sign-in and onboarding

  Sign-in and onboarding now use a clean light theme that matches the rest of the app. Text is clearer, buttons are consistent, and contrast is improved.

  #### Switch between quarters in the quarterly report

  The quarterly report now includes a quarter selector. You can review recent quarters instead of only the latest one. Every section, including baselines, weekly charts, teams, and objectives, updates to match your selection.

  #### Also in this release

  * The Key metrics board on the dashboard has a refreshed layout, with progress-colored trend bars and clearer period totals.
  * AI spend records now include a cache-aware cost estimate for supported AI coding tools, for a more complete spend picture.

  ### Important changes

  | What changed                                                                                                                                                                               | What you will notice                                                                                                            | What you can do                                                            |
  | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
  | Pull request cycle time, throughput, review coverage, and quality headlines on reports now use the full period instead of averaging weekly values.                                         | Some headline figures may shift slightly compared to earlier periods. Missing periods show as unavailable instead of showing 0. | Compare periods inside the app. All periods now use the same calculation.  |
  | The Key metrics board now calculates alignment share, AI-assisted share, and cost-per-performance as true totals across the selected window, rather than an average of weekly percentages. | Some percentages, including AI-assisted share, may read differently, especially for windows with uneven weekly activity.        | Use the in-app window figures going forward. They reflect the full period. |
  | Objective lists and quarterly reports now return every objective for organizations with more than 50, instead of stopping at 50.                                                           | Organizations with more than 50 objectives will see additional objectives in lists, reports, and alignment figures.             | No action needed. The fuller list appears automatically.                   |

  ### Fixes

  * You can now edit the host path and token name on an existing token-based connection, instead of only rotating the token.
  * Charts now render every value on the vertical axis, so no tick is skipped.
  * The processing status dashboard now refreshes automatically after you retry or dismiss an item.
  * We strengthened the security of the platform.
</Update>

<Update label="v0.12.4" description="July 3, 2026" tags={["patch"]}>
  ### Highlights

  #### Refreshed dashboard

  The dashboard now opens on the last 12 months by default. Team rows show alignment and AI spend alongside performance. Objectives render as shaded area charts, and the top 20% share callout shows what percentage of total performance it represents.

  #### Asana task linking by ID

  Navigara now recognizes Asana's human-readable task IDs (for example `IDP-4355`) in commit messages. Commits and Asana tasks line up automatically, not just from the underlying task link.

  #### Safer connection setup

  The connections page only shows sign-in options that are fully set up on your account. You always land on a working setup step.

  #### Also in this release

  * List pages across the app now share a consistent panel layout and color palette.

  ### Important changes

  | What changed                                                                                                                                               | What you will notice                                                                                                             | What you can do                                                                   |
  | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
  | Performance totals and averages on developer, team, and repository pages now use one consistent calculation everywhere.                                    | Some totals and benchmark lines may shift slightly, and now always agree with the same number shown in lists and charts.         | Compare periods and entities freely — the same calculation is used on every page. |
  | A team's total performance now includes people who contributed to the team's work during the period, even if they have since moved to another team.        | Team totals now match the sum of the rows shown below them. Former developers appear with a "Former" label.                      | No action needed.                                                                 |
  | AI detection now also recognizes commits authored directly by an AI coding agent, not only commits with an AI co-author, using an updated detection model. | Some commits from AI coding agents may now be marked as AI-assisted. Existing commits update the next time they are re-analyzed. | No action needed.                                                                 |

  ### Fixes

  * Jira: objective and sub-objective changes now update the alignment status of all related commits, including ones several levels down.
  * Jira: on-premises Jira connections now keep separate identities, so two on-premises instances are never mixed together.
  * Reported AI tool usage and spend from on-premises analysis is now calculated consistently over time.
</Update>

<Update label="v0.12.3" description="June 30, 2026" tags={["patch"]}>
  ### Highlights

  #### Connect Asana and Linear

  Navigara now connects directly to Asana and Linear with a one-click sign-in flow. For Asana, you can choose which workspace or workspaces to sync, so multi-workspace teams get exactly the projects and tasks they need.

  #### Flexible email delivery

  Organizations running Navigara on their own infrastructure can now send password reset, invitation, and welcome emails through any standard email provider, using a simple configuration.

  #### Also in this release

  * Cloud infrastructure monitoring alerts help the Navigara team keep the platform reliable.

  ### Important changes

  | What changed                                                                                                         | What you will notice                                                                           | What you can do                                                                |
  | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
  | AI-detection now uses a more conservative threshold, favoring precision over recall.                                 | Fewer commits are flagged as AI-assisted; flagged commits are held to a higher confidence bar. | No action needed. Detection continues to improve in future releases.           |
  | Commit scoring now credits developer effort more accurately for new files, new functions, and cross-file code reuse. | Work-type scores for some commits may shift slightly compared to earlier periods.              | Compare periods inside the app — all periods use the same updated calculation. |

  ### Fixes

  * Organization owners, admins, members, and viewers can now access the Connections page from Settings.
</Update>

<Update label="v0.12.2" description="June 25, 2026" tags={["patch"]}>
  ### Highlights

  #### Refreshed visual design

  Navigara has a new look across the app, including dashboards, settings, and sign-in. Buttons, cards, menus, and other controls use a refined color palette, softer shadows, and tighter spacing in both light and dark mode.

  ### Important changes

  | What changed                                                                                                                                    | What you will notice                                                                                                                | What you can do                                                                                             |
  | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
  | The objective alignment KPI on the dashboard summary uses the same alignment calculation as the detailed alignment charts elsewhere in the app. | The objective alignment percentage on the dashboard may shift, and now shows as two lines (key aligned and aligned) instead of one. | Compare periods and views inside the app. The dashboard summary and detail charts use the same calculation. |

  ### Fixes

  * Objective alignment figures on the dashboard summary stay consistent with the alignment charts shown elsewhere in the app.
</Update>

<Update label="v0.12.1" description="June 25, 2026" tags={["patch"]}>
  Navigara v0.12.1 refreshes the dashboard and team views, and improves chart accuracy across performance pages.

  ### Highlights

  #### Dashboard summary and teams

  The dashboard summary now shows performance, objective alignment, and AI augmentation as trend lines. Each trend line has a trend chip comparing the start and end of the period. The Developers section is now a Teams section. It shows your top and bottom teams by performance, with a link to each team's page.

  #### Performance chart views for teams and developers

  Team and developer pages now have clickable summary cards. Use them to switch the chart between alignment mix, work mix, average member performance, and AI augmentation. AI spend now shows as spend per unit of value delivered, with total spend shown alongside it.

  #### Team hierarchy

  Sub-teams and parent teams are back on team pages. A breadcrumb shows each team's place in the hierarchy. A picker lets you assign sub-teams when creating or editing a team.

  #### Also in this release

  * The Developers list filters are simpler: search by name or email, filter by team, or by probation status.
  * Developer detail pages now show the same clickable performance charts available on team pages.

  ### Fixes

  * The team edit page now opens.
  * The "Top 20% Sum" trend line on the dashboard timeline chart now renders alongside its legend and summary value.
  * Chart Y-axes on developer and team pages now scale closer to the actual data, removing excess empty space above the highest value.
  * Table row hover is now visible in light mode.
</Update>

<Update label="v0.12.0" description="June 22, 2026" tags={["minor"]}>
  ### Highlights

  #### Find and re-enable disabled repositories

  Repositories you disabled from analysis previously disappeared with no way to bring them back. A new Disabled tab next to your repository list shows every disabled repository and lets you re-enable it with one click.

  #### A guided setup wizard for task tracking connections

  Connecting Jira, Linear, or another task tracker now walks you through picking which projects to sync. It also shows how issue types map to objectives, sub-objectives, and issues. The same wizard supports every provider. Reopening it later shows your saved settings instead of resetting them.

  #### Multiple connections per AI tool

  You can add more than one connection for the same AI assistant. For example, you can set up separate connections for different backends or departments. Each connection gets its own setup view and can be removed independently.

  #### Also in this release

  * Team and developer pages now show extra performance and alignment detail cards.
  * The commits page highlights pull-request metrics, including merged count, average cycle time, and review coverage, and makes AI-assisted commits easier to spot.
  * The AI spend page is reorganized around cost, with a per-developer breakdown, pagination for large teams, and a drill-down view for individual developers.
  * The settings page now shows when each API token was last used.
  * Reports has graduated from beta and is now generally available.
  * The toolbar shows a live indicator while your organization's data is being processed.
  * You can compare a period against its previous period directly in custom metric queries, and build custom calculated measures from existing ones.

  ### Important changes

  | What changed                                                                                                          | What you will notice                                                                                                        | What you can do                                                               |
  | --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
  | Commit scoring recognizes renamed files by their prior history and excludes generated and minified code from scoring. | Performance scores for past and future periods can shift, especially for repositories with renamed files or generated code. | Compare periods inside the app. All periods use the same updated calculation. |
  | Large commits are now fully analyzed.                                                                                 | More commits contribute to performance metrics, which can change historical totals for repositories with large commits.     | No action needed. Metrics automatically reflect the fuller analysis.          |

  ### Fixes

  * Navigara now shows a maintenance page instead of signing you out when it briefly cannot reach the server.
  * Developer reports now support the quarterly view.
  * The commits page keeps your repository filter selected when you also filter by developer.
  * The developers page keeps your filters and page position when you change the time range.
  * Switching organizations now loads all your organizations the first time you select "Show more".
  * Strengthened the security of the password change flow.
</Update>

<Update label="v0.11.8" description="June 2, 2026" tags={["patch"]}>
  ### Fixes

  * Pull request metrics in reports now stay up to date and scoped correctly after team or hierarchy changes.
</Update>

<Update label="v0.11.7" description="June 1, 2026" tags={["patch"]}>
  ### Highlights

  #### More accurate average-per-developer metric

  The average-per-developer figure now sums each week's average within a period. Larger periods, like a month or quarter, stay proportional to their weeks. A developer who joins partway through a longer period no longer skews the average for everyone else.

  #### Consistent numbers across dashboard and reports

  The dashboard summary and KPI cards now use the same average-per-developer calculation as quarterly reports. The numbers match everywhere you see them.

  ### Important changes

  | What changed                                                                                                                                                             | What you will notice                                                                                                                                                                     | What you can do                                                                   |
  | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
  | The average-per-developer calculation now sums weekly averages instead of using a single period-wide rate. The dashboard uses the same calculation as quarterly reports. | Average-per-developer figures for months and quarters may shift slightly from previous values. Dashboard figures may also differ slightly from before, while matching quarterly reports. | No action needed. All periods and pages now use the same, consistent calculation. |

  ### Fixes

  * The quarterly report now loads when no team roles are configured, showing a clear message instead of staying on a loading state.
</Update>

<Update label="v0.11.5" description="June 1, 2026" tags={["patch"]}>
  ### Highlights

  #### AI tool usage and spend, per developer

  Navigara now ingests usage telemetry from AI coding tools. It attributes tokens and spend to the developer who generated them. You can track AI adoption and cost person by person, not just organization-wide.

  #### Refreshed dashboard overview

  The dashboard overview now shows Performance, AI Augmented, and Alignment side by side. It runs on an updated metrics engine for faster, more consistent numbers.

  #### Also in this release

  * The Repositories page replaces automatic polling with a manual Refresh button, so you control when the list updates.
  * Adding a developer to a new team now warns you first if they already belong to another team, since the move ends their current membership.
  * Directory sync (SCIM) now supports value-path filtering for Microsoft Entra ID provisioning.
  * Metric-backed list views support entity search filters and pagination for faster browsing on large organizations.

  ### Important changes

  | What changed                                                                                               | What you will notice                                          | What you can do                                                                    |
  | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
  | Total commit counts for repositories now use the verified count from analysis instead of an approximation. | Commit totals shown for some repositories may shift slightly. | No action needed — the new totals are more accurate and consistent across the app. |

  ### Fixes

  * Editing a repository that was previously stopped now resumes its analysis automatically.
  * Developer lists and filters now show the correct team for each developer.
  * Team membership lists no longer show duplicate or outdated entries for developers who changed teams.
</Update>

<Update label="v0.11.4" description="May 26, 2026" tags={["patch"]}>
  ### Fixes

  * Team pages now open when the team name includes spaces or accented characters.
  * Team membership history no longer shows duplicate entries when someone rejoins the same team on the same day.
  * Signing up now returns a clear "already registered" message when the email address is already in use, even when multiple sign-up attempts happen at the same time.
</Update>

<Update label="v0.11.3" description="May 25, 2026" tags={["patch"]}>
  Navigara v0.11.3 brings a redesigned time picker, a full membership history for teams, and richer executive summary gauges on reports and dashboards.

  ### Highlights

  #### Redesigned time picker

  The date range picker now uses simple period chips (day, week, month, quarter, year) with quick presets like "Last 12 weeks" or "Last 8 quarters". A new "complete periods only" toggle lets you exclude the current, still-in-progress period from your view so you are always comparing full periods. The default view is now the last 12 complete weeks.

  #### Team membership history

  Team detail pages now include a membership history panel showing every developer who has ever been on the team, past and current. Filter by name or email, and open a developer's role directly from the list.

  #### Executive summary gauges

  Reports and dashboards now show Performance, Objective alignment, and AI efficiency as clear gauge cards, each with a year-over-year trend indicator. Reports also gained an outcomes section highlighting the quarter's top objectives with supporting evidence, and a quality and governance summary covering pull request throughput, review coverage, and cycle time.

  #### Also in this release

  * You can now pause analysis for an individual repository from its settings, without removing the repository.
  * We strengthened the security of the platform.

  ### Important changes

  | What changed                                                                                  | What you will notice                                                      | What you can do                                                                         |
  | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
  | Team membership shown in past period summaries now reflects who was on the team at that time. | Historical summaries for teams may show different developers than before. | Compare periods inside the app. All periods now use the same, time-accurate membership. |

  ### Fixes

  * Connecting a tracker or issue integration now shows a clear message when a connection is temporarily rate limited.
  * Adding or editing a team member now shows a clear error message if the request cannot be completed.
  * Searching for a developer to link now returns results faster.
</Update>

<Update label="v0.11.2" description="May 19, 2026" tags={["patch"]}>
  ### Highlights

  #### Bulk add team members

  You can now add several developers to a team in one step. Search and multi-select developers, or paste a list of email addresses. Preview each person's current team assignment. Set a shared start date, with a per-row override when needed.

  #### Also in this release

  * Team pages stay in sync everywhere. Changes made from the Developers page are immediately reflected on the Teams page.
  * API key errors are now shown clearly on the Tokens page, with a retry option.

  ### Important changes

  | What changed                                                                                                                                                                                                                                                                                                         | What you will notice                                                                             | What you can do                                                               |
  | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
  | Refined the calculation that measures how much a code change alters a developer's work, used in performance scoring. Mechanical, repetitive edits, like adding the same annotation across many files, are recognized more accurately. Simple variable renames are distinguished from more substantial logic changes. | Historical and new performance scores may shift slightly for commits affected by these patterns. | Compare periods inside the app. All periods use the same updated calculation. |

  ### Fixes

  * Improved the reliability of analysis processing for organizations with a large volume of pending work, so results keep flowing smoothly.
  * Improved reliability of the reporting connection setup flow with clearer error messages.
</Update>

<Update label="v0.11.1" description="May 15, 2026" tags={["patch"]}>
  ### Highlights

  #### Clearer issue tracker sync status

  The connected issue tracker card now shows "Last synced" as a relative time, with the exact time available on hover. A new **Force sync** button lets you trigger an immediate refresh instead of waiting for the next scheduled sync.

  ### Fixes

  * The **Add repository** button on the Repositories page now appears reliably on every page load.
</Update>

<Update label="v0.11.0" description="May 13, 2026" tags={["minor"]}>
  Navigara v0.11.0 makes team history and organization identity easier to manage, adds fast global search, and improves several existing surfaces.

  ### Highlights

  #### Team membership history

  Team pages now show a full history of which team each developer belonged to and when. You can add, edit, or delete historical or active membership periods. Changing a developer's team now asks for the transition date instead of assuming today.

  #### Global command search

  Press Cmd/Ctrl+K anywhere to search objectives, teams, developers, repositories, and commits. You can also jump straight to a page.

  #### Also in this release

  * Organizations can rename themselves from general settings.
  * CapEx datapack exports include richer issue metadata and links.
  * Organizations can set a default analysis start date, used when a repository does not specify one.
  * Repository connection setup includes clearer local setup guidance for Rancher Desktop users.

  ### Important changes

  | What changed                                                                                            | What you will notice                                                | What you can do                                        |
  | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------ |
  | The Architecture feature (architecture analysis and feature catalog) has been removed from the product. | The Architecture page and related settings are no longer available. | No action needed; other analysis views are unaffected. |

  ### Fixes

  * The file changes table respects your selected metrics view consistently.
  * The commits page keeps the correct total count while paging through results.
  * Search fields handle special characters correctly when filtering results.
  * API key names are validated for length to prevent overly long values.
  * Directory sync (SCIM) is more reliable when mapping and syncing user attributes. Revoking a sync token can be repeated safely.
</Update>

<Update label="v0.10.20" description="May 5, 2026" tags={["patch"]}>
  ### Highlights

  #### Team hierarchy

  Teams can now be organized into a tree, with parent teams and sub-teams. Create sub-teams when you create a team, or move a team under a new parent. The teams list shows the full structure with a clear indented view. Metrics for a parent team now include all of its sub-teams, so a leader can see their whole organization at a glance.

  #### CapEx report export

  The CapEx report now has an Export CSV button. It downloads one row per developer per month for the selected date range, with hours and CapEx percentage. The file opens directly in Excel or Google Sheets.

  #### SCIM connection management

  Organization admins can now create, list, and revoke SCIM tokens from Settings. This supports identity-provider provisioning.

  #### Also in this release

  * Error messages and page refresh behavior are clearer across Repositories, Teams, and Explore, so failed actions are easier to notice and retry.

  ### Important changes

  | What changed                                                      | What you will notice                                        | What you can do                                                    |
  | ----------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ |
  | AI-assisted commit detection uses an updated classification model | Commits may be classified differently as AI-assisted or not | No action needed; classifications continue to update automatically |

  ### Fixes

  * Historical summaries now load their status and totals reliably.
  * Repository and benchmark pages refresh automatically after you delete, stop, or reset an analysis, so the list reflects the latest state.
  * Accepting a team invitation now keeps an active organization selected.
  * Analysis results are preserved more reliably if processing is interrupted partway through.
</Update>

<Update label="v0.10.19" description="April 28, 2026" tags={["patch"]}>
  ### Fixes

  * Team management shows clear confirmation and error messages when you create a team, update a team, add members, or remove members.
</Update>

<Update label="v0.10.18" description="April 27, 2026" tags={["patch"]}>
  ### Highlights

  #### Team visibility on the developer page

  The developer detail page now shows a Team card. You can see which team a developer belongs to without switching pages. Organization owners and admins can assign a team directly from this card when one is not set yet.

  #### Also in this release

  * Sync status for Linear now distinguishes an organization that has never connected Linear from one that connected but has not synced yet.

  ### Important changes

  | What changed                                                                                                                 | What you will notice                                                                                                                                                                                                                      | What you can do                                                               |
  | ---------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
  | Engineering Throughput Value (performance scoring) no longer applies a fixed minimum impact value to every file in a commit. | Historical performance scores can shift, especially for small or trivial commits that previously clustered at the same low value. The overall distribution of scores is now smoother and more representative of actual contribution size. | Compare periods inside the app. All periods use the same updated calculation. |

  ### Fixes

  * Deleting a team now asks for confirmation before removing it, to help prevent accidental deletions.
  * Benchmark reports now show grouped and aggregated results.
</Update>

<Update label="v0.10.17" description="April 23, 2026" tags={["patch"]}>
  ### Highlights

  #### Repository connection health

  Navigara now detects when a repository connection loses access, for example because of expired credentials or an unreachable repository. Affected repositories show a clear status. You can retry the connection with one click to restore analysis.

  #### Also in this release

  * Team performance metrics automatically refresh when a developer joins or leaves a team.
  * Role filters on the Developers and Reports pages now include every matching developer, even for large teams.

  ### Important changes

  | What changed                                                                                                              | What you will notice                                                                  | What you can do                                                            |
  | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
  | Team metrics now reflect which team a developer belonged to at the time the work was done, instead of their current team. | Historical metrics on team pages may shift slightly for developers who changed teams. | No action needed. Team pages automatically show the corrected attribution. |

  ### Fixes

  * Objective pages now consistently show performance charts and breakdowns.
  * Performance reports show refreshed data with corrected work-classification percentages.
</Update>

<Update label="v0.10.15" description="April 21, 2026" tags={["patch"]}>
  ### Highlights

  #### Smoother sign-in and organization switching

  Signing in with email or a single sign-on provider now takes you straight to your dashboard with the right organization selected. Switching organizations is instant.

  #### New AI provider option

  Organizations can now connect Navigara to Claude and GPT models through Azure AI Foundry, in addition to the existing provider options.

  #### Also in this release

  * Access controls now limit repository tag changes, developer identity changes, and developer merges to organization admins.

  ### Fixes

  * Dashboards now display up-to-date data across all views.
  * Commit history analysis now respects each repository's configured start date. Large, long-running repositories analyze faster and stay within the intended time window.
  * Updating a Git access token now automatically refreshes repository discovery. Deleting a token now warns you when active repositories depend on it.
</Update>

<Update label="v0.10.14" description="April 20, 2026" tags={["patch"]}>
  ### Highlights

  #### Renamed performance unit to Engineering Throughput Value (ETV)

  The quarterly performance report now presents your score as Engineering Throughput Value (ETV). This aligns naming across the quarterly report and the performance whitepaper. The report also adds an Activity measure showing how actively engaged your team was each quarter, with clear color bands and a worked example.

  #### Refreshed and expanded performance whitepaper

  The cross-organization performance whitepaper now shows independent scales per organization. Smaller teams are no longer flattened by larger ones. The whitepaper also adds a cohort breakdown table and a full appendix listing every repository analyzed.

  #### Also in this release

  * Team, seniority, and role selections on the Developers page stay applied immediately after you make them.
  * Team member lists and additions are more reliable.
  * The dashboard summary (active developers, average performance, active repositories) loads faster.

  ### Fixes

  * We strengthened access controls around organization settings.
</Update>

<Update label="v0.10.13" description="April 16, 2026" tags={["patch"]}>
  ### Highlights

  #### Cleaner repository and team pages

  Repository and team detail pages now show cleaner, more relevant information. Outdated panels have been removed.

  #### Consistent developer counts

  Developer counts now match everywhere they appear on a repository page.

  ### Important changes

  | What changed                                                                          | What you will notice                                                                                                              | What you can do                                                   |
  | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
  | Weekly activity charts now align time buckets to your account's configured time zone. | For organizations outside UTC, some past weekly charts may show different values as data is grouped into the correct time window. | No action needed. Charts automatically reflect the new alignment. |

  ### Fixes

  * Commit history catches up automatically after an analysis run is interrupted, so no commits are left unprocessed.
  * Developer counts on repository pages are consistent across all views.
  * Team detail pages no longer show an unrelated repositories section.
  * Repository detail pages no longer show an outdated project information panel.
</Update>

<Update label="v0.10.12" description="April 15, 2026" tags={["patch"]}>
  ### Highlights

  #### License expiration banner

  Self-hosted organizations now see a banner in the sidebar as their license approaches expiration. It shows a clear countdown, and a follow-up notice during the grace period after expiration. Cloud organizations are not affected.

  #### Also in this release

  * Dashboard pages load faster. They combine several data requests into fewer round trips.

  ### Fixes

  * Analysis of very large repositories continues from where it left off if interrupted.
</Update>

<Update label="v0.10.11" description="April 14, 2026" tags={["patch"]}>
  ### Highlights

  #### Regenerate summaries for your whole organization

  You can now regenerate developer summaries for your entire organization from Settings. Previously you could only do this one repository at a time.

  ### Fixes

  * The discovered repositories page now loads faster and shows accurate result counts while paging through results.
  * Pull request data now loads for public repositories outside your connected GitHub organization.
  * Newly created teams now appear immediately in every team selector on the page, without needing a refresh.
</Update>

<Update label="v0.10.10" description="April 14, 2026" tags={["patch"]}>
  ### Highlights

  #### Stronger account security

  Navigara now requires stronger passwords when you sign up, reset your password, or accept an invitation. A checklist shows in real time whether your password meets the requirements as you type. Password reset requests are rate-limited, and email addresses are validated before an account is created.

  #### Faster repository analysis

  Analysis of larger repositories now scales horizontally. Organizations with heavy analysis workloads see faster processing. Source code parsing is also more efficient, improving analysis speed and reducing memory use.

  #### Also in this release

  * Invitations and organization access use stronger validation.
  * Repository selection during setup supports pagination and filtering by provider.

  ### Fixes

  * Page numbers on the commits list stay accurate when navigating between pages.
  * The probation period notice disappears automatically once the probation period ends.
</Update>

<Update label="v0.10.9" description="April 13, 2026" tags={["patch"]}>
  ### Fixes

  * Signing in now takes you to your dashboard, even if you also have a personal organization from onboarding.
  * Objectives you do not have permission to view now show a clear message instead of a not found page.
</Update>

<Update label="v0.10.8" description="April 13, 2026" tags={["patch"]}>
  ### Highlights

  #### Clickable commit references

  Commit references in reports and the period detail view are now clickable. Select one to jump straight to the source commit.

  ### Fixes

  * Analysis of large repositories now completes more consistently.
</Update>

<Update label="v0.10.7" description="April 12, 2026" tags={["patch"]}>
  ### Highlights

  #### Faster search across selectors

  Repository, developer, and user pickers now search on the server as you type. Selectors open instantly and results update as you search.

  #### Sortable, paginated file changes

  The file changes table on commit and developer pages supports sorting by complexity, engagement, and performance. Pagination handles commits that touch many files. You can also expand a commit's file changes directly from the developer page.

  #### Streamlined sign-in

  Login, invitation, and onboarding pages now show only the sign-in options your organization has configured. Icons and loading states are consistent across all three.

  #### Also in this release

  * Repository analysis skips example folders, dependency manifests, and changelog files, focusing on your actual source code.
  * The date picker on the add and edit repository dialogs is consistent across both, and opens on the month of the currently selected date.

  ### Important changes

  | What changed                                                                                    | What you will notice                                                                          | What you can do                                                                   |
  | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
  | The Projects feature (project filters and the "Performance by Project" chart) has been removed. | Project-based filtering and charts no longer appear on the repositories and objectives pages. | Use the repository and developer filters that remain in place for the same views. |
  | The "Waste" metric label is now called "Fixes" throughout the app.                              | Dashboards, charts, tooltips, and settings show "Fixes" instead of "Waste".                   | No action needed. The underlying metric is unchanged, only the label is new.      |

  ### Fixes

  * Re-inviting someone with an already-pending invitation refreshes their invitation rather than showing an error.
  * The edit repository dialog keeps your changes in place while data refreshes in the background.
  * Creating a team with a name that is already in use shows a clear error message.
  * Team names are limited to 255 characters, consistent across the app and API.
  * Setting a developer's primary email shows a confirmation toast.
</Update>

<Update label="v0.10.6" description="April 9, 2026" tags={["patch"]}>
  ### Highlights

  #### Bitbucket Server and Data Center support

  Organizations using a self-hosted Bitbucket Server or Data Center instance can now connect it the same way as Bitbucket Cloud. This includes pull request history, comments, and approvals.

  #### Licensing for self-hosted deployments

  Self-hosted deployments now include a license key system. Administrators can see trial and license status directly in the product.

  #### CapEx reports

  A new Reports section in the sidebar includes a CapEx report page with chart visualization. This gives finance and engineering leaders a clearer view of capitalized development effort.

  #### Also in this release

  * Invite links can now be copied directly from the invite dialog and from the pending invitations table.
  * The commits page now uses consistent pagination controls.
  * Commit lists can now be filtered by developer.
  * Connection setup now suggests the correct address format for host fields.
  * Accepting a team invitation now supports all available sign-in providers.

  ### Fixes

  * We updated underlying dependencies to strengthen platform security.
</Update>

<Update label="v0.10.3" description="April 8, 2026" tags={["patch"]}>
  ### Highlights

  #### Manage membership across every organization

  Platform administrators can now manage membership across every organization. They can assign the owner or admin role and remove any member. Organization-level admins keep their existing, more limited permissions.

  ### Fixes

  * The growth metric now displays its color clearly in all cases.
</Update>

<Update label="v0.10.0" description="April 8, 2026" tags={["minor"]}>
  Navigara v0.10.0 brings a role-aware view of your organization, more control over which repositories count toward your metrics, and better root-cause tracing for fixes.

  ### Highlights

  #### Role picker with role-filtered metrics

  You can switch between roles, for example engineer or manager, from a global picker. Every page, including dashboards, summaries, and reports, filters its metrics to match the selected role. This makes it easier to see the numbers that matter for a specific perspective.

  #### Repository settings and metrics exclusion

  Each repository now has a settings panel where you can exclude it from organization-wide metrics. When you turn on exclusion, Navigara recalculates all affected metrics in the background so dashboards and reports stay consistent.

  #### Deeper root-cause tracing for fixes

  Navigara traces fixes back to the commit that originally introduced the issue being fixed. This works even when the fix and the original change touch different files or functions. It gives more accurate context on developer summaries and commit history.

  #### Also in this release

  * Added a quarter option to the time-bucket selector, presented as a dropdown.
  * Repositories are shown with their owner and repository name instead of a raw URL.
  * Added Navigara tools for AI assistants, through MCP, to list repositories and objectives, fetch summaries, and query metrics directly.

  ### Important changes

  | What changed                                                             | What you will notice                                                            | What you can do                                                                  |
  | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
  | Code complexity scoring uses a more precise, per-symbol analysis method. | Complexity-related scores can shift slightly for past and future periods.       | Compare periods inside the app. All periods use the same updated method.         |
  | Engagement metrics weigh imports and non-code files more accurately.     | Engagement scores may change slightly for affected developers and repositories. | No action needed. The new values are more representative of actual contribution. |

  ### Fixes

  * Strengthened access controls around organization membership, repository management, and administrative actions.
  * Invitations can no longer be sent twice to the same address for an organization.
  * Settings pages show a clear error and revert your change if a save does not go through.
  * The developers list includes all available time-bucket sizes.
</Update>

<Update label="v0.9.9" description="March 27, 2026" tags={["patch"]}>
  ### Highlights

  #### AI-augmented badge on commits

  The commits list and commit detail page now show a badge on commits identified as AI-augmented. This applies when AI detection is enabled for your organization.

  #### Architecture overview

  The Features page is now Architecture. It has a filter bar for searching by name, category, and team, and a clearer table layout.

  #### Also in this release

  * Repositories now rank by total performance, so the sort order matches what is shown on the page.
  * Search when adding a repository now matches names anywhere, not only at the start, and shows how many results are available.

  ### Fixes

  * Editing a repository's analysis start date to an earlier date now updates its metrics and summaries to match.
  * Large charts on the commit detail page render smoothly.
  * The date picker in Add Repository shows the correct month.
  * Search in Add Repository waits briefly before searching, and no longer overwrites your results while a sync is in progress.
  * Sync and connection errors in Add Repository are shown so you know what to do next.
  * The commit detail page keeps the file changes table inside its card.
</Update>

<Update label="v0.9.8" description="March 24, 2026" tags={["patch"]}>
  ### Highlights

  #### Also in this release

  * Reanalyzing a commit from the interface now completes reliably and shows correct details.

  ### Important changes

  | What changed                                                                             | What you will notice                                                        | What you can do                                                                |
  | ---------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
  | Complexity and impact calculations now recognize renamed and moved files more precisely. | Complexity and impact scores for affected commits may be lower than before. | Compare periods inside the app. All periods use the same, updated calculation. |

  ### Fixes

  * Reanalyzing a commit now consistently displays its details.
</Update>

<Update label="v0.9.7" description="March 24, 2026" tags={["patch"]}>
  Navigara now connects to Azure DevOps, and architecture analysis becomes more flexible and more accurate.

  ### Highlights

  #### Azure DevOps support

  You can now connect Azure DevOps repositories to Navigara. Sign in with a personal access token or Microsoft Entra ID. Pull requests, reviewers, and approvals sync the same way they do for GitHub and GitLab.

  #### Flexible architecture analysis

  You can now choose which repositories architecture analysis covers: all of them, or a specific selection. Coverage also improved, so more of your codebase is captured under the right feature area.

  #### Also in this release

  * Signing in with Google now works reliably when your organization uses a custom frontend address.
  * Work attribution across shared directories and files touched by multiple features is now more accurate, reducing miscategorized activity.

  ### Important changes

  | What changed                                                                                                         | What you will notice                                                                                                          | What you can do                                                            |
  | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
  | Performance scores no longer count merge commits, which previously duplicated the scoring of the underlying commits. | Past and present performance scores may be lower than before, reflecting each developer's individual commits more accurately. | Compare periods inside the app — all periods now use the same calculation. |

  ### Fixes

  * Browser tabs left open across a deployment now reload automatically instead of showing repeated errors.
  * The developer breadcrumb now appears when navigating from a developer's page to one of their commits.
</Update>

<Update label="v0.9.6" description="March 19, 2026" tags={["patch"]}>
  ### Fixes

  * Repository pages now show all developers who have contributed, including developers first seen on another repository.
  * The developer list on a repository page now matches the performance totals shown above it, and uses the same table experience as the team page, including team, seniority, and role filters and column visibility controls.
</Update>

<Update label="v0.9.5" description="March 19, 2026" tags={["patch"]}>
  ### Fixes

  * Improved scheduling so analysis keeps processing smoothly, and other work like summaries and metrics keeps moving during heavy load.
  * Polished several display details across the app, including chart controls, filters, and labels on the Teams page and elsewhere, for a cleaner and more consistent look in both light and dark themes.
</Update>

<Update label="v0.9.4" description="March 18, 2026" tags={["patch"]}>
  ### Highlights

  #### Sign in with Microsoft

  You can now sign in to Navigara with your Microsoft account. This includes work, school, and personal accounts.

  #### Feature contributions chart

  The Features page now includes a chart. It shows developer contributions to each feature over time.

  #### Also in this release

  * The organization switcher now supports search and pagination. This makes it faster to find and switch between organizations.
  * The Features page now shows which features depend on each feature. This replaces the previous interface list.

  ### Fixes

  * Repository list pagination now uses the correct total count. Page numbers and navigation are accurate.
  * The organization role picker now shows each member's actual role.
</Update>

<Update label="v0.9.3" description="March 17, 2026" tags={["patch"]}>
  ### Highlights

  #### Custom AI model connections

  Navigara now supports OpenAI-compatible AI model endpoints, in addition to the default provider. This lets you connect the model that fits your setup.

  #### Role filter on the average performance chart

  You can now filter the average member performance chart by role. This makes it easier to compare like with like.

  #### Smarter developer matching

  Navigara now recognizes when the same developer commits using different email addresses. It keeps them as one developer profile, so activity and performance stay in one place.

  #### Also in this release

  * The Features area moved after Objectives in the sidebar for a more logical flow.

  ### Important changes

  | What changed                                                                            | What you will notice                                          | What you can do                                                           |
  | --------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------- |
  | The impact score calculation for commits now focuses on code complexity and engagement. | Impact scores may shift slightly compared to earlier periods. | Compare periods inside the app. All periods now use the same calculation. |

  ### Fixes

  * Root cause detection in commit analysis points to the originating commit more consistently.
  * Organizations with matching names automatically get a unique address.
  * Setup waits for your provider installation to finish before moving to the next onboarding step.
  * We strengthened the security of the platform.
</Update>

<Update label="v0.9.2" description="March 16, 2026" tags={["patch"]}>
  ### Highlights

  #### Objective detail pages

  Every objective now has its own detail page. It shows a stacked area chart of grow, maintenance, and waste effort over time, plus breakdowns by developer and by project. Objectives with no recorded work yet show a clear "work hasn't started" state instead of an empty chart. You can also open the linked Linear issue directly from the page.

  #### Features list

  Organizations that turn on architecture analysis in settings now get a Features page. It lists detected architectural features, with expandable details for each feature's dependencies and entry points.

  #### Also in this release

  * The objectives chart now has an Absolute / Percent toggle, so you can view effort as raw amounts or as a share of the total.
  * Admins can now invite multiple people by email at once from the organization panel.
  * Team average performance charts gained a comparison mode toggle.

  ### Fixes

  * Accepting an organization invitation now only auto-completes when the logged-in account matches the invited email.
  * Accepting an invitation now always switches your active session to the invited organization.
  * The team average performance graph animation now displays correctly.
</Update>

<Update label="v0.9.1" description="March 11, 2026" tags={["patch"]}>
  ### Highlights

  #### Bitbucket Cloud support

  You can now connect Bitbucket Cloud repositories alongside GitHub and GitLab. Navigara discovers your Bitbucket repositories, analyzes commits, and tracks pull requests the same way it does for other providers.

  #### See how work connects to your objectives

  Commits can now be linked to the Issue, sub-objective, and objective they belong to. This is based on your issue tracker hierarchy. It works whether you connected your repositories or your issue tracker first.

  #### Redesigned objectives page

  The objectives page has a cleaner chart and a performance column with an at-a-glance score. Objectives are now ordered by target date. Hovering a row highlights it on the chart and vice versa. You can filter to objectives active in your selected time range.

  #### Also in this release

  * Organizations can turn AI-detection columns on or off for their Developers, Repositories, and Teams tables.
  * Repository settings now include a "Check for new commits" option to catch up any commits that were missed.

  ### Fixes

  * Moving a repository's analysis start date to an earlier date now analyzes the commits in the newly covered range.
  * Reanalyzing a repository after a temporary processing issue no longer skips previously skipped commits.
  * The app no longer shows a stale-session error after a period of inactivity.
  * Background summary and metric updates now skip periods that are already finalized.
</Update>

<Update label="v0.9.0" description="March 9, 2026" tags={["minor"]}>
  Navigara v0.9.0 brings a new way to see how AI tools contribute to your codebase, more flexible work-category reporting, and a more organized way to structure objectives.

  ### Highlights

  #### AI-augmented commit detection

  Navigara now automatically identifies commits created with the help of AI coding tools. It uses signals like co-author information, commit patterns, and branch names. You will see an "AI %" badge next to performance scores on the developers, repositories, and teams pages, so you can track how much of your team's work is AI-assisted.

  #### Flexible work-category reporting

  You can now choose how work is grouped across dashboards, charts, and reports. Pick the classic Grow / Maintenance / Waste view, or a simplified Grow / KTLO view that combines maintenance and waste into one category. Switch anytime from Settings.

  #### Reorganized objectives

  Objectives can now be folded to show or hide their child projects. This makes it easier to scan a long list of objectives and drill into the ones you care about. Objective detail pages also show more accurate child status counts.

  #### Also in this release

  * Clicking a developer's icon now takes you straight to their developer profile.
  * The developers page gained filters for role, team, and seniority.
  * Developer avatars now use their connected GitHub profile picture where available.
  * The onboarding experience has a refreshed layout and icons.

  ### Important changes

  | What changed                                                                                                                          | What you will notice                                                              | What you can do                                                                                     |
  | ------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
  | Legacy quality, velocity, and performance scores have been retired in favor of the Grow / Maintenance / Waste (or Grow / KTLO) model. | These older score types no longer appear on dashboards or reports.                | Use the Grow / Maintenance / Waste (or Grow / KTLO) categories for the same insights going forward. |
  | Minimum password length for new and changed passwords is now 8 characters.                                                            | Signing up, resetting, or changing a password now requires at least 8 characters. | Choose a password of 8 characters or more.                                                          |

  ### Fixes

  * The role selector on the team performance graph now works.
  * Selected time range and bucket size are preserved when navigating between developer and team detail views.
  * Requests that hit a temporary rate limit now retry automatically.
  * Objectives show accurate child status counts and improved contrast for status themes.
  * Repository links in the commits view now take you to the correct repository page.
  * We strengthened the security of account authentication and password handling.
</Update>

<Update label="v0.8.2" description="February 27, 2026" tags={["patch"]}>
  ### Highlights

  #### Objectives from your issue tracker

  Navigara can now automatically create and update objectives from your issue tracker's initiatives. Objectives are matched using the initiative hierarchy. Branch names serve as a fallback when an issue reference is not available, so more of your delivery work is captured without manual setup.

  #### More deployment flexibility for self-hosted teams

  Organizations running Navigara on their own infrastructure can now run analysis independently from the rest of the platform. They can connect it over a dedicated network endpoint and turn on a dedicated analysis setting per organization. This gives self-hosted teams more control over how and where analysis runs.

  #### Move from self-hosted to cloud

  Teams running Navigara on their own infrastructure can now migrate their data to the Navigara cloud using a new migration tool.

  #### Also in this release

  * Performance charts on the developer and repository pages load more efficiently.

  ### Fixes

  * The developers page now loads more efficiently, with fewer unnecessary requests.
  * Repository sync now reliably detects updated pull requests.
  * Dashboard sections recover gracefully if an error occurs, without affecting the rest of the page.
  * Analysis is more stable for repositories that contain non-standard text encoding.
  * We strengthened the security of authentication and internal communications.
</Update>

<Update label="v0.8.1" description="February 25, 2026" tags={["patch"]}>
  ### Fixes

  * The performance deviation percentage on developer and repository charts now uses the same benchmark baseline as the chart line, so the percentage and the chart always agree.
  * Open tabs refresh automatically after a new deployment, so you can keep taking actions without interruption.
</Update>

<Update label="v0.8.0" description="February 25, 2026" tags={["minor"]}>
  ### Highlights

  #### Guided onboarding

  New organizations now go through a guided setup. Tell us about your organization, connect your code source, choose the repositories to analyze, and watch Navigara analyze them in real time. You can navigate between steps using the page URL, and your progress is saved if you refresh.

  #### Sign in and connect with GitLab

  You can now sign in to Navigara with GitLab, alongside Google and GitHub. Organizations can also connect GitLab during onboarding or from Settings to discover and analyze repositories across their GitLab groups.

  #### Linear workspace integration

  Connect your Linear workspace from Settings to bring initiatives, projects, and issues into Navigara. Commits are automatically linked to the Linear issues they reference, and objectives are created and kept in sync from your Linear initiatives.

  #### Also in this release

  * Repository analysis now includes pull requests and merge requests from GitHub and GitLab, linked to the commits that merged them.
  * The developers and objectives pages now support keyboard navigation and are easier to use with screen readers.

  ### Fixes

  * Pagination controls across list pages now render correctly in both light and dark mode.
  * Newly connected repositories now start with the correct default branch.
  * We strengthened the security of organization membership, invitations, and data queries across the platform.
</Update>

<Update label="v0.7.7" description="February 23, 2026" tags={["patch"]}>
  ### Fixes

  * Invitation links now show the right sign-in or sign-up form based on whether you already have an account.
  * Analysis automatically recovers if a connection is interrupted partway through, without losing progress.
</Update>

<Update label="v0.7.6" description="February 19, 2026" tags={["patch"]}>
  ### Highlights

  #### MCP server for AI assistants

  Navigara now offers an MCP (Model Context Protocol) server. AI assistants such as Claude Desktop and Cursor can connect directly using your API key. Assistants can list your teams and pull AI-generated commit summaries and performance scores for a team without leaving the chat.

  #### Faster developers list

  The developers list now loads faster. Sorting and pagination are now handled server-side.

  ### Important changes

  | What changed                                                                                                 | What you will notice                                                                      | What you can do                                                                                   |
  | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
  | Developer and team metrics now group activity by developer identity instead of email address.                | Counts and charts for developers with multiple linked email addresses may shift slightly. | Review team and developer pages. Merged developer identities are grouped consistently everywhere. |
  | The dashboard "Top 20% Sum" widget now calculates the top-performer share as a portion of total performance. | This value can now be lower than total performance.                                       | Use the widget to compare top-developer concentration against total output.                       |

  ### Fixes

  * Invitation links now open for people who have not signed in yet.
  * Team pages now show the Repositories section and the Developer Performance chart.
  * The analysis status no longer shows an error badge for a run that a newer, successful run has already replaced.
  * Analysis now skips auto-generated helper files from framework tooling, keeping developer metrics focused on real work.
</Update>

<Update label="v0.7.5" description="February 17, 2026" tags={["patch"]}>
  ### Important changes

  | What changed                                                                                                   | What you will notice                                                                             | What you can do                                                                             |
  | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
  | Performance score calculation (growth, maintenance, and cleanup values) has been updated for report summaries. | Performance scores in your Reports may change. The performance badge now appears in more places. | Regenerate existing reports to see the updated scores. No action is needed for new reports. |
</Update>

<Update label="v0.7.4" description="February 17, 2026" tags={["patch"]}>
  ### Fixes

  * Excluding or including a commit now updates repository metrics right away. Excluded work no longer appears in graphs and reports.
  * Repository analysis details, such as author and cost information, are preserved when a later analysis attempt does not complete.
</Update>

<Update label="v0.7.3" description="February 17, 2026" tags={["patch"]}>
  ### Fixes

  * Analysis scheduling now skips repositories you have stopped.
  * Analysis scheduling only re-processes repositories with new activity, instead of repeating completed work.
</Update>

<Update label="v0.7.2" description="February 17, 2026" tags={["patch"]}>
  Navigara now processes only new activity during daily repository syncs, keeping your data current with less delay.

  ### Fixes

  * Daily repository syncs now process only new commits since the last analysis, so your data stays up to date faster.
  * Large repositories now have more time to complete analysis, improving reliability for repositories with a high volume of history.
</Update>

<Update label="v0.7.0" description="February 16, 2026" tags={["minor"]}>
  ### Highlights

  #### API tokens for programmatic access

  You can now create and manage Navigara API tokens directly from Settings. Generate a token, copy its key once at creation time, and revoke it later when it is no longer needed.

  #### Developer avatars

  Developers and teams now show profile pictures pulled from GitHub or GitLab. Clean initials appear as a fallback when no picture is available.

  #### Faster, more flexible metrics

  Performance metrics are now precomputed and stored in a query-ready form. Dashboards and reports load faster and stay consistent as team membership and tags change over time.

  #### Also in this release

  * Commits can now be sorted by performance on the commits page.
  * The performance chart legend shows a tooltip explaining each series.
  * The admin panel shows analysis connection status, so operators can see health at a glance.
  * Developer detail pages paginate commits for smoother browsing on active developers.
  * Light theme styling has been refined across components.
  * The time picker better recognizes preset ranges and remembers your selection across page refreshes.
  * You can now filter developers by when they joined and by probation status.

  ### Fixes

  * Commits appear in the report sheet view.
  * Trend calculations in the dashboard summary section are accurate.
  * Minified files are skipped during commit analysis, avoiding noise in results.
  * The zero-day index only applies to developers, as intended.
  * Team assignment reflects current team membership consistently.
  * Developers with missing email data are handled in commit queries.
  * Session handling has been made more resilient, reducing unexpected sign-outs.
</Update>

<Update label="v0.6.3" description="February 6, 2026" tags={["patch"]}>
  ### Fixes

  * You can now add a personal access token for a GitHub Enterprise instance. If adding the token fails, you now see a clear message instead of the dialog closing silently.
</Update>

<Update label="v0.6.2" description="February 6, 2026" tags={["patch"]}>
  ### Highlights

  #### GitHub Enterprise support for tokens

  Navigara now validates access tokens against GitHub Enterprise instances, not just github.com. If your organization runs its own GitHub Enterprise deployment, you can add and use tokens for it directly.

  #### Also in this release

  * The Add token dialog now shows a clear, specific message when a token cannot be validated.

  ### Important changes

  | What changed                                                                                          | What you will notice                                                            | What you can do                                                           |
  | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
  | The newcomers table on the developer dashboard uses a consistent calculation for performance figures. | Numbers for newcomers on the dashboard may look slightly different than before. | Compare periods inside the app. All periods now use the same calculation. |
</Update>

<Update label="v0.6.1" description="February 5, 2026" tags={["patch"]}>
  ### Highlights

  #### Simplified connections settings

  The Tokens page is now part of Connections. Each provider (GitHub, GitLab, Bitbucket) shows as a collapsible card with its token count and an expandable token list. You manage every connection from one place.

  #### Repositories contribution on team detail

  Team detail pages now include a repositories contribution section. It shows which repositories a team's developers are actively contributing to.

  #### Also in this release

  * Filters show a clearer selected state and support multiple active filters at once.
  * Line charts show a loading skeleton while data is being fetched.
  * Your selected time range and bucket size are preserved as you navigate between pages.
  * Git tokens let you specify the provider explicitly, improving support for self-hosted GitHub Enterprise, GitLab, and Bitbucket instances.

  ### Important changes

  | What changed                                                                                                                                 | What you will notice                                                                               | What you can do                                                               |
  | -------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
  | The reach factor in performance scoring now counts unique external files that depend on a change, excluding references within the same file. | Performance scores for some commits, especially in files with many internal references, may shift. | Compare periods inside the app. All periods use the same updated calculation. |

  ### Fixes

  * Team charts load team members directly, so team performance data displays reliably.
  * Metadata updates handle empty values, keeping repository and team metadata consistent.
</Update>

<Update label="v0.6.0" description="February 4, 2026" tags={["minor"]}>
  Navigara v0.6.0 introduces Teams, a new way to group developers and track their performance together, along with a redesigned developer detail page and a smoother reporting experience.

  ### Highlights

  #### Teams

  You can now group developers into Teams and view their combined performance over time. Each team gets its own detail page with a performance chart, member search, and an AI-generated summary of the team's work. You can create, edit, and configure teams from Organization Settings.

  #### Developer detail redesign

  The developer detail page now shows a repository-by-repository breakdown of performance. This makes it easier to see where a developer's work is happening. Charts across the product now share one consistent tooltip style, so you can compare grow, maintenance, and waste values at a glance.

  #### Also in this release

  * The projects list has a refreshed layout.
  * Reports now animate smoothly when opening.
  * Organization Settings includes a new option to refresh your data on demand.

  ### Fixes

  * The developers table on the dashboard updates when you change the time range.
  * The performance graph on the team detail page displays reliably.
  * Charts and filters are easier to read in light theme.
  * The server shuts down cleanly during restarts, avoiding delayed availability.
</Update>

<Update label="v0.5.0" description="January 30, 2026" tags={["minor"]}>
  ### Highlights

  #### Redesigned dashboard, repository, and developer views

  The dashboard, repository detail page, and repositories list page have a new look and feel, with clearer layouts. The repositories list also has a new performance chart. Developer list tables on the dashboard are redesigned for easier scanning, and graph line tooltips are now clearer and easier to read.

  #### Also in this release

  * Analytics queries now support an industry-standard dimensions option for more flexible reporting.

  ### Fixes

  * Developer avatar initials now display when a name contains non-letter characters.
  * Commit history for developers now includes all of their associated email addresses.
</Update>

<Update label="v0.4.7" description="January 29, 2026" tags={["patch"]}>
  Small workflow improvements to developer reports, plus two connection fixes.

  ### Highlights

  #### Faster navigation to developer detail

  Click a point on a developer's line graph, or a time period on the developer detail page, to jump straight to the matching report. You can also sort commits inside the report pop-up window.

  #### Also in this release

  * Cleaned up spacing in the report pop-up window and on pages without a stat card.

  ### Fixes

  * Developers who commit using GitHub's private "noreply" email address are now matched to their existing account.
  * Repository sync with a GitLab on-premises server now completes when the server URL is entered without a protocol prefix.
</Update>

<Update label="v0.4.6" description="January 27, 2026" tags={["patch"]}>
  ### Fixes

  * The retry failed button in the work queue now retries only the failed items. You can recover from errors without rescanning everything else.
</Update>

<Update label="v0.4.1" description="January 26, 2026" tags={["minor"]}>
  ### Highlights

  #### Connect repositories with a GitHub App

  You can now connect your GitHub organization using a GitHub App instead of managing personal access tokens. This also improves developer matching by recognizing multiple email addresses, including no-reply and alias addresses, for the same developer.

  #### Redesigned developer list

  The developers list has a refreshed look. It includes a new performance graph, clearer table columns, simplified filters, and a new pagination control with a page size selector.

  #### Also in this release

  * You can now edit a developer's joining date, set a probation period, and filter the developer list by probation status.
  * The performance graph and its deviation stat card have a cleaner, easier-to-read design.

  ### Important changes

  | What changed                                            | What you will notice                                                                                                 | What you can do                                                                     |
  | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
  | Performance metrics are now expressed on a 0-100 scale. | Metric values across the app will look different from before, even though they reflect the same underlying activity. | Compare periods inside the app going forward. All periods use the same 0-100 scale. |

  ### Fixes

  * Cloning private repositories connected through a GitHub App now works reliably.
  * Charts display dates consistently regardless of your time zone.
  * Week numbers on charts that start on Sunday now display correctly.
  * Repository data access is now scoped to the correct organization.
</Update>

<Update label="v0.3.19" description="January 22, 2026" tags={["patch"]}>
  ### Fixes

  * The repository benchmark selector no longer shows an option for a day with no activity.
  * Performance summaries generate only for fully completed periods. This gives you more consistent results.
</Update>

<Update label="v0.3.18" description="January 22, 2026" tags={["patch"]}>
  ### Highlights

  #### Zero-day index view

  Charts now offer a Zero-day index visualization mode alongside the Organization average. It shows upper and lower bands around the benchmark average, so you can see how performance spreads over time. The legend and tooltip show performance, average, and spread.

  #### Custom benchmarks in charts

  You can now select a custom benchmark from the chart dropdown menu, in addition to Organization average and Zero-day index. The average performance deviation card updates its name to match your selected benchmark.

  #### Also in this release

  * The Zero-day index option is now available directly from the repositories dropdown menu.

  ### Fixes

  * Repository sync now completes reliably, even when some items previously required a retry.
</Update>

<Update label="v0.3.14" description="January 20, 2026" tags={["patch"]}>
  ### Highlights

  #### Copy your organization ID

  The general settings page now shows your organization ID. Use the one-click copy button to share it quickly when needed.
</Update>

<Update label="v0.3.13" description="January 20, 2026" tags={["patch"]}>
  ### Highlights

  #### Filter dashboard metrics by developer group

  You can now filter dashboard metrics by a group of developers at once. This makes it easy to compare a selected cohort against team or organization averages.
</Update>

<Update label="v0.3.12" description="January 17, 2026" tags={["patch"]}>
  ### Highlights

  #### Improved commit analysis quality

  We upgraded the underlying model that powers commit analysis. This improves the quality of analysis results.
</Update>

<Update label="v0.3.9" description="January 16, 2026" tags={["patch"]}>
  ### Highlights

  #### Faster commit history for large repositories

  Pages that list commits and developer activity now load significantly faster for organizations with large histories. This holds even with tens of thousands of commits.

  #### Faster analysis processing

  Behind-the-scenes processing for developer summaries is now much lighter on system resources. This keeps analysis running smoothly as organizations grow.

  ### Important changes

  | What changed                                                                                                                                      | What you will notice                                                                                                           | What you can do                                                               |
  | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
  | Commit analysis now more thoroughly excludes generated and bundled build files (for example, minified JavaScript output) from complexity scoring. | Developer activity and complexity scores may shift for repositories that commit build output, better reflecting original work. | No action needed. The improved detection applies automatically going forward. |

  ### Fixes

  * Large result sets on the commits list now keep filtering and pagination consistent across pages.
</Update>

<Update label="v0.3.8" description="January 15, 2026" tags={["patch"]}>
  ### Fixes

  * Commit detail pages now load reliably in repositories with a large commit history.
  * When you merge or split a developer's email addresses, their commit history, contribution graph, and metrics update automatically to match.
</Update>

<Update label="v0.3.7" description="January 15, 2026" tags={["patch"]}>
  ### Fixes

  * The developer page now updates after you type a custom date into the time filter.
</Update>

<Update label="v0.3.6" description="January 15, 2026" tags={["patch"]}>
  ### Highlights

  #### Simplified dashboard navigation

  Dashboard pages no longer show a back-arrow control. Use your browser's back button or breadcrumbs to move around.

  ### Fixes

  * The sidebar toggle icon now collapses and expands the sidebar.
</Update>

<Update label="v0.3.5" description="January 14, 2026" tags={["patch"]}>
  ### Fixes

  * The navigation sidebar now collapses and expands smoothly, and the toolbar stays aligned with it.
</Update>

<Update label="v0.3.4" description="January 13, 2026" tags={["patch"]}>
  Navigara now gives you more control over which commits count toward your metrics, and refines how developer performance is measured against the organization average.

  ### Highlights

  #### Exclude commits from metrics

  You can now exclude individual commits from performance metrics, with a reason you choose. Excluded commits are marked on the commit page and are left out of all metrics calculations.

  #### Also in this release

  * Reanalyzing a commit now uses the improved analysis process, giving you more consistent results.

  ### Important changes

  | What changed                                                                                                                                                                   | What you will notice                                                                                 | What you can do                                                                          |
  | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
  | Developer and repository performance deviation is now calculated as the difference from the average performance per active developer, instead of an average of daily averages. | Deviation percentages on developer and repository pages can shift slightly from what you saw before. | Compare periods inside the app going forward — all periods now use the same calculation. |

  ### Fixes

  * Repositories pages linked directly with a time range in the URL now load and filter correctly.
  * Repositories hosted on GitLab Enterprise now detect the default branch reliably, even when it is not included in the initial project listing.
</Update>

<Update label="v0.3.3" description="January 13, 2026" tags={["patch"]}>
  ### Fixes

  * Summary reports now filter correctly by schedule type, scope, and period.
  * The file list dropdown in commit details now responds correctly when you select an item.
</Update>

<Update label="v0.3.1" description="January 13, 2026" tags={["patch"]}>
  Organization owners now have more control over their team, and repository discovery is clearer.

  ### Highlights

  #### Team member management

  Organization owners and admins can change a member's role, remove a member, or cancel a pending invitation. Each action has a confirmation step to prevent accidental changes. The owner role is shown as a fixed badge. You can no longer remove yourself or change your own role by accident.

  #### Also in this release

  * The developers table shows email addresses in a tooltip when you hover over a developer's name, keeping the table itself cleaner.
  * Repository discovery shows a loading indicator while Navigara searches for repositories to add.

  ### Important changes

  | What changed                                                                                                                                                                                                                                     | What you will notice                                                                           | What you can do                                                                                      |
  | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
  | Organization invitations and role settings no longer offer an "Admin" organization role. Only Owner, Member, and Viewer are available. The UI labels "Platform role" (system-wide) separately from "Organization role" (within an organization). | Existing members keep their current role. New invitations only offer Owner, Member, or Viewer. | Review your organization's member roles in team settings if you relied on the previous Admin option. |

  ### Fixes

  * Repositories with no commits in the selected period show a clear "No commits" status.
  * Clicking the dependency arrow in the file changes table keeps your session active.
  * Period summaries update in place and show when they were last generated.
</Update>

<Update label="v0.3.0" description="January 12, 2026" tags={["minor"]}>
  ### Highlights

  #### Configurable periodic summaries

  Navigara now generates periodic summaries automatically. You get a regular, up-to-date view of developer and repository performance without asking for one.

  #### Redesigned performance graphs

  Repository and developer performance graphs now let you switch between relative and absolute views. You can compare against the organization average from a dropdown menu.

  #### Visibility into skipped files and commits

  Analysis now shows which files and commits were filtered out, for example lockfiles or generated code. A clear explanation shows what is included in your metrics.

  #### Also in this release

  * A quick-access arrow on the repository developers list takes you straight to each developer's page.

  ### Important changes

  | What changed                                                                                                                                                                      | What you will notice                                                             | What you can do                                                           |
  | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
  | The performance deviation stat now compares a repository's total output (growth, maintenance, and waste combined) against the organization's monthly average for the same period. | Deviation values on repository and developer pages can shift compared to before. | Compare periods inside the app. All periods now use the same calculation. |

  ### Fixes

  * The developers page loads for organizations with more than 1,000 developers.
  * You can assign a developer to a team in organizations with more than 1,000 developers.
  * Seniority level displays for developers.
  * Benchmark charts aggregate data based on the selected time bucket.
</Update>

<Update label="v0.2.1" description="January 5, 2026" tags={["patch"]}>
  ### Highlights

  #### Custom benchmarks

  You can now save groups of developers or repositories to compare against. Choose average, median, or another percentile for how the group is aggregated, so comparisons match the way your team works.

  ### Fixes

  * Newly connected repositories now show complete commit metrics from the start of analysis.
</Update>

<Update label="v0.2.0" description="January 5, 2026" tags={["minor"]}>
  This release brings cleaner performance charts, more reliable repository views, and new developer tracking fields.

  ### Highlights

  #### Flexible time aggregation for commit activity

  The Commits view now lets you group commit activity by day, week, or month. Zoom in for recent detail or zoom out for a longer trend.

  #### Probation tracking for developers

  You can now record a developer's joining date and end of probation date. This makes it easier to track ramp-up periods alongside performance history.

  #### Also in this release

  * Developer day detail pages now show the developer's name in the breadcrumb.
  * The global time picker now accepts month ranges that span into the next year, for example "Dec 2025 - Jan 2026".

  ### Fixes

  * Repository pages keep open dropdown menus open while a repository analysis is in progress.
  * Performance and dashboard charts show date labels clearly, without overlapping text.
  * Selecting a seniority level on the developer filters no longer clears the selected team, and vice versa.
</Update>

<Update label="v0.1.7" description="December 30, 2025" tags={["patch"]}>
  ### Highlights

  #### Seniority levels for developers

  You can now assign a seniority level to each developer. Choose Junior, Medior, Senior, or a custom level. Use the new seniority filter to view and compare developers by level.
</Update>

<Update label="v0.1.6" description="December 29, 2025" tags={["patch"]}>
  Navigara now gives clearer summaries of your team's activity, makes token expiration easy to track, and adds a more flexible time picker.

  ### Highlights

  #### Clearer, more factual period summaries

  Period summaries describe what happened in plain, factual language. Commit and pull request references in a summary are clickable links, and key terms are highlighted for faster scanning.

  #### Redesigned time picker

  The time picker supports typing values directly and selecting custom ranges, with a fixed default time. This makes it faster to pick the exact period you want to view.

  #### Refreshed developer page

  The developer page has a cleaner, more consistent layout.

  #### Also in this release

  * API tokens on the tokens settings page show their expiration date, with clear badges for tokens that are expired or expiring soon.
  * Team and project charts use improved metric colors for better readability.

  ### Fixes

  * The invitation login page displays correctly.
  * Bucket size selection in team and project charts applies correctly.
  * Token expiration dates from GitHub are parsed correctly regardless of timezone format.
</Update>

<Update label="v0.1.5" description="December 19, 2025" tags={["patch"]}>
  ### Highlights

  #### PHP analysis

  Navigara now analyzes PHP repositories with the same depth as other supported languages. This includes accurate symbol detection and reference finding across your PHP codebase.

  #### Also in this release

  * List pages across Navigara (developers, teams, projects, repositories) now consistently apply your selected time range.

  ### Important changes

  | What changed                                                                                                   | What you will notice                                                                        | What you can do                                                           |
  | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
  | The developers table now includes AI-assisted waste time in its totals, alongside growth and maintenance work. | Totals on the developers table may be higher than before for periods with AI-assisted work. | Compare periods inside the app. All periods now use the same calculation. |

  ### Fixes

  * Metrics now stay consistent when the same commit affects multiple repositories.
  * The time period selector now works after refreshing the page.
</Update>

<Update label="v0.1.0" description="December 18, 2025" tags={["major"]}>
  Navigara is now available. This first release brings together AI-powered performance insights, flexible views of your Developers, Repositories, Teams, and Projects, and the account tools you need to get your Organization set up.

  ### Highlights

  #### AI-powered performance summaries

  Navigara generates AI-powered summaries for Repositories and Developers. Each summary highlights key strengths, concerns, and recommendations based on recent activity. You can regenerate a summary at any time as new work comes in.

  #### Teams and projects

  You can group Developers into Teams and Repositories into Projects. Each Team and Project gets its own detail view with a performance graph and a table of its members. This lets you track work at the level that matters to you.

  #### Commit knowledge graph

  Commit detail pages include an interactive graph. It shows how a commit's changes connect to the rest of your codebase. This makes it easier to understand the scope and impact of a change at a glance.

  #### Also in this release

  * A global time picker lets you choose custom date ranges and bucket sizes across dashboards.
  * Members can switch between Organizations they belong to directly from the sidebar.
  * Dashboards, Repositories, and Developer pages have clearer performance charts and benchmark visualizations.
  * Organization owners can invite members, manage Repository tokens, and reset passwords.
  * Repositories can be tagged and automatically grouped by Project.

  ### Fixes

  * Time range selections carry through to Team, Project, and Developer detail pages.
  * The Repository detail page shows the combined score for each developer.
  * Charts show only bars that reflect data for the selected range.
  * Developer emails are matched consistently regardless of capitalization, so contributions group correctly.
</Update>
