Version Packages#14216
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
e94caaa to
655db81
Compare
655db81 to
735e296
Compare
f378d93 to
6d2f2fa
Compare
b40ac9b to
68967b4
Compare
21bf6ba to
3f7e382
Compare
|
Dependency limit exceeded — report not shown. This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report. Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard. Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account. |
c42f4f9 to
8385658
Compare
cf2f0a8 to
0b55efb
Compare
efd4f57 to
45b7ebe
Compare
9ab3fe1 to
74d460c
Compare
74d460c to
5bd35aa
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@audius/sdk@16.0.0
Major Changes
6bd5c27: Rename the path field on
getNotificationsandgetPlaylistUpdatesfromuserIdtoid, matching the convention used by every/users/{id}/…method. Add an optionaluserIdquery field that carries the requester id for personalization of embeddedrelated.users(e.g.does_current_user_follow).Migration:
The two ids differ only when a manager reads a managed user's notifications; in the normal flow they're the same value. The wire format and server URL are unchanged — only the request type shape was renamed to remove a collision between the path and the new query parameter.
Minor Changes
be0537f: Add an optional
userId?: stringquery parameter to three endpoints so the backend can personalize embedded users inrelated.users/ collection owners (does_current_user_follow, etc.):events.getRemixContestsusers.getContestsByUserplaylists.getPlaylistsNewReleasesWithout this, the endpoints' handlers (
app.getMyId(c)) resolved the requester id from the missing?user_id=query and got0, so embedded user objects came back withdoes_current_user_follow: falsefor everyone. Clients that primed those into a shared cache (e.g. viaprimeRelatedData/primeCollectionData) silently poisoned follow state for the surfaced artists.Existing callers continue to work unchanged — the field is optional. Pass
Id.parse(currentUserId)(or whichever id your app treats as "me") to opt in.Patch Changes
https://anti-abuse-oracle.audius.engineering, replacing the oldhttps://discoveryprovider.audius.cohost in the SDK services config and supporting clients/services.allowedApiKeystoUploadTrackMetadataSchemaso it's preserved when uploading or updating tracks. Previously the strict schema stripped the field, which prevented the "Disallow Streaming via the API" setting from being saved.creatornode2.audius.coandcreatornode3.audius.co.@audius/sdk-legacy@6.0.29
Patch Changes
visitorId, the identity service's fingerprint-based OTP bypass is gone (new devices always require OTP), and the anti-abuse-oracle drops the per-fingerprint device-count scoring and UI section.@audius/sp-actions@1.0.33
Patch Changes
@audius/common@1.5.79
Patch Changes
toSdkGenrein the track adapter filtered out any value not in the canonicalGenreenum and returnedundefined, which then fell back toDEFAULT_GENRE(Electronic) before reaching the SDK. Now any non-empty genre string is passed through unchanged (the SDK upload schema already caps it at 100 chars), so custom genres entered by artists are preserved end-to-end.otaVersionattribute (or"native"when no OTA is applied), so feature flags can be gated on a specific OTA cut in addition to the native binary version.usePrefetchTrackCommentsandusePrefetchTrackPageLineup, hooks that warm a track's comment list and "more by / remixes / you might also like" lineup as early as possible (e.g. on track screen mount) so those sections render from cache instead of starting their own fetch only once they mount. Each keeps a live observer so the warmed data isn't evicted before the section mounts.usePrefetchTrackCommentscan fire from a bare trackId;usePrefetchTrackPageLineupstill depends on the hero track + owner handle but starts the instant those resolve rather than waiting for the mobile screen-ready/animation gate.CONTESTSfeature flag is enabled and the artist hosts at least one remix contest. Previously the desktop and mobile-web profiles always rendered the tab for any artist (ignoring the flag entirely), and the React Native side respected the flag but still showed the tab for artists who don't run any contest — both led to an empty/unreachable destination. Adds a shareduseUserHasRemixContesthook that paginates the global remix-contest list (matchingContestsTab's page cap) and matchesevent.userIdagainst the host. Direct visits to/:handle/contestson a non-qualifying profile fall back to the default tab so the body stays in sync with the (now hidden) tab list.visitorId, the identity service's fingerprint-based OTP bypass is gone (new devices always require OTP), and the anti-abuse-oracle drops the per-fingerprint device-count scoring and UI section.store/lineup:lineupActions,lineupReducer,lineupSelectors,LineupBaseActions,lineupRegistry) from@audius/common. The lineup engine has been fully migrated to tan-query hooks plus the playback slice; these exports had no remaining consumers and were not wired into any store.feed-page:tablocalStorage value is migrated transparently so existing users land on the same tab they had selected.@audius/mobile@1.5.186
Patch Changes
ContestHerowas clipping its scaled cover image withoverflow: 'hidden', so the existing scale + translate over-scroll interpolation could only stretch within the 220px hero box and never bled upward into the over-scroll gap. The clip is removed (mirroringProfileCoverPhoto), and the title/CTA/countdown section gets its own opaque background to cover the downward bleed — same sibling-with-bg patternProfileHeaderuses below the cover photo.iframe { height: 100% }but neither<html>nor<body>had an explicit height, so the iframe collapsed and left a visible gap inside the 16:9 container. Givinghtml, bodyan explicit100%height lets the iframe fill the card as intended.TrackLineuppreviously waited a 100ms debounce before dispatchingloadNextPage, then waited again for the parent'sisFetchingto round-trip back through tanquery before any skeleton rows appeared — so users would scroll to the bottom, see nothing happen, then see late skeletons, then tracks. The threshold is now bumped from 0.5 to a full viewport ahead, the debounce and the duplicateonScrollhandler are removed, and a synchronous local "load triggered" flag flips skeletons on in the same tick the scroll handler fires.useResendRecoveryEmail, ChatUserListScreen usesuseSearchUsersModalinfinite query, track edit/delete flows go throughuseUpdateTrack/useDeleteTrackhooks instead of the saga + confirmer queue.otaVersionattribute (or"native"when no OTA is applied), so feature flags can be gated on a specific OTA cut in addition to the native binary version.CONTESTSfeature flag is enabled and the artist hosts at least one remix contest. Previously the desktop and mobile-web profiles always rendered the tab for any artist (ignoring the flag entirely), and the React Native side respected the flag but still showed the tab for artists who don't run any contest — both led to an empty/unreachable destination. Adds a shareduseUserHasRemixContesthook that paginates the global remix-contest list (matchingContestsTab's page cap) and matchesevent.userIdagainst the host. Direct visits to/:handle/contestson a non-qualifying profile fall back to the default tab so the body stays in sync with the (now hidden) tab list.visitorId, the identity service's fingerprint-based OTP bypass is gone (new devices always require OTP), and the anti-abuse-oracle drops the per-fingerprint device-count scoring and UI section.feed-page:tablocalStorage value is migrated transparently so existing users land on the same tab they had selected.@audius/protocol-dashboard@0.1.19
Patch Changes
@audius/web@1.5.180
Patch Changes
position: relativeon the inner photo div was overriding the CSS module'sposition: absolute, which dropped the photo into the parent flex container alongside the edit button — both flex items competed for space, shrinking the banner below full width.CommentBlocklayout. Previously the badge sat inline next to the username; now the header usesjustifyContent='space-between'with user link + timestamp on the left and the Host badge in aflexShrink: 0wrapper on the right. Applies to both top-level contest comments and nested replies..artistCoverPhotobanner div lacked a positioning context, so the blur overlay'sposition: absolute; inset: 0escaped to the nearest positioned ancestor and bled outside the cover photo banner. Addingposition: relative(andoverflow: hidden) to the banner contains the blur to the intended 136px header.CONTESTSfeature flag is enabled and the artist hosts at least one remix contest. Previously the desktop and mobile-web profiles always rendered the tab for any artist (ignoring the flag entirely), and the React Native side respected the flag but still showed the tab for artists who don't run any contest — both led to an empty/unreachable destination. Adds a shareduseUserHasRemixContesthook that paginates the global remix-contest list (matchingContestsTab's page cap) and matchesevent.userIdagainst the host. Direct visits to/:handle/contestson a non-qualifying profile fall back to the default tab so the body stays in sync with the (now hidden) tab list.visitorId, the identity service's fingerprint-based OTP bypass is gone (new devices always require OTP), and the anti-abuse-oracle drops the per-fingerprint device-count scoring and UI section.feed-page:tablocalStorage value is migrated transparently so existing users land on the same tab they had selected.isFetching(so they only painted after a multi-tick state round-trip), and a per-page skeleton count of justpageSize(4 on Trending, ~480px tall on desktop) that didn't fill the loading window. The threshold is now ~2× the scroll parent's viewport, a synchronous trigger flag renders skeletons on the next frame, and the skeleton count is sized to fill the threshold area so the bottom stays populated even when the user scrolls in faster than the next page can return.