Remove membersChange24hrPercent by rickyrombo · Pull Request #346 · AudiusProject/api

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo · 2025-08-28T20:01:46Z

Removes the membersChange24hrPercent from the /v1/coins/:mint/insights endpoint.

It's not included in the design anymore and is slowing down the endpoint greatly.

DejayJD

🔪

rickyrombo · 2025-08-28T20:03:32Z

 type MembersStatsRow struct {
-	Members int `json:"members"`
-	Members24hChangePercent float64 `json:"membersChange24hPercent"`
+	Members int `json:"members"`


could we remove this too @faridsalau / @DejayJD ? Or are we using it somewhere? Might be nice to just have this be a birdeye proxy

* origin/main: [API-321] Migrate tests for blast writes (#342) Update query for best selling (#347) Remove membersChange24hrPercent (#346) [QA-2301] Fix blockees req (#345)

## Summary Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from `c5fcacf` (#924) to **`e8586ac`**. **Primary:** go-openaudio **#348** — fixes `playlists.last_added_to` never being written (perpetually NULL), which silently broke the "recently added to" sort and the playlist-update notification. Now set to the block time of the most recent track add (code-only in #348). **Also carried** (main advanced past the baseline): #345/#346 — the **TrackCollaborator** entity. This adds ETL migration **0033**, which `CREATE TABLE IF NOT EXISTS track_collaborators` (a new, empty table) plus one index on it. `core-indexer` runs this vendored image, so the bump is required to ship the fix. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260609013415-e8586ac9ce16` ## Deploy note — migration 0033 is low risk 0033 creates a brand-new empty table + index with `IF NOT EXISTS`. There's no existing data to scan and no `ACCESS EXCLUSIVE` lock on a populated table (unlike the 0031 slug index), so it applies instantly — no pre-build/CONCURRENT step needed. The `last_added_to` fix itself is code-only (no migration). ## Test plan - [x] `go mod tidy` — only go.mod/go.sum changed - [x] `go build ./...` passes - [x] resolved module contains the `last_added_to` writes (`LastAddedTo` in playlist_row.go) and migration `0033` - [ ] Post-deploy: migration version 33 applied clean; creating/editing a playlist populates `last_added_to`, and a rename preserves it 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…hboard merge (#932) Phase 2 of collaborative tracks (the api slice). Consumes the ETL `TrackCollaborator` entity (go-openaudio #345 / #346) and surfaces it through the API. **Ships inert** — nothing emits the on-chain invites/accepts until the client work lands, so this is safe to deploy dark. ### Recap A track owner tags collaborator artists (in track metadata); each must **accept** (pending → accepted). Accepted collaborators get the track on their profile and merged into their dashboard analytics. Scope is **display + analytics only** — no revenue split, no edit rights. ### What's here **Table + notifications** - `ddl/migrations/0220_track_collaborators.sql` mirrors the ETL table with `CREATE TABLE IF NOT EXISTS` (byte-compatible with go-openaudio migration 0033). It runs in the `migrations/` pass, *before* `functions/`, so the trigger always has its table regardless of ETL-indexer timing. - `ddl/functions/handle_track_collaborator.sql` — a trigger modeled on `handle_manager_request.sql`: a new pending invite notifies the **collaborator** (`track_collaborator_invite`); a transition to accepted notifies the **inviter/owner** (`track_collaborator_accept`). - Both types added to the notifications request whitelist. **Read path** - Track responses now carry a `collaborators` array (accepted only), bulk-resolved in a single indexed query folded into the existing user fetch — no N+1. - `GET /users/:id/tracks` UNIONs the user's owned tracks with tracks they've accepted a credit on, preserving sort/pagination. The artist-pick pin now references the **profile** user, so a collaborator's track is never spuriously pinned by the *owner's* pick. **Dashboard** - `GET /users/:id/listen_counts_monthly` widens to include co-owned tracks (engagement analytics). - The dashboard track table is powered by `GET /users/:id/tracks`, so it merges automatically. - **Sales/revenue intentionally left scoped to the seller** — collaborators don't share revenue (per the no-split scope). Easy to widen later if desired; flagging for a decision. **New endpoint** - `GET /users/:id/collaboration_invites?status=pending|accepted|rejected` lists a user's invites/credits with the inviter embedded as a user object (mirrors `/managers`). Powers the client's accept/decline UX. ### Performance - The collaborators embed is one extra indexed query per track-list response (returns 0 rows for the common no-collaborator case; backed by the `track_collaborators` PK). The profile UNION uses the covering `(collaborator_user_id, status, track_id)` index. - Every track response now includes a `collaborators` field (empty array when none) — a small, constant payload addition. ### Tests `api/v1_track_collaborators_test.go`: collaborators embedded on track responses, accepted credit appears on the collaborator's profile, pending invite stays hidden, the invites endpoint (status filter + validation), and the notification trigger firing for both invite and accept. Full `./api/` package suite passes. > Note: `sql/01_schema.sql` carries the table + trigger inline so fresh/test DBs have them; `make test-schema` (which needs an exclusive local pg) will canonicalize the placement on the next regen. ### Next Phase 3 (apps): SDK methods, upload tagging UI, push + in-app notifications, comma-separated artist line, dashboard — web + mobile, behind a flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

rickyrombo added 2 commits August 28, 2025 12:59

Remove membersChange24hrPercent
a4b407c

remove from swaggerg
8cd3018

rickyrombo requested review from DejayJD, dylanjeffers and faridsalau August 28, 2025 20:01

DejayJD approved these changes Aug 28, 2025
View reviewed changes

faridsalau approved these changes Aug 28, 2025
View reviewed changes

rickyrombo commented Aug 28, 2025
View reviewed changes

fix test
1ddcc0b

rickyrombo merged commit fdcdfca into mainAug 28, 2025
5 checks passed

rickyrombo deleted the mjp-insights-faster branch August 28, 2025 20:13

This was referenced Jun 9, 2026
feat(api): collaborative tracks — notifications, embed, profile + dashboard merge #932
Merged
chore(api): bump etl for playlists.last_added_to (#348) #933
Merged

Uh oh!

Conversation

rickyrombo commented Aug 28, 2025

Uh oh!

DejayJD left a comment

Choose a reason for hiding this comment

Uh oh!

rickyromboAug 28, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

rickyrombo commented Aug 28, 2025

Uh oh!

DejayJD left a comment

Choose a reason for hiding this comment

Uh oh!

rickyromboAug 28, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

rickyrombo commented Aug 28, 2025

Uh oh!

DejayJD left a comment

Choose a reason for hiding this comment

Uh oh!

rickyromboAug 28, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

rickyrombo commented Aug 28, 2025

Uh oh!

DejayJD left a comment

Choose a reason for hiding this comment

Uh oh!

rickyromboAug 28, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

rickyrombo commented Aug 28, 2025

Uh oh!