release: promote main

[github-actions]

Everything on main that release does not have yet. Merging this is what puts it in
front of users, because release is what a deploy and a plain clone both point at.

Nothing releasable is waiting — no version bump will ride along with this.

Merge it with a merge commit, not a squash: a squash would give release a new
commit of its own, and the tags on main would stop being ancestors of what you shipped.

• chore: release main (chore: release main #78)

---

Summary by cubic

Promote v1.3.0 from main to release to ship recent features and fixes. Merge with a merge commit (no squash) to preserve tag ancestry.

• New Features

  • Microsoft sign-in and Outlook mailbox sync.
  • Delete companies, contacts, and deals via API.
  • New dashboard and overview components.
  • SEO audit skill and marketing flag for landing visibility.

• Bug Fixes

  • Generate route types before type checking.
  • Improved redirect logic for signed-out users and sign-in path.

^{Written for commit f27e1d0. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
crm-agent	Ready	Preview	Aug 7, 2026 3:49pm
crm-api	Ready	Preview	Aug 7, 2026 3:49pm
crm-app	Ready	Preview	Aug 7, 2026 3:49pm

[cubic-dev-ai]

1 issue found across 3 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="CHANGELOG.md">

<violation number="1" location="CHANGELOG.md:3">
P2: The added 1.3.0 section advertises as new a set of commits already released in 1.2.0/1.1.0/1.0.0 (e.g. microsoft sign-in 2a0062f also in 1.2.0; brand-mapping aad5945 also in 1.0.0; the rest identical to 1.1.0). This contradicts the PR intent that nothing releasable/versioned rides along, and ships a 1.3.0 changelog that misrepresents the release as containing features users already received. Verify the release source/tag selection so 1.3.0 only lists commits not in any earlier release, or drop the empty version bump.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The added 1.3.0 section advertises as new a set of commits already released in 1.2.0/1.1.0/1.0.0 (e.g. microsoft sign-in 2a0062f also in 1.2.0; brand-mapping aad5945 also in 1.0.0; the rest identical to 1.1.0). This contradicts the PR intent that nothing releasable/versioned rides along, and ships a 1.3.0 changelog that misrepresents the release as containing features users already received. Verify the release source/tag selection so 1.3.0 only lists commits not in any earlier release, or drop the empty version bump.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At CHANGELOG.md, line 3:

<comment>The added 1.3.0 section advertises as new a set of commits already released in 1.2.0/1.1.0/1.0.0 (e.g. microsoft sign-in 2a0062f also in 1.2.0; brand-mapping aad5945 also in 1.0.0; the rest identical to 1.1.0). This contradicts the PR intent that nothing releasable/versioned rides along, and ships a 1.3.0 changelog that misrepresents the release as containing features users already received. Verify the release source/tag selection so 1.3.0 only lists commits not in any earlier release, or drop the empty version bump.</comment>

<file context>
@@ -1,5 +1,53 @@
 # Changelog
 
+## [1.3.0](https://github.com/trycompai/crm/compare/v1.2.0...v1.3.0) (2026-08-07)
+
+
</file context>