Skip to content

Conversation

chirag-parmar
Copy link
Contributor

No description provided.

@chirag-parmar chirag-parmar marked this pull request as ready for review September 9, 2025 03:34
Comment on lines +93 to +111
shasum -a 512 build/nimbus_verified_proxy > "nimbus_verified_proxy.sha512sum"
- name: Upload release binary artifacts
if: success() && startsWith(github.ref, 'refs/tags/')
uses: actions/upload-artifact@v4
with:
name: proxy-${{ matrix.os }}-${{ matrix.cpu }}
path: |
build/nimbus_verified_proxy*
if-no-files-found: warn

- name: Upload release checksum artifacts
if: success() && startsWith(github.ref, 'refs/tags/')
uses: actions/upload-artifact@v4
with:
name: proxy-${{ matrix.os }}-${{ matrix.cpu }}-checksum
path: |
build/nimbus_verified_proxy.sha512sum
if-no-files-found: warn
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this means the release will misbehave when the current verified proxy CI hasn't finished it's build?
i.e release might use stale artifacts

Copy link
Contributor Author

@chirag-parmar chirag-parmar Sep 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right, I just realised github workflows are not pipelined. Should I go ahead and pipeline the workflows or should I just rebuild the verified proxy for the release job(rebuilding seems wasteful)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right, I just realised github workflows are not pipelined. Should I go ahead and pipeline the workflows or should I just rebuild the verified proxy for the release job(rebuilding seems wasteful)?

Whatever gets selected here, please also think ahead in the sense that nimbus_portal_client will also need to be added to the release binaries eventually

@@ -133,9 +133,22 @@ jobs:
cat linux-arm64-checksum/* >> release_notes.md
echo '# Windows AMD64' >> release_notes.md
cat windows-amd64-checksum/* >> release_notes.md
echo '# macos ARM64' >> release_notes.md
echo '# MacOS ARM64' >> release_notes.md
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Official capitalization is macOS

cat proxy-linux-arm64-checksum/* >> release_notes.md
echo '# Windows AMD64' >> release_notes.md
cat proxy-windows-amd64-checksum/* >> release_notes.md
echo '# MacOS ARM64' >> release_notes.md
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also macOS.

@advaita-saha
Copy link
Contributor

The expected correct way would to implement the VP distribution build into
make -j<> dist-linux-amd64

This currently generates EL build, but should also generate a VP build
And take the release process from there

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.

4 participants