Released: 2.0.0-beta.3
- feat: use latest blockhash and allow as param for exchange method
- fix: do not assume tx is mutated on sign
- fix: cykura swapAccountMetas to be computed instead cached

Released: 2.0.0-beta.4
- fix: wsol related swap wrapping lesser sol that is needed
- fix: slight improvement to pubkey generation
- feat: added awaiter to onTransaction, it's a Promise which would resolve when a transaction is confirmed

Release: 3.0.0-beta.0
- feat: jup4 program which include atomic swap, and new integrations such as meteora, invariant and goosefx
- feat: the default getMultipleAccounts now use base64+zstd to reduce payload
- breaking: slippage changed to slippageBps, which slippageBps = Math.ceil(slippage / 100)
- breaking: routeInfo now return slippageBps which is used for swap instruction
- breaking: removed token ledger


Example migration: https://github.com/jup-ag/jupiter-core-example/commit/1f6967e46736b52ba9b4d7a85f91d2628e3d0e26

Release: 3.0.0-beta.1
- fix: split trade amm from combing amms that exceed tx size
- feat: enforceSingleTx option, will exclude routes which might return more than 1 tx
- fix: goosefx memory leak and update logic
- fix: to not compute on 0 amount internally

Release: 3.0.0-beta.2
- fix: esm build
- feat: added balansol to jupiter
- fix: meteora depeg account is not updated properly
- fix: optimization in updating accounts in amms

Release: 3.0.0-beta.5 (skip to .5)
- feat: dradex integration
- fix: add computebudget by default
- fix: goosefx panic error on some quotes
- feat: add ammsToExclude to Jupiter.load

Example usage of ammsToExclude, it’s fully typed so it’s better to use with typescript:

Jupiter.load({
ammsToExclude: {
Raydium: true,
GooseFX: true
}
})

To not consider Raydium and GooseFX when computing and fetching.

Everyone, we are removing Serum from jup.ag and recommend sdk integrators remove Serum for the time being. There are questions on who has the program update authority key on Serum. Given the situation at FTX, we think it’s safer to remove Serum.

You can exclude Serum using ammsToExclude.

We will continue to look into the situation and will update people here if we learn more.

Release: 3.0.0-beta.7
- fix: handle raydium Swap status, which cause raydium not to be showed up on Jupiter
- fix: ammsToExclude now default to not include Serum and GooseFX

relesae: 3.0.0-beta.8
- fix: SplTokenSwapAmm feePct showing NaN
- feat: new integration Lifinity v2
- feat: new integration Raydium clmm (we recommend to turn this off first, there’s 2 pools that is unswappable, we have contacted Raydium about it)
- feat: new integration Openbook

jup.ag now show Lifinity v2 and Openbook

Behind the scene updates:
- Raydium is transistioning some of their pools to Openbook and might have cause some errors in the Jupiter SDK. Just restart it, it should be fine, expect more of these errors in coming days.
- Lifinity did an updated to their oracles. Also a restart should fix it.

release: 3.0.0-beta.9

core
- fix: add raydiumclmm status check
- feat: new integration Crema
- feat: new integration MarcoPolo
- fix: match openbook and raydium together
- chore: remove unwanted sdk from installation
- fix: add freeze trade status detection to lifinity
- fix: lifinity now require setup transaction

react-hook
- feat: use api for quote and swap (migration)
- fix: support platformFeeAndAccounts in react-hook
- fix: add support to handle error from api

release: 3.0.0-beta.10
- fix: crema swaps on low liquidity
- fix: openbook price impact bug that break quote on certain market
- fix: update dradex sdk

react-hook
- fix: platform fee not applied correctly

next release will be v4, will release in a bit

release: 4.0.0-beta.0
- feat: versioned transaction that utilize address lookup table.
- feat: 3 hops swap
- fix: platform fee in all kinds of routes

Breaking changes:
- transaction returned in VersionedTransaciton format, along with its addressLookupTableAccounts for composability
- only swapTransaction will be returned now, there is no more setupTransaction and cleanupTransaction
- enforceSingleTx changed to asLegacyTransaction to return legacy transaction format, but only involve limited amms

v4 API is using the version now: https://docs.jup.ag/integrating-jupiter/backend-bot-integration/using-the-api

release: 4.0.0-beta.1
- fix: swap instruction using wrong inamount when hopping
- fix: update whirlpool to latest sdk
- fix: internal input route segment for 3 hops

release: 4.0.0-beta.2 || release: 3.0.0-beta.12
- fix: transaction fee calculation

release: 4.0.0-beta.3 || release: 3.0.0-beta.13
- fix: signature fee calculation

release 4.0.0-beta.4
- fix: consider sol creation for minimum fee calculation

release 4.0.0-beta.5
- feat: added computeUnitPriceMicroLamports in exchange method

release: 4.0.0-beta.6
- fix: split trade not using ALT
- feat: add swapMode in react-hook

release: 4.0.0-beta.7
- fix: update raydium clmm library that check on liquidity requirement on quoting
- fix: react-hook not correcting set wrapUnwrapSOL when querying a transaction's balance changes.

release: 3.0.0-beta.15
- fix: backport whirlpool fix to v3