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

feat: Adding arbitrary contract definition #646

Merged
merged 22 commits into from
Jun 11, 2024

Conversation

parithosh
Copy link
Member

No description provided.

network_params.yaml Outdated Show resolved Hide resolved
@barnabasbusa barnabasbusa enabled auto-merge (squash) June 11, 2024 14:36
@barnabasbusa barnabasbusa merged commit cb58b65 into main Jun 11, 2024
75 of 106 checks passed
@barnabasbusa barnabasbusa deleted the add-arbitrary-contract-def branch June 11, 2024 14:36
This was referenced Jun 11, 2024
h4ck3rk3y pushed a commit that referenced this pull request Jun 13, 2024
🤖 I have created a release *beep* *boop*
---


##
[4.0.0](3.1.0...v4.0.0)
(2024-06-13)


### ⚠ BREAKING CHANGES

* migrate from kurtosis-tech to ethpandaops repository
([#663](#663))

### Features

* add names to run-sh
([#666](#666))
([6b447b7](6b447b7))
* Adding arbitrary contract definition
([#646](#646))
([cb58b65](cb58b65))
* migrate from kurtosis-tech to ethpandaops repository
([#663](#663))
([d980fee](d980fee))
* update Lodestar BN <> VC compatibility
([#664](#664))
([7f365da](7f365da))


### Bug Fixes

* permissions on autorelease
([#671](#671))
([fcaa2c2](fcaa2c2))
* update release please
([#670](#670))
([fa53672](fa53672))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

3 participants