chore(sdks): Version Packages - #681
Merged
Merged
Conversation
marktoda
approved these changes
Aug 5, 2026
plondon
approved these changes
Aug 5, 2026
Contributor
Author
|
● Reviewed · 2026-08-05 21:56 UTC · view run ↗
Changesets release PR bumping |
Graphite Automations"Request reviewers once CI passes on sdks monorepo" took an action on this PR • (08/05/26)3 reviewers were added to this PR based on Siyu Jiang (See-You John)'s automation. |
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
@uniswap/liquidity-launcher-sdk@1.9.0
Minor Changes
bc01784: Quick-launch preset: state the graduation pool's tick spacing, which the 2026-08-05 chain-4663 full redeploy changed on-chain from 50 to 25 without any SDK constant describing it.
QUICK_LAUNCH_POOL_TICK_SPACING(new) →25. The value the launch flow passes inMigratorParameters.poolParameterssince the redeploy — deliberately NOT the genericfeeToTickSpacingderivation, which yields 50 for the 2500 fee tier. Evidence: the post-redeployInitializecensus on chain 4663 shows every quick-launch graduation pool minted at spacing 25 (295 pools in the redeploy's first day, zero new pools at 50).QUICK_LAUNCH_ALLOWED_POOL_TICK_SPACINGS(new) →[25, 50]. The append-only grandfather set (same shape asQUICK_LAUNCH_ALLOWED_GRADUATION_FDV_USD): pools are permanent, so routing/discovery consumers deriving a token's candidate launch pools must race a(QUICK_LAUNCH_LP_FEE, spacing)key for every entry — the token address alone cannot say which generation minted its pool. This is the constant rh-cca'sLAUNCH_POOL_TIERS-style routing should consume instead of hand-maintained literals (Uniswap/universe#38608 shipped the interim literal).QUICK_LAUNCH_PRESET.lp.tickSpacing(new field) →QUICK_LAUNCH_POOL_TICK_SPACING, beside the existinglp.fee.feeToTickSpacingitself is unchanged — it remains the generic v3-canonical/interface derivation used for validation; the preset now states the observed on-chain value where the launch flow no longer follows that formula.isQuickLaunchclassification is unaffected (it never matched on the pool key).