Conversation
guanbinrui
force-pushed
the
develop
branch
2 times, most recently
from
March 3, 2023 15:44
43c6e4c to
1931e81
Compare
guanbinrui
force-pushed
the
develop
branch
2 times, most recently
from
November 6, 2023 17:25
621ed43 to
ec19101
Compare
* chore: remove avatar and recommend feature * fixup! chore: remove avatar and recommend feature
Co-authored-by: Jack-Works <Jack-Works@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* feat(redpacket): cleanup unused code in SolanaRedPacketCard - remove unused imports and variables - simplify dependencies in claimedShareText - refine callback dependencies * refactor(redpacket): remove unused variables and optimize hook dependencies
* chore: update key name * refactor: rm unnecessary try-catch * fix: cspell * chore: ignore patches on cspell
…unused NextID binding proof helper (#12278)
Signed-off-by: yajianggroup <yajianggroup@outlook.com>
* chore: bump version to 2.34.1 * chore: migrate load storage provider (#12266) * fix: linter * chore: update key name (#12267) * chore: update key name * refactor: rm unnecessary try-catch * fix: cspell * chore: ignore patches on cspell * fix: LOAD_NETWORK_ENV * chore: migrate load storage provider * fix: conditional legacy gateway, .env, 30MB limit * fix: lint & format * refactor: file service * fix: u flag * chore: hardcode key * fix: eslint * fix: linter --------- Co-authored-by: xylophonez <69069725+xylophonez@users.noreply.github.com> Co-authored-by: guanbinrui <guanbinrui@users.noreply.github.com> Co-authored-by: Xylophone <xylophonezygote@gmail.com> Co-authored-by: Jack-Works <Jack-Works@users.noreply.github.com>
* feat(wallet): mf-6735 add privy wallet option and update wallet startup UI * feat(privy-wallet): mf-6735 integrate privy wallet with firefly auth and update popup UI * feat: mf-6735 integrate privy wallet support and x account login - add Privy provider and API integration for wallet management - support Privy wallets in MaskWalletProvider and wallet hooks - enable login and wallet creation via X (Twitter) account with auth timeout handling - adapt transaction requests to handle Privy wallet signing - update cspell dictionaries and ignore reg exps for privy related domains - adjust UI components for importing/creating wallets with Privy option * feat(privy): mf-6735 integrate privy auth, providers and chain configs * feat(shared): mf-6735 add privy setup provider to UI roots wrap application root providers and modals with PrivySetupProvider and mount PrivySetup where needed. * fixup! feat(shared): mf-6735 add privy setup provider to UI roots * fix: follow up reviews * fix: revert to jsxCompose * fix: follow up reviews * fix: linter --------- Co-authored-by: swkatmask <swkatmask@users.noreply.github.com>
* fix: mf-6823 stop relying on thirdweb free-tier rpc for BSC and Fantom * fix: mf-6821 drop OnFinality from Metis rpc list (needs api key, serves stale blocks) * fix: replace dead public rpc presets for Ethereum and Polygon * fix: linter --------- Co-authored-by: swkatmask <swkatmask@users.noreply.github.com>
… cards (#12478) * fix: mf-6831 fix dark mode text colors on web3 profile and red packet cards * fix: mf-6831 fix horizontal padding of contract items in coin metadata menu
The IPFS provider of the Web3 File Service uploaded through a hardcoded Infura project (ipfs.infura.io:5001) and linked files via the mask.infura-ipfs.io gateway. Infura deprecated its IPFS product, so both upload and download are permanently dead. Remove the upload UI entry, the file browser tab, the Worker implementation (with its dead Infura credentials) and the now-unused kubo-rpc-client dependency. Keep the read path intact: Provider.IPFS enum members, the gateway entry and the schema enum values stay so historical posts with IPFS files still render their file card. Drop the IPFS mention from the terms page.
#12490) Tag pushes and branch pushes for the same commit share the same sha, causing them to fall into the same concurrency group and cancel each other. This dropped the tag-triggered run (and its release-publish step) for v2.36.0 when the released-branch push for the same commit arrived a few seconds later. Claude-Session: https://claude.ai/code/session_01QKMxkCAVGzSyvaCghCNDSq Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
- prepare-release.yml: manually dispatched, lets you pick patch/minor/major, bumps package.json accordingly, commits, and opens a "[Release] New release X.Y.Z (type)" PR. Patch targets `released` directly (matching the existing hotfix/* convention); minor/major target `develop` (matching the existing release/* convention). - tag-release.yml: when a "[Release] New release" PR merges into `released`, automatically creates and pushes the `vX.Y.Z` tag, which triggers the existing Compile workflow's release-publish step. Promoting develop to released for minor/major releases is still a manual step outside this automation. Claude-Session: https://claude.ai/code/session_01QKMxkCAVGzSyvaCghCNDSq Co-authored-by: Claude Sonnet 5 <noreply@anthropic.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
13 participants
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.
Description
Closes # (NO_ISSUE)
Type of change
Previews
Checklist
console.logsIf this PR depends on external APIs:
chrome-extension://[id]moz-extension://[id]