This repository was archived by the owner on Jul 15, 2025. It is now read-only.
Gorelease #1237
Unanswered
vinayak0035
asked this question in
Q&A
Gorelease
#1237
Replies: 3 comments 1 reply
|
We are actively working on cleaning this up and updating the Docker, docker-compose, and images. Thank you for bringing this up and we are aware of the issue. All mumbai references will be removed and replaced with amoy. |
0 replies
|
also this perm file is required ? |
1 reply
|
Update: |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi @petejkim @djpolygon, I have a question.
In the release process (https://github.com/maticnetwork/heimdall/blob/v1.2.0/.github/workflows/release.yml#L42), it calls the release, which in turn triggers the
make releasecommand. This process then calls the.gorelease.yamlfile. During the Docker build, we are currently copying thegenesis-testnet-v4file, which is from the Mumbai testnet (located inbuilder/file).Since the testnet is now Amoy, shouldn’t we update the
builder/fileswith the Amoy genesis file and ensure it gets copied during the Docker build?Also prerm is it req to copy this file as i can see this is commented file and is only used in mainnet and amoy
https://github.com/maticnetwork/heimdall/blob/master/.github/workflows/mainnet_deb_profiles.yml#L84
All reactions