release: v1.15.3 - #177
Merged
Merged
Conversation
…filter (#175) Co-authored-by: Lewis Carhart <lewis@trycomp.ai>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@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
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.
Puts v1.15.3 on
release, which is the branch production deploys from. Opened by the Release workflow.Summary by cubic
Release v1.15.3: fixes URL param collisions in the app and makes enrichment status resilient to late/foreign task writes.
Old: the fields sheet used the query param "fields", which collided with table field filters; New: the fields sheet uses dedicated keys "manageFields" and "manageField", with a central
SEARCH_PARAMregistry; Side effect: deep links using "fields=" must be updated.Old: completed enrichment could later read as failed when a different task wrote status (or when a late run arrived); New: status writes are guarded so only owning tasks can change them, and
COMPLETEhandling respects task timing; Side effect: API methods report whether a new task was actually queued.API and app
AgentTriggerService.companyRequestedandcontactCreatednow return boolean (queued or already present).companies.research,companies.enrich, andcontacts.enrichreturnqueued: boolean. Clients must handlefalse(no-op) and only set PENDING on true; UI toasts updated accordingly.apps/app/lib/search-param-keys.tsand applies them across the app to prevent collisions (record sheet, quick switcher, overview scope, list tables). Update any saved links: "…&fields=company" → "…&manageFields=company".Agent and reliability
COMPLETEstampsenrichedAteven on rechecks and ignores stale completions when a newer request exists.Test infra
packages/db/scripts/test-db.tsrebuilds the test database if drift or foreign migrations are detected (or when run with--reset). Docs updated indocs/setup.md.Written for commit 3c3e07a. Summary will update on new commits.