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

chore(main): release 0.3.1 #181

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 4, 2023

🤖 I have created a release beep boop

0.3.1 (2023-09-26)

Features

Bug Fixes

  • bring back wait for capella fork epoch (#212) (c7cce7e)
  • bug with participant counts that lead to more than needed participants (#221) (7b93f1c)
  • dont wait for epoch 1 and launch MEV before tx-fuzz (#210) (8b883af)
  • fail capella fork epoch (#196) (ebff2d0)
  • fix mismatch between validator_count & metrics gazer (#223) (5dd4f9b)
  • Improve MEV setup to use less containers for non_validator nodes (#224) (bd176f0)
  • Kevin/postgres package upgrade (#179) (1bcc623)
  • Kevin/unpin redis version (#182) (4eb7127)
  • lodestar flag (#217) (5f1e0f2)
  • mev should work with the validator count change (#225) (37dccce)
  • mev-boost creation by making it depend on actual participant count (#191) (7606cff)
  • Mock builder updates (#193) (6cc3697)
  • parse input (#205) (a787b38)
  • pass through env var now for builder_signing_tx_key (#207) (a63f2fd)
  • Pin Redis version in prep for package catalog version upgrade (#180) (09b235a)
  • remove hardcoding of addresses in MEV flood (#184) (21b0975)
  • replace plan.assert with plan.verify (#202) (073135d)
  • start boost immediately after relay starts running (#213) (b6ce1e9)
  • update readme for MEV params (#189) (c1bf13e)
  • use 4th private key (index 3) for tx fuzz like before (#215) (1752ed0)
  • use the third address instead of coinbase for tx-fuzz (#185) (3b2993c)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--kurtosis branch 7 times, most recently from f989401 to 07c8980 Compare September 11, 2023 16:24
@github-actions github-actions bot force-pushed the release-please--branches--main--components--kurtosis branch 8 times, most recently from 19ba069 to 62a59f2 Compare September 18, 2023 20:01
@github-actions github-actions bot force-pushed the release-please--branches--main--components--kurtosis branch 14 times, most recently from 3ef5a43 to fcba91b Compare September 22, 2023 12:20
@github-actions github-actions bot force-pushed the release-please--branches--main--components--kurtosis branch 2 times, most recently from a1a6760 to 7c02eb4 Compare September 22, 2023 13:09
@github-actions github-actions bot force-pushed the release-please--branches--main--components--kurtosis branch from 7c02eb4 to ce721ae Compare September 26, 2023 10:25
@h4ck3rk3y h4ck3rk3y merged commit b943370 into main Sep 26, 2023
@h4ck3rk3y h4ck3rk3y deleted the release-please--branches--main--components--kurtosis branch September 26, 2023 13:44
@github-actions
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant