<!--
Audience
  External customers using the Aerion browser extension (Chrome and Firefox,
  which release in lockstep). Treat this as a shipped product: do not mention
  internals, frameworks, or repo plumbing.

Forbidden words / leaks
  Do not name implementation details: "React", "Redux", "webpack",
  "TypeScript", "content script", "manifest", "service worker", "postMessage",
  component names, file paths, ticket IDs (DEV-, CC-, MCP-). Rephrase as
  user-visible outcomes.

Style
  Terse and outcome-focused. Describe the user-visible effect, not the
  mechanism. One short sentence per change; "editorialize a little" is fine,
  field-by-field detail is not.

Vantage point
  Write from the customer's POV — what they observe — not the implementer's.

Surface (do mention)
  - New capabilities and visible UI changes.
  - Behavior changes customers will notice (faster, fewer clicks, new
    validation, copy changes).
  - Bug fixes that resolve customer-visible breakage.

Don't surface
  - Refactors, file moves, type-only changes, dependency bumps.
  - Internal observability, build, or test infrastructure.
  - Mechanism / framework details, ticket IDs.
-->

# Aerion Browser Extension (Chrome/Firefox) Release Notes

## v3.0.1 — 2026-06-22

- Fixed the extension unexpectedly interrupting Aerion login flows on other platforms

## v3.0.0 — 2025-09-23

- Rebranded from CoffeeCup to Aerion.
- Added single sign-on with Google and Microsoft.
- Updated to manifest v3 on Firefox

## v2.6.2 — 2024-11-22

- Updated to manifest v3 on Chrome

## v2.2.0 — 2023-02-14

- Refreshed the reference status design and the toolbar icon, now with dark-mode support.
- Fixed references for Jira projects with similar short codes being grouped under the wrong project.