-
Notifications
You must be signed in to change notification settings - Fork 26
bump juno to v0.12.2 #525
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 juno to v0.12.2 #525
Conversation
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 2 to 3. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@v2...v3) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 2.2.1 to 3.2.0. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@8c0edbc...2b51285) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [aws-actions/configure-aws-credentials](https://github.com/aws-actions/configure-aws-credentials) from 1.7.0 to 4.0.2. - [Release notes](https://github.com/aws-actions/configure-aws-credentials/releases) - [Changelog](https://github.com/aws-actions/configure-aws-credentials/blob/main/CHANGELOG.md) - [Commits](aws-actions/configure-aws-credentials@67fbcbb...e3dd6a4) --- updated-dependencies: - dependency-name: aws-actions/configure-aws-credentials dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 3.2.0 to 5.3.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@c56af95...2cdde99) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
gauntlet: add DEPLOY_ACCOUNT action
* deploying a fresh l2 feed before each starknet validator test * adds explicity tx.wait() calls * updates comment * reusing l2 uptime feed
* debug logs * publickey is for nonce manager, not contract address * add skip validate to estimate * change tag to pending * make deep copy in txstore * deep copy fix * set x-apikey option for juno rpc * fix bug * add api key in few places * fix debug err * log * tidy up logging * remove nonce tracking from txstore * clean up deep copy * remove test
* adjust token amount + add exp timer * add back skip_validate flag * modify config
# Conflicts: # integration-tests/go.mod # integration-tests/go.sum
upgrade ctf
|
Thanks, is this just cause? Or is there some dependency in the core that requires this bump |
I was hoping this would have a cascading effect that fixes the sourcegraph issues, but starknet.go is not compatible with this version anyways. |
|
@jmank88 Nethermind recently made a code change to update starknet.go based off our request to bump juno. They said it'll be released in their next version |
|
Updated to the latest starknet.go version, but now this forces us to upgrade geth, so we're blocked on smartcontractkit/chainlink#11809. |
|
4d70695 to
6d57319
Compare
|
Why was this closed? Please re-open @chray-zhang |
|
I accidentally erased some of chainlink-starknet's origin history. Do you have a local branch you can force push up? If not I created a new PR with your commit: #555 Can you let me know if that's the change? |
That is probably good enough 👍 |





No description provided.