chore: release/v1.2.0 #268
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
moldy530
requested review from
rthomare,
dancoombs,
mokok123,
avasisht23 and
denniswon
as code owners
* docs: guides on how to handle userop not elligible for sponsorship * Update packages/core/src/provider/types.ts Co-authored-by: Michael Moldoveanu <michael.moldoveanu@alchemy.com> * Update site/guides/sponsoring-gas/gas-sponsorship-eligibility.md Co-authored-by: Ajay Vasisht <43521356+avasisht23@users.noreply.github.com> * Update site/guides/sponsoring-gas/gas-sponsorship-eligibility.md Co-authored-by: Ajay Vasisht <43521356+avasisht23@users.noreply.github.com> * Update site/guides/sponsoring-gas/gas-sponsorship-eligibility.md Co-authored-by: Ajay Vasisht <43521356+avasisht23@users.noreply.github.com> --------- Co-authored-by: Michael Moldoveanu <michael.moldoveanu@alchemy.com> Co-authored-by: Ajay Vasisht <43521356+avasisht23@users.noreply.github.com>
…etween 1271 and UO signing (#258)
# Pull Request Checklist - [x] Did you add new tests and confirm existing tests pass? (`yarn test`) - [x] Did you update relevant docs? (docs are found in the `site` folder, see guidleines below) - [x] Do your commits follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard? - [x] Does your PR title also follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard? - [x] If you have a breaking change, is it [correctly reflected in your commit message](https://www.conventionalcommits.org/en/v1.0.0/#examples? (e.g. `feat!: breaking change`) - [x] Did you run lint (`yarn lint:check`) and fix any issues? (`yarn lint:fix`) - [x] Is the base branch you're merging into `development` and not `main`? <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on adding the ability to simulate user operation asset changes in the Alchemy provider. ### Detailed summary - Added `SimulateUserOperationAssetChangesRequest` and `SimulateUserOperationAssetChangesResponse` types. - Added `alchemy_simulateUserOperationAssetChanges` method to the provider. - Added `withAlchemyUserOpSimulation` middleware function. - Updated tests. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
# Pull Request Checklist - [ ] Did you add new tests and confirm existing tests pass? (`yarn test`) - [ ] Did you update relevant docs? (docs are found in the `site` folder, see guidleines below) - [ ] Do your commits follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard? - [ ] Does your PR title also follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard? - [ ] If you have a breaking change, is it [correctly reflected in your commit message](https://www.conventionalcommits.org/en/v1.0.0/#examples? (e.g. `feat!: breaking change`) - [ ] Did you run lint (`yarn lint:check`) and fix any issues? (`yarn lint:fix`) - [ ] Is the base branch you're merging into `development` and not `main`? <!-- start pr-codex --> --- ## PR-Codex overview ### Detailed summary - Added a new method `withAlchemyUserOpSimulation()` to the `AlchemyProvider` class that adds the Alchemy UserOperation Simulation middleware. - Added a new middleware method `withAlchemyUserOpSimulation()` to the `aa-alchemy` package for simulating asset changes resulting from user operation. - Added documentation for `withAlchemyUserOpSimulation()` method in the `aa-alchemy` package. - Added documentation for `simulateUserOperationAssetChanges()` method in the `aa-alchemy` package. - Added documentation for `withUOSimulationMiddleware()` method in the `aa-core` package. - Added a new guide on how to simulate a User Operation using Alchemy's Account Kit. > The following files were skipped due to too many changes: `site/guides/sim-user-operation.md` > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
# Pull Request Checklist - [x] Did you add new tests and confirm existing tests pass? (`yarn test`) - [x] Did you update relevant docs? (docs are found in the `site` folder, see guidleines below) - [x] Do your commits follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard? - [x] Does your PR title also follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard? - [x] If you have a breaking change, is it [correctly reflected in your commit message](https://www.conventionalcommits.org/en/v1.0.0/#examples? (e.g. `feat!: breaking change`) - [x] Did you run lint (`yarn lint:check`) and fix any issues? (`yarn lint:fix`) - [x] Is the base branch you're merging into `development` and not `main`? <!-- start pr-codex --> --- ## PR-Codex overview ### Detailed summary - Updated URLs in various files to reflect changes in the site structure - Replaced occurrences of "/getting-started" with "/overview/getting-started" - Updated links and references to the "Getting Started" page - Updated links and references to the "Packages Overview" page - Updated links and references to the "Why Account Kit" page - Updated links and references to the "Introduction" page > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
Co-authored-by: Matthew Foyle <mfoyle93@gmail.com>
moldy530
force-pushed
the
release/v1.2.0
branch
from
7e10595 to
1814eb3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
yarn test)sitefolder, see guidleines below)feat!: breaking change)yarn lint:check) and fix any issues? (yarn lint:fix)developmentand notmain?PR-Codex overview
Detailed summary
getting-started.mdlink inLight Account ExamplesectionhomepageandoptionalDependenciesinalchemy/package.jsongetDefaultLightAccountFactoryAddressmethod description ingetDefaultLightAccountFactoryAddress.mdweb3auth.tsprovider-adapter.test.tsto useproviderinstead ofsignersim-uo-example/sim-middleware.tsandsim-uo-example/sim-method.tssimulate-uosignUserOperationHashmethod inaccount/types.tslight-account/e2e-tests/constants.tssponsoring-gas.md,demos.md,README.md, andoverview.mdaccount.test.tsto usechainvariableaa-accounts/index.mdalchemy-sdkversion inethers/package.jsonuri-jsversion inyarn.lock