Repository navigation
Version Packages - #14609
Open
github-actions[bot] wants to merge 1 commit into
Open
Version Packages#14609github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
|
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. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 2, 2026 18:26
930e403 to
c645e3e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
October 13, 2026 22:56
692d479 to
fe3a054
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 20, 2026 05:24
fe3a054 to
0255d55
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
October 28, 2026 22:01
2e7aaad to
9a3c389
Compare
dylanjeffers
added a commit
that referenced
this pull request
Nov 7, 2026
…p updates (#14751) ## Problem The desktop app has not updated since Aug 3. Desktop has two update paths, and both need a newer version than the one installed: - **Web update** (`checkForWebUpdate` in `packages/web/src/electron.js`): polls `s3://audius.co/package.json` every minute and only downloads `build-production.tar.gz` when the marker has the same major.minor and a **strictly higher patch**. - **Full app update** (electron-updater): reads `download.audius.co/latest*.yml` and only installs a **higher version**. Nothing bumps `packages/web/package.json` per release. It has been `1.5.180` since Version Packages #14216 (2026-08-03). The open Version Packages PR (#14609) doesn't touch web either, because no changeset names `@audius/web`. Every production approval since then has published version 1.5.180: - `s3://audius.co/package.json` was last written 2026-11-03 and says `1.5.180`. - `latest*.yml` says `1.5.180`, and the Mac build was re-released 2026-11-03 under the same version. So a desktop install on 1.5.180 sees nothing newer and keeps whatever web bundle it installed, anywhere from Aug to Nov. This is also why desktop users were still hitting the old 500 MB upload cap long after the 2 GB change. ## Fix `production-gate` now picks the release version after approval: ``` next = patch + 1 of max(packages/web/package.json, published s3://audius.co/package.json) ``` `web-deploy` and the Mac/Windows/Linux desktop jobs write that version into `packages/web/package.json` and `build-production/package.json` before packaging. That keeps the S3 marker, the web-update tarball, the electron-updater feeds and the app's own `appVersion` on the same number. The Slack messages report it too. Why after approval: runs wait at the gate for days and get approved out of order. A version picked at build time would give every waiting run the same number. Nothing changes on the client. The S3 layout is the same (`packages/web/` prefix in the tar, `package.json` inside `build-production/`). An old client only understands "higher patch", and that's what it gets. ## How existing 1.5.180 installs pick it up The next approved production run publishes **1.5.181** (checked against the live marker: repo 1.5.180, published 1.5.180 → 1.5.181). - Running 1.5.180 apps see the 1.5.181 marker within a minute and download the bundle. The web update banner appears (patch bumps are below `MIN_APP_VERSION`, so it's the soft banner), and accepting it reloads into the current web build. - electron-updater also sees 1.5.181 in `latest*.yml` on next launch, downloads the full app, and installs it on quit. That path is silent for patch bumps. - Every later approval goes to 1.5.182, 1.5.183, and so on, so this can't freeze again. ## Confirmed on a real install On a Mac desktop install from Aug 18: - `/Applications/Audius.app` is 1.5.180. - `~/Library/Application Support/Audius/build-production/package.json` is also 1.5.180, so `getNewestBuildDirectory` keeps loading the bundled Aug 18 build. - The S3 marker is 1.5.180, so `checkForWebUpdate` never fires. - The bundled `app.asar` has none of the flags added after Aug 18 (`track_tile_waveform`, `now_playing_comments`). ## Verify after the next approval 1. `curl -s https://s3.us-west-1.amazonaws.com/audius.co/package.json | jq -r .version` prints `1.5.181`, and the `Pick release version` step in the gate job logs the same number. 2. Leave that 1.5.180 desktop app open for a minute and the web update banner appears. Accept it, then check that `~/Library/Application Support/Audius/build-production/package.json` is 1.5.181. 3. Quit and relaunch, and electron-updater installs the 1.5.181 app. ## Notes - The repo version stays the floor. A manual bump, or a minor bump for a forced full update, still wins over the published marker. - If two runs are approved within minutes of each other, both can pick the same number before either writes the marker. The second tarball then overwrites the first at that version, and clients that already took the first wait one more release. This only matters for near-simultaneous approvals, so I didn't add locking. - The web bundle's embedded version (Optimizely `appVersion`, analytics, the settings page) still comes from the repo `package.json` at build time, because the build runs before the gate. Only the update markers and desktop app versions are stamped. - `actionlint` is clean. I ran the version-pick script locally against the live S3 marker. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
November 12, 2026 18:21
4ad7b46 to
16f710d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 13, 2026 00:28
16f710d to
5bb7d36
Compare
This branch has not been deployed
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@18.0.0
Major Changes
5a1a3a0: Load @solana/web3.js on first use instead of when the SDK is created.
createSdkWithServicesnow creates a lazysolanaClientand the Solana relay,PublicKeySchemaand the program client defaults import @solana/web3.js only when they need it.solanaClient.getConnection(), which resolves to the RPCConnection. Use it instead ofsolanaClient.connection.sdk.services.solanaClient.connectionthrows until the client has loaded (after anyawait solanaClient.<method>()call, includinggetConnection()), and the defaultsolanaClientis no longerinstanceof SolanaClient. AsolanaClientpassed in throughservicesis used as-is.rewardManagerClient.lookupTableis only available once that client has loaded, unlessrewardManagerLookupTableis passed in its config.PublicKeySchema(and schemas built on it, such asMintSchema) now only supports async parsing (parseAsync/safeParseAsync). The SDK's own methods already parse asynchronously.SolanaAddressSchemavalidates the address as base58-encoded 32 bytes without @solana/web3.js. It accepts the same strings as before.Minor Changes
chats.createwith more than one invitee makes a group (grp_id), newchats.leave, andis_grouponUserChat.has_repliedto user chats anduncategorized_unrepliedto the unread-by-category counts. Add anendAdornmentslot toSelectablePill.users.getListenerCitiesfor an artist's top listener citiessdk.services.ethereum.<contract>.abiis only available after that contract has been used, and these services are no longerinstanceoftheir client classes. Also marks the package as side-effect free so bundlers can drop unused exports.tracks.getTrackStemsDownloadUrlfor downloading a track's stems as one zipPatch Changes
2633593: Parse weekly rotation notifications so a response containing one does not fail to load the entire notification list.
6e30f1f: Fix several error-handling bugs:
SolanaRelayWalletAdapter.connect()resetsconnectingwhen fetching the fee payer fails.SolanaRelay.relay()rethrows the original response error when the error body isn't JSON.SolanaClient.buildTransaction()rounds the percentile-based priority fee, which threw on fractional values.4042e05: Load
tus-js-clientand the Nodefile-typepath only when an upload or file type check needs them, and fetch the storage node list on first use instead of when the SDK is created.1408b93: Use @noble/curves for secp256k1 and @noble/ciphers for AES-GCM instead of @noble/secp256k1 and micro-aes-gcm. Chat and email encryption, shared secrets and signatures are byte-for-byte the same.
737c197: When a storage node reports an audio upload as done without its transcode result, poll the next node and fail after two minutes instead of waiting for the 20-minute stall timeout.
de6f379: Define the Ethereum mainnet chain in the SDK instead of importing it from
viem/chains, so bundlers that don't tree-shake CommonJS (like Metro) no longer include viem's full chain list.@audius/harmony@0.6.0
Minor Changes
has_repliedto user chats anduncategorized_unrepliedto the unread-by-category counts. Add anendAdornmentslot toSelectablePill.@audius/sdk-legacy@6.0.31
Patch Changes
@audius/sp-actions@1.0.35
Patch Changes
@audius/protocol-dashboard@0.1.21
Patch Changes