feat: add e2e coverage for release publish command #220
Conversation
This file contains hidden or 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
bdchatham
reviewed
Jul 7, 2025
mellis0303
changed the title
|
We have changed the env secrets for l1 to sepolia , that is why the e2e devnet is failing. |
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.
Motivation:
To provide e2e testing coverage for the release publish command. Ensuring that local docker registry is spun up and ReleaseManager contract is queried and updated correctly
Modifications:
Added e2e coverage testing to e2e.yml workflow file.
Result:
Added E2E coverage testing for release publish command.
Testing:
Queries the ReleaseManager contract for version and checks the devnet.yaml context for artifacts proving release publish command was successful.