Update typescript interface function definion and bump version to 2.0.0

[v9n]

Follow Step 2 and 3

npm install
cd packages/api-augment
npm run clean:defs
npm run generate

then run:

npm run clean
npm run build

Note: I changed the port 8855 in the download-metadata script to my local 2.0.0 rpc node port 9946

[chrisli30]

Hmm I don’t think the events in augment-api-events.ts is updated correctly. Either there’s no logic to pick up the deleted event names, or the local node is still returning them through rpc.

@v9n maybe try to completely delete this file before running the npm scripts?

[chrisli30]

This version needs to be reset to "2.0.0-rc.1", meaning release candidate 1 for 2.0.0

[v9n]

thanks. I just corrected it.

[chrisli30]

Isn’t this Notify in automationTime deleted?

[v9n]

the Notify event is still there to support other test. We don't expose the extrins etc but the event still in the Event enum. Let me try to remove them all from the blockchain.

[chrisli30]

This should be deleted.

[chrisli30]

@imstar15, the types package’s code is behind. How do we update the types package?

[imstar15]

@imstar15, the types package’s code is behind. How do we update the types package?

This line of configuration also needs to be manually updated to 2.0.0-rc.1.
packages/api-augment/package.json also needs to be manually updated to 2.0.0-rc.1.

[chrisli30]

The changes are published on npm as v2.0.0-rc.1 as tested in xcm-demo code. Good to merge.

@v9n A couple of things to keep in mind of.

1. The commit message regen is too simple. Please ALWAYS make sure the message explains the reason a code commit. For example, in the case you can use Regenerate the api-augment files with the correct oak-blockchain version v2.0.0
2. The previous version of this PR was incorrect. I assumed that the regenerate scripts ran against an old blockchain code version.

[v9n]

@chrisli30 Sounds good. 👍 for the commit message. I will usually rebase and write more description commit before we merge.