Releases: Emurgo/yoroi-graphql-migration-backend
Releases · Emurgo/yoroi-graphql-migration-backend
1.1.3-pre1
Merge pull request #275 from Emurgo/ruslan/fix-status-check Added safe-navigation to the status check after tx submission
1.1.2
Merge pull request #273 from Emurgo/fix/allow-empty-asset-name-on-ma-…
1.1.0
Breaking change
- Requires cardano-db-sync 6.0.0
Deprecations
- The following endpoints are being renamed (old paths still work for backwards compatibility)
api/getAccountState
->api/account/state
api/getPoolInfo
->api/pool/info
api/getRewardHistory
->api/account/rewardHistory
Internal changes
account/state
endpoint no longer requires running a cardano-node instance locally (now queried fromcardano-db-sync
)
New features
- Allow passing payment keys (encoded as bech32
addr_vkh
to match CIP5) foraddresses/filterUsed
,txs/history
,txs/utxoForAddresses
- Allow bech32 encoding of staking keys (
stake
andstake_test
) foraccount/registrationHistory
,account/state
,account/rewardHistory
,txs/history
- Add reward history endpoint (
account/rewardHistory
) api/account/state
now properly fills therewards
andwithdrawals
fields in the response
Bug fixes
txs/history
endpoint used to return the wrong information for themetadata
field. It now always returnsnull
pending implementation of this field in a future version.api/getRewardHistory
now returns[]
as a default value (instead of an address being omitted from the response if it has never been registered)txs/history
endpoint now supports mid-block pagination. Previously, trying to paginate mid-block (ex: getting block A tx 1 and block A tx 2 in two separate queries) would drop resultstxs/history
now properly returns transactions where the staking key appears in a certificate and none of the input / outputs belong to the user- Fixed broken check for
REFERENCE_BEST_BLOCK_MISMATCH
fortxs/history
- Fixed
type
field intxs/history
(used to always returnshelley
, but now properly returnsbyron
for byron-era transactions)
1.0.0
Initial version