Release v16 #256
Merged
Release v16 #256
Conversation
This file contains 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
BREAKING CHANGE: 🧨 Since some of the settlements related entities have been removed and new ones have been added, this will require a full resync. Following are the breaking changes: - Entities `Settlement`, `MediatorAffirmation`, `IdentityInstructions` have been removed - Changes in `Venue` entity 1. New attribute `signers` has been added to track all the allowed signers associated with them 2. New derived field `instructions: [Instruction]!` has been added to track instruction info associated a Venue - Adds new enum `InstructionTypeEnum` to track instruction type - Changes in `Instruction` entity 1. `eventId`, `eventIdx` have been removed 2. `settlementType: String!` has been modified to `type: InstructionTypeEnum!` 3. `endAfterBlock: Int` has been added to track block after which `SettleManual` type instructions can be executed 4. `mediators: [String!]!` has been added to track list of mediators for an instruction 5. New derived fields namely - `parties: [InstructionParty]!`, `affirmations: [InstructionAffirmation]!`, `events: [InstructionEvent]!` have been added to query more information about an instruction - Changes in `Leg` entity 1. Attribute `settlement: Settlement` has been removed 2. Attribute `instruction` is now non-null 3. The `from` and `to` part of the legs have been split separately into identity and portfolio number to support off chain legs. The new attributes are `from: String!`, `fromPortfolio: number`, `to: String!`, `toPortfolio: number` - Following new entities have been added: 1. `InstructionParty` - to track all the DIDs associated with an instruction. 2. `InstructionAffirmation`- to track all the affirmations received for an instruction 3. `OffChainReceipt` - to track all the receipts used in affirming off chain legs 4. `InstructionEvent` - to track all the event associated with an instruction. This will give a clear picture about the lifetime of an instruction on how it got created, to affirming, to execution
A new attribtue `failureReason` has been added to `Instruction` entity which stores the error type and details depicting why the instruction failed.
BREAKING CHANGE: 🧨 Changes to support 7.x chain: - New module `electionprovidermultiphase` has been added to `ModuleIdEnum` - Following new events have been added to `EventIdEnum`: `MultiSigAddedAdmin`, `MultiSigRemovedAdmin`, `MultiSigRemovedPayingDid`, `MultiSigSignersAuthorized`, `MultiSigSignersRemoved`, `MultiSigSignersRequiredChanged`, `ProposalApprovalVote`, `TickerLinkedToAsset`, `Chilled`, `EraPaid`, `ForceEra`, `Kicked`, `PayoutStarted`, `SlashReported`, `StakersElected`, `ValidatorPrefsSet`, `ElectionFailed`, `ElectionFinalized`, `PhaseTransitioned`, `Rewarded`, `Slashed`. - Following new extrinsics have been added to `CallIdEnum`: `add_admin`, `add_multisig_signers`, `add_multisig_signers_via_admin`, `approve`, `approve_join_identity`, `change_sigs_required_via_admin`, `create_proposal`, `join_identity`, `reject`, `remove_admin_via_admin`, `remove_multisig_signers_via_admin`, `remove_multisig_signers`, `remove_payer`, `remove_payer_via_payer`, `chill_other`, `force_apply_min_commission`, `kick`, `set_min_commission`, `set_staking_configs`, `register_unique_ticker`, `pre_approve_asset`, `exempt_asset_affirmation`, `remove_asset_affirmation_exemption`, `remove_asset_pre_approval`, `link_ticker_to_asset_id`, `governance_fallback`, `set_emergency_election_result`, `set_minimum_untrusted_score`, `submit`, `sumbit_unsigned`. - New handlers have been added to track the following events: `TickerLinkedToAsset`, `MultiSigAdminAdded`, `MultiSigRemovedAdmin`, `MultiSigSignersAuthorized`, `MultiSigSignersRemoved`, `ProposalApprovalVote` - ID of the `Asset` entity is the new Asset ID generated from chain 7.0.0 chain. For older chains, legacy ticker format is used to generate the ID. All referencing entities will now be tracking this ID for any given Asset. To keep the old reference of ticker, new ticker attributes have been added to some entities where `assetId` was referenced as `string` - `ticker` attribute of `Asset` entity is now optional.
BREAKING CHANGE: 🧨 Changes to support ticker fields - - A new attribute `raisingTicker` of type string has been added to `Sto` entity. This will track ticker value for the raising Asset associated with an Sto. - `ticker: String` attribute of the `ClaimScope` entity has been replaced by `asset: Asset` to have a mapping to asset entity. - `AssetPendingOwnershipTransfer` entity has been removed
BREAKING CHANGE: 🧨 New attributes `raisingAssetId` and `offeringAssetId` of type string have been added to the `Investment` entity to track the asset ID for the respective type of assets (raising and offering).
BREAKING CHANGE: 🧨 New attribute `assetId` has been added to `Scope` json to track the ID of the asset for `Asset` scope type
BREAKING CHANGE: 🧨 Since 7.x chain, Instruction can be created without specifying a venue. To support that `venue` attribute in `Instruction` entity has been made optional.
BREAKING CHANGE: 🧨 Changes to support multisig with 7.x chain - A new `MultiSigAdmin` entity has been added to track admins for a multisig. This also results in a new derived attribute `admins` to be added tot `MultiSig` entity. - New `Approved` status has been added to `MultiSigProposalStatusEnum` - Both `creator` and `creatorAccount` fields in `MultiSigProposal` are now optional.
when a multiSig signer changes their vote, the vote record will now be updated instead of inserting a second vote. Proposal approval/rejection counts will now be decremented in this case
polymath-eric
requested review from
VictorVicente,
prashantasdeveloper and
sansan
as code owners
|
VictorVicente
approved these changes
Sep 30, 2024
|
/fast-forward |
|
🎉 This PR is included in version 16.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Description
Release v16 of SubQuery. This version includes support for 7.0 chains and must be upgraded to before the chain upgrades (expected Nov 2024).
This version requires a resync and has breaking changes in settlement queries. Any application using the Polymesh SDK should be upgraded to a version newer than v24.8.0. Alternatively SDK v23..3.1 has supported backported if a breaking update isn't immediately suitable for you.
Breaking Changes
JIRA Link
Checklist