chore(main): release 1.15.3 - #176
Merged
carhartlewis merged 1 commit intoAug 21, 2026
Merged
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
github-actions
Bot
force-pushed
the
release-please--branches--main--components--crm
branch
from
August 21, 2026 14:21
ca3e6af to
13e1e7c
Compare
carhartlewis
deleted the
release-please--branches--main--components--crm
branch
August 21, 2026 14:24
Contributor
Author
|
🤖 Created releases: 🌻 |
strats360
pushed a commit
to strats360/crm
that referenced
this pull request
Aug 24, 2026
* Implement currency conversion features and enhance deal handling - Introduced a new CurrencyModule to manage currency conversion and rates. - Added ConversionService for handling currency conversions and fetching rates. - Updated DealsService to support base amounts and currency conversion logic. - Enhanced Deal and Dashboard functionalities to include reporting currency and unconverted deals. - Implemented new currency-related contracts and routes for setting reporting currency and manual rates. - Added integration tests to ensure correct handling of currency conversions and deal totals. * Refactor currency rates service to use open.er-api.com - Updated the currency rates service to fetch exchange rates from open.er-api.com, replacing the previous provider frankfurter.dev. - Enhanced error handling to check for unsupported base currencies in the response. - Implemented retry logic for fetching rates with a maximum of two attempts and a reduced timeout. - Cleaned up stale exchange rates for unsupported currencies during the refresh process. - Updated documentation to reflect the new exchange rate provider and its implications. * Enhance currency handling and conversion logic - Introduced baseCurrency to the Deal model to track the currency of baseAmount. - Updated ConversionService to streamline currency conversion processes and improve deal field handling. - Enhanced CurrencyService to enforce permissions for managing currency settings based on user roles. - Refactored DealsService to incorporate base currency logic in deal aggregations and reporting. - Improved DashboardService to accurately reflect open deal values based on the current reporting currency. - Updated integration tests to validate new currency handling features and ensure correct behavior across services. * Enhance currency conversion logic and improve deal handling - Updated `pendingWhere` method in `ConversionService` to explicitly match null `baseCurrency`, ensuring no deals are excluded from totals. - Added integration test to verify that deals with missing currency are correctly handled and updated. - Modified seeding logic to ensure `baseCurrency` is set alongside `baseAmount` for newly created deals, preventing issues with unconverted figures. - Updated documentation to clarify changes in currency handling and the implications for deal visibility. * Refine currency conversion logic and enhance deal handling - Updated `ConversionService` to conditionally clear rates only when `onlyMissing` is false, improving efficiency in handling missing currencies. - Enhanced integration tests to verify correct behavior when dealing with unconverted figures and missing currency rates. - Introduced a new utility function in the deal sheet component to manage currency options, ensuring proper display of unsupported currencies. * Revise agent and API documentation for clarity and structure - Updated AGENTS.md to emphasize the importance of reviewing relevant documentation before starting work, including a new index table for quick reference. - Refined API rules in api.md to clarify logging practices and the separation of intelligence from the API. - Consolidated environment setup instructions into a new setup.md file for better organization and ease of access. - Enhanced currency handling in DashboardService and related tests to ensure accurate reporting and conversion logic. - Improved integration tests to validate new currency handling features and ensure correct behavior across services. * Enhance documentation and introduce new currency handling guidelines - Updated AGENTS.md to include new references for the Agent panel and local setup instructions. - Added a new docs/agent-panel.md file detailing the Agent panel's functionality and usage. - Introduced docs/currency.md to clarify currency handling rules and reporting practices. - Revised environment setup instructions in docs/environment.md for better clarity and organization. * Add anonymous usage telemetry documentation and enhance currency handling in DealSheet * Implement anonymous usage telemetry and enhance related documentation - Added telemetry functionality to track anonymous usage data, including installation metrics and tool usage. - Introduced new environment variables for telemetry configuration in `.env.example`. - Updated `AGENTS.md` to reference the new telemetry documentation. - Created a `TelemetryModule` with services and controllers for managing telemetry data. - Added a settings page for telemetry configuration in the application. - Enhanced error handling and logging for telemetry events across various services. - Removed outdated ADR on telemetry usage from the repository. * Remove telemetry-related components and references from the application - Deleted the TelemetryRouter and its associated service, removing the telemetry status query. - Updated the settings sidebar to eliminate the Telemetry option. - Removed the TelemetrySettingsPage and its related components, including the TelemetryStatus display. - Cleaned up unused imports and references to telemetry throughout the codebase. * Enhance telemetry functionality and improve budget management - Added an 'exhausted' state to the focus management to track when the research budget is depleted. - Updated the spend function to prevent multiple budget exhaustion events from being recorded. - Refactored the rollup service to handle telemetry rollup claims and restore counters more effectively. - Improved error handling in telemetry events to ensure proper reporting and recovery from failures. - Enhanced documentation to clarify the behavior of telemetry when disabled and the implications for data integrity. * Add telemetry support and enhance landing page analytics - Introduced `@crm/telemetry` package to manage telemetry configurations and constants. - Integrated `posthog-js` for analytics on the landing page, ensuring it only runs on allowed domains. - Updated the `LandingAnalytics` component to initialize analytics tracking based on hostname. - Enhanced the `audit` hook to exclude specific event types from archiving. - Improved agent session handling by implementing offline thread management. - Added utility functions for analytics host validation and created tests for the new functionality. - Updated documentation to reflect changes in telemetry usage and landing page analytics. * Update agent panel to use SETTLED_TTL_MS for archive stale time and enhance documentation - Changed the `staleTime` for the archive query in the agent panel from `Infinity` to `SETTLED_TTL_MS` to ensure proper session management. - Updated documentation to clarify the behavior of the archive in relation to session state and stale time handling. * Enhance landing page analytics with CTA event tracking - Introduced `captureLanding` function to track user interactions with the setup prompt and GitHub star buttons. - Updated `SetupPromptButton` and `GitHubStarButton` components to accept a `location` prop for distinguishing between 'hero' and 'closing' CTAs. - Modified `LandingAnalytics` to include new event types for clipboard actions and button clicks. - Enhanced documentation to reflect the new telemetry events and their usage. * Update README with new images and remove outdated ones - Replaced outdated images with new visuals for the landing page, showcasing agents and capabilities. - Removed references to deleted images related to deals, contacts, and companies to streamline documentation. * Refactor README to improve layout of screenshots - Converted individual screenshot sections into a table format for better visual organization. - Updated captions for clarity and conciseness, enhancing the overall presentation of the landing page visuals. * Update README and images for landing page - Removed outdated captions from the README for agents and capabilities images to streamline content. - Updated binary images for agents, capabilities, and hero sections to enhance visual quality on the landing page. * Update README and replace landing hero image - Updated the README to reflect the new image caption for the companies list. - Replaced the outdated landing hero image with a new product shot to enhance visual appeal. - Removed the old landing hero image from the repository. * Update landing page images for agents and capabilities - Replaced existing binary images for agents and capabilities on the landing page to improve visual quality and consistency. - Ensured that the new images align with the recent updates to the README and overall landing page design. * Update landing page images for agents and capabilities to enhance visual quality * Refactor AddButton component in multiple sheets to use ComponentProps for better type safety - Updated the AddButton function in create-company-sheet, create-contact-sheet, create-deal-sheet, and add-sso-provider-sheet to accept props of type ComponentProps from the Button component. - This change enhances type safety and allows for more flexible button properties across different sheets. * Refactor TelemetryService to integrate RollupService for telemetry rollups - Replaced FunnelService with RollupService in TelemetryService to handle telemetry rollups. - Implemented a timer to run rollups hourly, enhancing telemetry data collection. - Updated documentation to reflect changes in telemetry rollup processes and clarify the in-process execution without cron dependencies. * Report installs without a cron, and stop double counting them The install count was reading 1 while 20 databases had migrated. Every "Active installs" tile is built on install_daily, which only ever fired from POST /internal/telemetry/rollup — a route that refuses to run without CRON_SECRET. An install that never configures a cron reported nothing at all, however much it was used. TelemetryService now rolls up in-process, on boot and hourly. The existing row lock on install makes all but the first of those a no-op, and it short-circuits before the aggregation runs, so it is still one set of grouped queries per install per day. The route stays, still behind CRON_SECRET, for a platform cron that would rather drive it; nothing depends on it now. Two ways the same event could arrive twice, both of which the hourly timer would have made more frequent: A rollup wrongly read as failed hands the day back and is re-sent. posthog-node does not reject on a failed send, so the client inferred failure from a module-global error counter that any other capture could move. It now enqueues and awaits flush(), which does throw, and treats either signal as a failure — erring toward a re-send, which is free, over consuming a day whose event never left. A milestone sent before it was recorded, so both the boot sweep and the rollup sweep could send the same step. One install sent first_fact_applied six times. The insert is now the claim: of two sweeps exactly one is told it landed the row, and only that one sends. A failed send deletes the row so the step is retried. Both events also carry a deterministic uuid derived from the install and the day (or the step), so a duplicate that does get out is ingested once. Installs and active installs were always safe — PostHog's unique math is per install per day — but the summed agent-usage properties were not. * Derive the dedupe id with SHA-256 in a v8 uuid CodeQL flags a weak algorithm reached by the install identity, and it is right that the two do not belong in one expression. SHA-1 was there only because RFC 4122 defines v5 that way; nothing depends on being a v5, so this is a SHA-256 digest in a v8 uuid, the slot RFC 9562 leaves for a derivation of one's own. * CMP-1 chore: enrich agentic experience * ci: open pull requests, gate titles and promote releases automatically (trycompai#53) * Lewis/contact and currencies (trycompai#56) * Implement fields management features (trycompai#55) * Lewis/dynamic field fix (trycompai#70) * Refactor query prefetching in Companies, Contacts, and Deals pages to… (trycompai#71) * chore: release main (trycompai#72) * feat(api): add microsoft sign-in and outlook mailbox sync (trycompai#73) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore: release release * ci: run release-please on main and document merge order (trycompai#76) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * chore: release main (trycompai#78) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(db): CMP-1 persist durable custom agents (trycompai#67) * feat(agent): CMP-1 add sandboxed builder and runner runtimes (trycompai#60) * refactor(app): CMP-59 harden CRM UI foundations (trycompai#61) * feat(app): CMP-46 add the private agent builder workspace (trycompai#62) * feat(app): CMP-12 review agent drafts before deployment (trycompai#63) * fix(app): CMP-47 consolidate agent builder presentation (trycompai#64) * feat(app): CMP-47 add inline composer context * fix(app): move chat beneath overview in icon rail (trycompai#83) Co-authored-by: grim <75869731+ripgrim@users.noreply.github.com> * fix(ci): tag releases automatically and keep previews off the production schema (trycompai#82) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.4.0 (trycompai#86) * feat(agent): bound agent builder retries and improve chat scrolling (trycompai#89) * fix(app): render agent transcript chronologically with anchored tool results (trycompai#92) Co-authored-by: grim <75869731+ripgrim@users.noreply.github.com> Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> * fix(agent): declare granted write actions in draft access summary (trycompai#93) Co-authored-by: grim <75869731+ripgrim@users.noreply.github.com> * chore(main): release 1.5.0 (trycompai#91) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(api): warn when the deployed schema does not match schema.prisma (trycompai#88) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * CMP-62 chore: add gh-stack skill (trycompai#96) * chore(main): release 1.5.1 (trycompai#97) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(ci): make the release guard reject only genuinely untagged pull requests (trycompai#105) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * fix(ci): stop the auto-titler downgrading a release The titler regenerated the title on every push once it had written one, so a pull request's subject was whatever its *last* commits looked like. trycompai#105 carried the whole website-tracking feature and was retitled `fix(ci)` by its final push, squashed onto main under that subject, and released as a patch whose notes mention none of it. A generated title is now left alone unless it stops being a conventional commit or stops covering the branch, and no title — generated or typed — may release less than the commits behind it: `floor_of` takes the strongest bump on the branch and `generate` raises its proposal to meet it. A branch holding a `feat` cannot ship as a `fix`, and one holding a breaking change cannot ship without the `!`. Over-releasing is the safe direction; losing a feature out of the changelog is not. * feat(tracking): add website tracking with form capture and attribution A first-party script on the marketing site, a collector in the API, and one rule: a form submission becomes a contact. Page views, click labels and first/last-touch attribution hang off that, with a 90-day retention sweep, an hourly contact cap and a per-minute event budget. The work landed in 815a832. The auto-titler had retitled its pull request `fix(ci)` on the last push, so it squashed onto main under that subject and released as a patch whose notes describe only the guard fix. This commit carries no code — it exists so the changelog and the version say what actually shipped. See docs/tracking.md. * chore(main): release 1.6.0 (trycompai#106) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(ci): make a release one pull request instead of two Shipping was a release pull request into `main` and a promotion pull request into `release`, open at the same time, with a warning on the promotion telling you to merge the other one first. Merge them the wrong way round and you shipped untagged code and left the version behind for the next promotion. Nobody should have to hold that rule in their head to deploy. The tag and the code have to travel together, so the release workflow now does it in one step: when release-please cuts the tag it merges that exact commit into `release` through the merges API. One pull request, no order to remember, and the tag is by construction an ancestor of what shipped. `promote.yml` is gone. A conflict is the one case a human still has to see, and it can only mean somebody committed to `release` directly, so it fails the run and says so rather than quietly leaving production behind. Non-releasable commits now wait for the next release rather than riding a promotion, which is the trade: `release` moves when a tag is cut and at no other time. * fix(ci): fall back to the pushed commit when release-please reports no sha * chore(main): release 1.6.1 (trycompai#108) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(db): add peek script for inspecting database contents (trycompai#110) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.7.0 (trycompai#111) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(agent): apply sourced facts to empty fields automatically (trycompai#112) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.8.0 (trycompai#113) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(ci): ship releases by opening a pull request into release (trycompai#114) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.8.1 (trycompai#115) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(agent): fill blank fields on the dispatch tick instead of sign-in (trycompai#117) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.8.2 (trycompai#118) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(agent): stop suggesting a URL that already matches the field (trycompai#120) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.9.0 (trycompai#121) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(tracking): support installing the tracking tag via Google Tag Manager (trycompai#124) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.10.0 (trycompai#126) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(app): copy the tracking snippet for the selected install method (trycompai#128) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.11.0 (trycompai#129) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat: edit a deployed agent, and show what Slack actually granted (CMP-77) (trycompai#109) * chore(main): release 1.12.0 (trycompai#132) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(app): search company dropdowns instead of scrolling them (trycompai#125) * fix(app): show select field values in record tables (trycompai#133) * fix(agent): let the assistant chat read the deal list it is told to use (CMP-77) (trycompai#139) * chore(main): release 1.13.0 (trycompai#136) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * chore: add anti-slop lint rules, dead-code checks and stricter Biome constraints (CMP-80) (trycompai#145) * refactor: clear anti-slop type assertions and conditional object spreads (CMP-81) (trycompai#146) * docs: propose an i18n layer (trycompai#143) * refactor: parse every remaining I/O boundary into a domain type (CMP-82) (trycompai#151) * fix: unblock the test suite and actually install the git hooks (CMP-83) (trycompai#152) * ci: run anti-slop lint in CI and pre-push (CMP-84) (trycompai#153) Co-authored-by: grim <75869731+ripgrim@users.noreply.github.com> * feat: enrichment queue widget (CMP-92) (trycompai#159) * feat(agent): read people from Context.dev instead of RapidAPI (CMP-86) (trycompai#158) Co-authored-by: grim <75869731+ripgrim@users.noreply.github.com> * feat: page the enrichment queue (CMP-92) (trycompai#160) Co-authored-by: grim <75869731+ripgrim@users.noreply.github.com> * chore(main): release 1.14.0 (trycompai#147) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat(agent): scope field backfill tasks to records missing values (trycompai#163) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.15.0 (trycompai#164) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(api): serve openapi.json and bundle swagger deps in function build (trycompai#166) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.15.1 (trycompai#167) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Lewis/openapi json (trycompai#169) * docs(api): explain runtime openapi document and vendoring rules (trycompai#170) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * chore(main): release 1.15.2 (trycompai#171) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(app): prevent url param collision between fields sheet and table filter (trycompai#175) Co-authored-by: Lewis Carhart <lewis@trycomp.ai> * fix: stop a finished enrichment reading as failed (trycompai#173) * chore(main): release 1.15.3 (trycompai#176) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * ci: add Vercel deploy workflow Deploys to Vercel on push to main/release branches. Also supports manual trigger via workflow_dispatch with environment selection (preview/production). Uses secrets: VERCEL_API_KEY, VERCEL_ORG_ID, VERCEL_PROJECT_ID --------- Co-authored-by: Lewis Carhart <lewis@trycomp.ai> Co-authored-by: grim <75869731+ripgrim@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Co-authored-by: Guzman Pintos <37162183+GuzmanPintos@users.noreply.github.com> Co-authored-by: twinprime19 <38123958+twinprime19@users.noreply.github.com> Co-authored-by: Kiro Agent <244629292+kiro-agent@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The changelog below is what will be published as the release notes. Edit the commit subjects, not this PR body — the body is regenerated on every push to main. Merging it tags the release and puts that commit on
release, so it is live — there is nothing else to merge.1.15.3 (2026-08-21)
Fixes
This PR was generated with Release Please. See documentation.