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

[Snyk] Upgrade @stellar/stellar-sdk from 12.1.0 to 12.2.0 #8

Merged
merged 1 commit into from
Aug 10, 2024

Conversation

OKEAMAH
Copy link
Owner

@OKEAMAH OKEAMAH commented Aug 10, 2024

snyk-top-banner

Snyk has created this PR to upgrade @stellar/stellar-sdk from 12.1.0 to 12.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: @stellar/stellar-sdk
  • 12.2.0 - 2024-07-19

    Fixed

    • @ stellar/stellar-base and its underlying dependency @ stellar/js-xdr have been upgraded to their latest versions; reference their release notes (v12.1.0 and v3.1.2, respectively) for details (#1013).

    Added

    • You can now pass custom headers to both rpc.Server and Horizon.Server (#1013):
    import { Server } from "@ stellar/stellar-sdk/rpc";

    const s = new Server("<some URL>", { headers: { "X-Custom-Header": "hello" }})

    • Horizon.Server now supports the new POST /transactions_async endpoint via the submitAsyncTransaction method (#989). Its purpose is to provide an immediate response to the submission rather than waiting for Horizon to determine its status. The response schema is as follows:
    interface SubmitAsyncTransactionResponse {
      // the submitted transaction hash
      hash: string;
      // one of "PENDING", "DUPLICATE", "TRY_AGAIN_LATER", or "ERROR"
      tx_status: string;
      // a base64-encoded xdr.TransactionResult iff `tx_status` is "ERROR"
      error_result_xdr: string;
    }
    • rpc.Server now has a getFeeStats method which retrieves fee statistics for a previous chunk of ledgers to provide users with a way to provide informed decisions about getting their transactions included in the following ledgers (#998):
    export interface GetFeeStatsResponse {
    sorobanInclusionFee: FeeDistribution;
    inclusionFee: FeeDistribution;
    latestLedger: number; // uint32
    }

    interface FeeDistribution {
    max: string; // uint64
    min: string; // uint64
    mode: string; // uint64
    p10: string; // uint64
    p20: string; // uint64
    p30: string; // uint64
    p40: string; // uint64
    p50: string; // uint64
    p60: string; // uint64
    p70: string; // uint64
    p80: string; // uint64
    p90: string; // uint64
    p95: string; // uint64
    p99: string; // uint64
    transactionCount: string; // uint32
    ledgerCount: number; // uint32
    }

    New Contributors

    Full Changelog: v12.1.0...v12.2.0

  • 12.1.0 - 2024-06-14

    v12.1.0

    Added

    • contract now exports the DEFAULT_TIMEOUT (#984).
    • contract.AssembledTransaction now has:
      • toXDR and fromXDR methods for serializing the transaction to and from XDR. These methods should be used in place of AssembledTransaction.toJSON and AssembledTransaction.fromJSONfor multi-auth signing. The JSON methods are now deprecated. Note: you must now call simulate on the transaction before the final signAndSend call after all required signatures are gathered when using the XDR methods (#977).
      • a restoreFootprint method which accepts the restorePreamble returned when a simulation call fails due to some contract state that has expired. When invoking a contract function, one can now set restore to true in the MethodOptions. When enabled, a restoreFootprint transaction will be created and await signing when required (#991).
      • separate sign and send methods so that you can sign a transaction without sending it (signAndSend still works as before; #922).
    • contract.Client now has a txFromXDR method which should be used in place of txFromJSON for multi-auth signing (#977).

    Deprecated

    • In contract.AssembledTransaction, toJSON and fromJSON should be replaced with toXDR and fromXDR.
    • In contract.Client, txFromJSON should be replaced with txFromXDR.

    Fixed

    • If you edit an AssembledTransaction with tx.raw = cloneFrom(tx.build), the tx.simulationData will now be updated correctly (#985).
from @stellar/stellar-sdk GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @stellar/stellar-sdk from 12.1.0 to 12.2.0.

See this package in npm:
@stellar/stellar-sdk

See this project in Snyk:
https://app.snyk.io/org/okeamah/project/16fbcc40-a0ac-4eb6-857a-38a6bbcd677a?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

changeset-bot bot commented Aug 10, 2024

⚠️ No Changeset found

Latest commit: f7bf8a7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

@OKEAMAH OKEAMAH merged commit 872d657 into master Aug 10, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants