Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump node-fetch and eosjs in /scripts #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Apr 29, 2023

Removes node-fetch. It's no longer used after updating ancestor dependency eosjs. These dependencies need to be updated together.

Removes node-fetch

Updates eosjs from 16.0.9 to 22.1.0

Release notes

Sourced from eosjs's releases.

EOSJS v22.1.0 Release Notes

This release is the stable release of EOSJS v22.1.0 and contains features, security, stability and miscellaneous fixes.

Support for Read Only Transactions

This release introduces support for the new feature of read only transactions within smart contracts. This feature provides a contract-supported method of read-only queries from external clients via HTTP-RPC. Prior to this release, access was limited to data stored in a single table in DB or KV tables via the get_table_rows or get_kv_table_rows API, a mechanism which is exacting and inefficient. Read-only queries enable developers to perform more complex, cross-table queries natively via contract code with the assurance that table data is from the same block height. It can also be used to understand the consequences of a transaction before it is sent. More information can be found here in the documentation for cleos and here in the documentation specific to eosjs.

The transaction_trace has been modified with the addition of a bill_to_accounts field, so that it is clear which account paid for cpu/net for the transaction. Additionally, in the case of a failed transaction, available traces are returned to assist in the understanding of why the transaction failed. You can find the failure traces by using the new details field in the RPCError object.

An example transaction using eosjs might look like:

await api.transact({
    actions: [{
        account: 'readonly',
        name: 'get',
        authorization: [{
            actor: 'readonly',
            permission: 'active',
        }],
        data: {},
    }],
}, {
    useLastIrreversible: true,
    expireSeconds: 30,
    readOnlyTrx: true,
    returnFailureTraces: true,
});

The above transaction calls this action that is able to retrieve entries in two tables instead of needing to run get_kv_table_rows multiple times:

[[eosio::action, eosio::read_only]]
std::vector<my_struct> get() {
   my_table_m tm{get_self()};
   my_table_f tf{get_self()};
std::vector<my_struct> ret;
auto itm = tm.id.begin();
auto itm_e = tm.id.end();
eosio::cout << "Males: \n";
while(itm != itm_e){
auto row = itm.value();
eosio::cout << "id=" << row.id << ", name=" << row.name << ",gender=" << row.gender << ", age=" << row.age << "\n";
my_struct s;
s.id = row.id;
s.name = row.name;
s.gender = row.gender;
s.age = row.age;
ret.push_back(s);
++itm;
</tr></table>

... (truncated)

Commits
  • 1fa93d4 Merge pull request #992 from EOSIO/release/22.1.x
  • 9ccdb11 Merge pull request #994 from EOSIO/merging_master
  • 370b9e8 Updating package.json and yarn.lock
  • d6842b6 Merge branch 'master' into merging_master
  • f05d9e8 Merge pull request #993 from EOSIO/updating_cicd_docker_image
  • 50dc670 Updating package.json and yarn.lock
  • 7147a05 Updating CI/CD to latest version before merging into develop
  • ea34fb9 Merge pull request #988 from EOSIO/updating_cicd_for_release
  • a1fbfb3 Updating default branch with new ci/cd and dependabot settings
  • f29efff Merge pull request #976 from EOSIO/dependabot/github_actions/develop/docker/s...
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by b1serviceaccount, a new releaser for eosjs since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Removes [node-fetch](https://github.com/node-fetch/node-fetch). It's no longer used after updating ancestor dependency [eosjs](https://github.com/EOSIO/eosjs). These dependencies need to be updated together.


Removes `node-fetch`

Updates `eosjs` from 16.0.9 to 22.1.0
- [Release notes](https://github.com/EOSIO/eosjs/releases)
- [Commits](EOSIO/eosjs@v16.0.9...v22.1.0)

---
updated-dependencies:
- dependency-name: node-fetch
  dependency-type: indirect
- dependency-name: eosjs
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants