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

ci(changesets): versioning packages #1833

Merged
merged 2 commits into from
Mar 14, 2024
Merged

Conversation

fuel-service-user
Copy link
Contributor

@fuel-service-user fuel-service-user commented Mar 5, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@fuel-ts/account@0.77.0

Minor Changes

    • Rename Asset type Fuel to NetworkFuel
    • Rename Asset type Ethereum to NetworkEthereum
    • Exporting Asset types, by @Torres-ssf (See #1877)
  • !feat: accept predicate data on the Predicate constructor
    This is a BREAKING change since the API for the Predicate constructor has changed:
    // old API
    const predicate = new Predicate(
      bytecode,
      provider,
      abi,
      configurableConstants,
    );
    // new API
    const predicate = new Predicate({
      bytecode,
      abi, // optional
      provider,
      inputData, // optional
      configurableConstants, // optional
    });
    Notice how the Predicate constructor now accepts an object with the following properties:
    • bytecode: The bytecode of the predicate.
    • abi: The JSON ABI of the predicate (optional).
    • provider: The provider for interacting with the predicate.
    • inputData: The predicate input data (optional).
    • configurableConstants: The configurable constants for the predicate (optional).
      This change was made with readability and ease-of-use in mind, since having too many arguments in a 'flat' constructor can be confusing. Consider a scenario where you want to create a Predicate with configurables but no input data:
    const predicate = new Predicate(
      bytecode,
      provider,
      abi,
      undefined,
      configurableConstants,
    );
    In this case, you would have to pass undefined as the inputData argument, which is not ideal. By using the object-based constructor, you can now pass an object with the properties you want to set, and the constructor will handle the rest:
    const predicate = new Predicate({
      bytecode,
      abi,
      provider,
      configurableConstants,
    });
    The setData method has been removed. If you want to pass in the predicate data after instantiating the Predicate or if you want to use a different data than the one passed in the constructor, you will have to create a new Predicate instance, by @Dhaiwat10 (See #1826)
  • Added requestMiddleware to ProviderOptions as a way to allow the user the modification of each fetch call's request, by @nedsalk (See #1822)

Patch Changes

  • Add try/catch block when parsing GraphQL stream data response, by @Torres-ssf (See #1839)
  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)
  • 🐞 fix: disallow transferring <= 0 amounts, by @Dhaiwat10 (See #1827)
    • Handling SqueezedOut status update when calling submitAndAwait subscription at Provider.sendTransaction
    • Handling SqueezedOut status update when calling statusChange subscrition at TransactionResponse.waitForResult, by @Torres-ssf (See #1829)

create-fuels@0.77.0

Minor Changes

  • The create-fuels template app now provides a local faucet and uses a local burner wallet to execute transactions.
    Previously, the app was using a hardcoded key to sign all transactions. This key is now being used as the key for the faucet, and the burner wallet is being used to execute transactions.
    For convenience, the burner wallet is persisted in local storage so that it can be used across multiple sessions.
    The burner wallet is also topped up with 10,000 coins on first load.
    This is an important step towards adding support for the Fuel Wallet SDK, which will allow users to sign transactions using their own wallets, by @Dhaiwat10 (See #1864)

@fuel-ts/abi-coder@0.77.0

Patch Changes

  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)

@fuel-ts/abi-typegen@0.77.0

Patch Changes

@fuel-ts/address@0.77.0

Patch Changes

  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)

@fuel-ts/contract@0.77.0

Patch Changes

  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)

@fuel-ts/crypto@0.77.0

Patch Changes

  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)

@fuel-ts/errors@0.77.0

Patch Changes

  • Add try/catch block when parsing GraphQL stream data response, by @Torres-ssf (See #1839)
  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)
  • 🐞 fix: disallow transferring <= 0 amounts, by @Dhaiwat10 (See #1827)
    • Handling SqueezedOut status update when calling submitAndAwait subscription at Provider.sendTransaction
    • Handling SqueezedOut status update when calling statusChange subscrition at TransactionResponse.waitForResult, by @Torres-ssf (See #1829)

fuels@0.77.0

Patch Changes

  • Better error message when fuels cli deployment fails due to unavailable node, by @nedsalk (See #1854)

@fuel-ts/hasher@0.77.0

Patch Changes

  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)

@fuel-ts/merkle@0.77.0

Patch Changes

  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)

@fuel-ts/program@0.77.0

Patch Changes

@fuel-ts/transactions@0.77.0

Patch Changes

  • Migrate implementations of sha256, keccak and scrypt to @noble/hashes, by @danielbate (See #1786)

@fuel-ts/versions@0.77.0

Patch Changes

  • Warn when running against unofficial fuel-core (e.g. nightly builds), by @nedsalk (See #1855)

@fuel-ts/forc@0.77.0

@fuel-ts/fuel-core@0.77.0

@fuel-ts/interfaces@0.77.0

@fuel-ts/math@0.77.0

@fuel-ts/script@0.77.0

@fuel-ts/utils@0.77.0

demo-wallet-sdk-react@0.1.1

@github-actions github-actions bot force-pushed the changeset-release/master branch 5 times, most recently from c0bb1f7 to 654f8d0 Compare March 7, 2024 10:30
@github-actions github-actions bot force-pushed the changeset-release/master branch 3 times, most recently from fbeea2d to 1df4163 Compare March 8, 2024 18:37
@nedsalk nedsalk closed this Mar 9, 2024
@nedsalk nedsalk reopened this Mar 9, 2024
@fuel-service-user fuel-service-user force-pushed the changeset-release/master branch 10 times, most recently from b31484f to 2daaa17 Compare March 14, 2024 05:30
arboleya
arboleya previously approved these changes Mar 14, 2024
@arboleya arboleya enabled auto-merge (squash) March 14, 2024 10:19
@arboleya arboleya disabled auto-merge March 14, 2024 10:36
danielbate
danielbate previously approved these changes Mar 14, 2024
Torres-ssf
Torres-ssf previously approved these changes Mar 14, 2024
Dhaiwat10
Dhaiwat10 previously approved these changes Mar 14, 2024
@arboleya arboleya enabled auto-merge (squash) March 14, 2024 15:06
Copy link
Contributor

Coverage Report:

Lines Branches Functions Statements
79.5%(+0.03%) 70.35%(+0%) 77.98%(+0.05%) 79.59%(+0.03%)
Changed Files:
Ok File (✨=New File) Lines Branches Functions Statements
🔴 packages/program/src/revert/revert-error-codes.ts 15.38%
(+1.1%)
0%
(+0%)
0%
(+0%)
14.28%
(+0.95%)
🔴 packages/program/src/revert/revert-error.ts 11.11%
(+0.4%)
0%
(+0%)
0%
(+0%)
11.11%
(+0.4%)

@arboleya arboleya merged commit bc72cb6 into master Mar 14, 2024
13 checks passed
@arboleya arboleya deleted the changeset-release/master branch March 14, 2024 15:11
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.

None yet

7 participants