Version Packages#14216
Open
github-actions[bot] wants to merge 1 commit intomainfrom
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
e94caaa to
655db81
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
655db81 to
735e296
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
f378d93 to
6d2f2fa
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
9 times, most recently
from
d88462b to
f0f9838
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
f0f9838 to
501f907
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-legacy@6.0.29
Patch Changes
@audius/sdk@15.3.2
Patch Changes
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.@audius/sp-actions@1.0.33
Patch Changes
@audius/common@1.5.79
Patch Changes
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.@audius/mobile@1.5.180
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.@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..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.