Taquito v19.0.0

Disclaimer
You might have noticed that we jumped versions from v17.5.0 to v19.0.0 (no v18). We do this as an effort to be in parallel with the current Octez version.

• Oxford - v18
• Oxford2 - v19

Taquito v19 supports Oxford2, and not the previously named Oxford protocol.

Potential Breaking Changes:
Oxford2 comes with quite a few breaking changes, please make sure to update your projects accordingly.

Oxford2 changes:

• Removed transactional rollups (tx rollup) references in Taquito #2650
• Removed origination proof from smart rollups #2597
• Updated all references of endorsement into attestation for Oxford2 #2599
• @taquito/rpc - Updated RPC types for Oxford2 compatibility #2596

Summary

New Features

• @taquito/local-forging - Added new property whitelist in smart rollup origination operation #2776

19.0.0-beta-RC.0

Disclaimer
You might have noticed that we jumped versions from v17.5.0 to v19.0.0 (no v18). We do this as an effort to be in parallel with the current Octez version.

• Oxford - v18
• Oxford2 - v19

Taquito v19 supports Oxford2, and not the previously named Oxford protocol.

Potential Breaking Changes:
Oxford2 comes with quite a few breaking changes, please make sure to update your projects accordingly.

Oxford2 changes:

• Removed transactional rollups (tx rollup) references in Taquito #2650
• Removed origination proof from smart rollups #2597
• Updated all references of endorsement into attestation for Oxford2 #2599
• @taquito/rpc - Updated RPC types for Oxford2 compatibility #2596

Summary

New Features

• @taquito/local-forging - Added new property whitelist in smart rollup origination operation #2776

Taquito v17.5.2

Hotfix

• @taquito/beacon-wallet - The previous version updated Beacon to v4.1.0, which enabled the use of TzSafe wallet from Beacon. Some early adopters that tried to use abstracted accounts from TzSafe were having issues with Taquito due to return types. This hotfix added a workaround so that abstracted account users are unblocked. Further support for abstracted accounts will be discussed and planned for a future release.
• @taquito/beacon-wallet - Deprecated the method getPK() in favour of pk member method.

Taquito v17.5.1

Dependency Update

• Updated Beacon dependencies to v4.1.0 which includes new features such as Proof of Event as well as updates to WalletConnect 2 support. For more detailed information in regards to the release, please refer to Beacon's release notes

Taquito 17.5.0

Important Note:
In this version, we replaced instances of Axios in favour of Fetch.

We are not expecting any breaking changes, but if there are any issues that you see regarding this, please reach out to the Taquito team.

Summary

New Features

• @taquito/taquito - Expose and publicly smartContractAbstractionSemantic #2534

Improvement

• @taquito/http-utils - Removed Axios as a dependency of Taquito in favour of fetch/node-fetch #2461

Documentation

• Updated RPC nodes on the website [PR#2732](#2732
• Updated Michelson encoder documentation to reference generateSchema instead of the outdated extractSchema #2630
• Added a Taquito Chatbot assistant for the Taquito website to help answer user questions #2684

Internals

• Removed archive node, and references to it in Taquito PR#2743
• Updated Sass, Lerna, and Firebase versions PR#2749
• Updated integration tests to increase speed and reliability #2741

@taquito/http-utils - Removed Axios in favour of fetch

The taquito/http-utils is responsible for handling all HTTP incoming and outgoing HTTP requests in Taquito. It utilized Axios as a main dependency to handle requests coming in and out of Taquito.

Now that browsers and Node have supported fetch natively, it makes more sense for us to move towards it.

Axios came with quite a large dependency tree, as well as multiple workarounds we needed to include for it to work properly (i.e. the axios-fetch-adapter)

With this change we hope for a more stable HTTP handler in Taquito while reducing the package size at the same time.

Taquito v17.4.0

Potential Breaking Changes :
We have updated various dependencies to the latest version in this release. Please update and test our packages for compatibility. We encourage all users to get in touch with the Taquito team if you encounter any unexpected behaviours and/or side effects.

We also strongly encourage users to migrate to Node v18 for increased stability.

Summary

Documentation

• Updated docs on flattening nested Michelson type pairs and unions #2458 #2328
• Added docs to obtain operation hash before injecting an operation #2550
• Added details of FA2 contract entrypoint balance_of param #2719
• Updated Wallet API docs to include examples on subscribing to events emitted by Beacon #2707
• Updated the Taquito test dApp to output events #2707

Internals

• Updated various dependencies PR#2693 PR#2720
• Added detectOpenHandles argument when running Flextesa integration tests as temporary workaround to Jest throwing circular JSON errors PR#2721

Taquito v17.3.2

Summary

• Updated Beacon version to v4.0.12

Documentation

• Updated website documentation to group sections by logical order instead of alphabetical #2665
• Added detail for getBalance() method documentation that it returns balances in mutez #2495

Internals

• Minor typo fix on variable name in RpcEstimateProvider PR#2669
• Added @taquito/core as an explicit dependency on other packages PR#2673

Taquito v18.0.0-RC.0

Breaking Changes: (if applicable)

• @taquito/rpc - Removed RPC method getOriginationProof() #2597

  • Batch API method withSmartRollupOriginate() now no longer needs originationProof as a parameter
  • Contract API method smartRollupOriginate() now no longer needs originationProof as a parameter

• @taquito/local-forging

  • now supports attestation instead of endorsement. #2599
  • removed support of set_deposit_limit operation #2646

• @taquito/rpc - Updated protocol constants in Taquito to support Oxford changes #2594

Summary

Oxford Support

• @taquito/rpc - Updated RPC endpoints' return types for getDelegates() and getConstants() #2596
• @taquito/rpc - RPC endpoints getBlock, preapplyOperations, runOperation, simulateOperation, getBlockMetadata now support RPCOptions of { version: 0 | 1 } (0 returns endorsement; 1 returns attestation) #2596
• @taquito/rpc - RPC endopintsgetPendingOperations now support RPCOptions of {version: 1 | 2 } (1 returns applied & endorsement; 2 returns validated & attestation) #2596
• @taquito/rpc - Removed RPC endpoint of getTxRollupInbox() and getTxRollupState() #2596
• @taquito/local-forging - removed forging support for set_deposit_limit operation #2646

Internals

• Updated integration test configs to support protocol Oxford PR#2632
• Removed remaining tx_rollup references from Taquito #2650
• Added timelock test case to our localForger tests #2653
• Added @taquito/core as explicit dependency in all package.json PR#2673

Taquito v17.3.1

Summary

• This is a patch release to upgrade @airgap/beacon-sdk and @airgap/beacon-dapp packages to v4.0.10 PR#2649
• Updating license to Apache-2.0 in package.json files PR#2636
• Updated the ledger dependencies PR#2645
• Applied dependency upgrades in website suggested by dependabot PR#2645

Taquito v17.3.0

A change in Licensing:
Taquito has moved from MIT to Apache 2.0.

Potential Breaking Changes:

• Previously, an OrToken's EncodeObject method would accept an object with multiple fields. It now only accepts an object with a single field.
• The generateSchema method in an OrToken with nested OrTokens (as well as ExtractSchema) would generate a schema object that was misleading and did not match what Execute created or EncodeObject accepted. This is now fixed and the behavior is consistent across all methods.
• OrToken.Execute() used to throw OrTokenDecodingError in case of failure, but now will throw OrValidationError

Summary

New Features

• @taquito/michelson-encoder - The OrToken's EncodeObject method now only accepts an object with a single field #2544

Bug Fixes

• @taquito/michelson-encoder - A nested PairToken with a mix of fields with annots and fields without annots could generate the wrong javascript object with Execute #2540
• @taquito/michelson-encoder - the generateSchema method in a nested OrToken now generates a schema that is consistent with Execute and EncodeObject #2543

const schema = {
    prim: 'pair',
    args: [
      {
        prim: 'pair',
        args: [
          {
            prim: 'pair',
            args: [{ prim: 'int' }, { prim: 'int' }],
            annots: ['%A3'],
          },
          { prim: 'int' },
        ],
      },
      { prim: 'bool' },
    ],
  };

  const michelineJson = {
    prim: 'Pair',
    args: [
      {
        prim: 'Pair',
        args: [{ prim: 'Pair', args: [{ int: '11' }, { int: '22' }] }, { int: '33' }],
      },
      { prim: 'True' },
    ],
  };
  const javaScriptObject = new Schema(schema).Execute(michelineJson);

Previously, this javaScriptObject would be equal to:

{
    2: true,
    A3: {
      0: 11,
      1: 22,
    },
}

But now it returns:

{
    1: 33,
    2: true,
    A3: {
      0: 11,
      1: 22,
    },
}

Internals

• integration-tests config improvement #2163
• update RPC urls to align with the updated infrastructure PR#2576 #2633

@taquito/michelson-encoder - Validate that an OrToken's EncodeObject method only accepts an object with a single field

Previously, an OrToken's EncodeObject method would accept an object with multiple fields. It now only accepts an object with a single field.

    const token = createToken({
        prim: 'or',
        args: [{ prim: 'int' }, { prim: 'string' }], annots: []
        }, 0) as OrToken;
    const javascriptObject = token.EncodeObject({ '0': 10, '1': '10' }));

Previously, this would return work and the result was the same as token.EncodeObject({ '0': 10, '1': '10' })). Now, this throws an error.

@taquito/michelson-encoder - For an OrToken with nested OrTokens, generateSchema behaved inconsistently with Execute and EncodeObject

Previously, generateSchema would generate a schema object that was misleading and did not match what Execute created or EncodeObject accepted. This is now fixed and the behavior is consistent across all methods.

const token = createToken(
  {
    prim: 'or',
    args: [
      {
        prim: 'bytes',
      },
      {
        prim: 'or',
        annots: ['A'],
        args: [
          {
            prim: 'or',
            args: [{ prim: 'int' }, { prim: 'nat' }],
          },
          { prim: 'bool' },
        ],
      },
    ],
  },
  0
) as OrToken;
const schema = token.generateSchema();

Previously, schema would be equal to:

{
    __michelsonType: "or",
    schema: {
        "0": { __michelsonType: "bytes", schema: "bytes" },
        "A": {
            __michelsonType: "or",
            schema: {
                "1": { __michelsonType: "int", schema: "int" },
                "2": { __michelsonType: "nat", schema: "nat" },
                "3": { __michelsonType: "bool", schema: "bool" }
            }
        }
    }
}

Which was inconsistent with what Execute created and what EncodeObject accepted.
Now it is:

{
    __michelsonType: 'or',
    schema: {
        0: { __michelsonType: 'bytes', schema: 'bytes' },
        1: { __michelsonType: 'int', schema: 'int' },
        2: { __michelsonType: 'nat', schema: 'nat' },
        3: { __michelsonType: 'bool', schema: 'bool' },
    },
}