chore: Release v18.0.0 with unstable v16 ExtrinsicMetadata extensions

[lexnv]

[18.0.0] - 2024-11-13

Changed

• v16: ExtrinsicMetadata extensions #86

cc @paritytech/subxt-team

[niklasad1]

Isn't this a breaking change i.e. some public fields of the ExtrinsicMetadata are changed? Or we don't mind because it's hidden behind the unstable feature?

[jsdw]

Yeah it's tough. The "unstable" means we are allowed to break it without caring, but that sort of approach does also mean any crate depending on the unstable feature would start breaking until updated. (eg polkadot-sdk and merkleized-metadata)

[lexnv]

Hmm yep, its a tough call, in the past we had breaking change for unstable versions (ie v15.1 included v15unstable). But since we cut a v17.0 for v16 unstable, I think its fine to do a v18 as well (just to keep consistency with our latest release schedules)

[lexnv]

Testing Done

V16 unstable extrinsics

      "extrinsic": {
        "versions": [
          4,
          5
        ],
        "address_ty": 167,
        "signature_ty": 316,
        "transaction_extensions_by_version": {
          "0": [
            0,
            1,
            2,
            3,
            4,
            5,
            6,
            7,
            8
          ]
        },
        "transaction_extensions": [
          {
            "identifier": "CheckNonZeroSender",
            "ty": 537,
            "implicit": 34
          },
          {
            "identifier": "CheckSpecVersion",
            "ty": 538,
            "implicit": 4
          },
          {
            "identifier": "CheckTxVersion",
            "ty": 539,
            "implicit": 4
          },
          {
            "identifier": "CheckGenesis",
            "ty": 540,
            "implicit": 13
          },
          {
            "identifier": "CheckMortality",
            "ty": 541,
            "implicit": 13
          },
          {
            "identifier": "CheckNonce",
            "ty": 543,
            "implicit": 34
          },
          {
            "identifier": "CheckWeight",
            "ty": 544,
            "implicit": 34
          },
          {
            "identifier": "ChargeAssetTxPayment",
            "ty": 545,
            "implicit": 34
          },
          {
            "identifier": "CheckMetadataHash",
            "ty": 547,
            "implicit": 96
          }
        ]
      },

V15 extrinsics

The call type is removed from v16 because it is identical to the other call enum:

      "outer_enums": {
        // 142 identical to extrinsic call_ty 142
        "call_enum_ty": 142,
        "event_enum_ty": 21,
        "error_enum_ty": 1056
      },

"extrinsic": {
        "version": 4,
        "address_ty": 167,
        "call_ty": 142,
        "signature_ty": 316,
        "extra_ty": 954,
        "signed_extensions": [
          {
            "identifier": "CheckNonZeroSender",
            "ty": 955,
            "additional_signed": 34
          },
          {
            "identifier": "CheckSpecVersion",
            "ty": 956,
            "additional_signed": 4
          },
          {
            "identifier": "CheckTxVersion",
            "ty": 957,
            "additional_signed": 4
          },
          {
            "identifier": "CheckGenesis",
            "ty": 958,
            "additional_signed": 13
          },
          {
            "identifier": "CheckMortality",
            "ty": 959,
            "additional_signed": 13
          },
          {
            "identifier": "CheckNonce",
            "ty": 961,
            "additional_signed": 34
          },
          {
            "identifier": "CheckWeight",
            "ty": 962,
            "additional_signed": 34
          },
          {
            "identifier": "ChargeAssetTxPayment",
            "ty": 963,
            "additional_signed": 34
          },
          {
            "identifier": "CheckMetadataHash",
            "ty": 965,
            "additional_signed": 96
          }
        ]
      },