Github Actions for NoM repos

Development ╰ Funding | Staging
60

Added action status badges in the README and updated syrius_library_updater such that it won’t fail if changes are not present.

1 Like
61

I think I can move forward and submit PRs for Github Actions for all repos.

Are there any other problems?

62

Can you please update all github workflows to echo the individual file hashes to stdout?
Otherwise, how will users know which workflow produced the releases?
Example: 1, 2

Also, do we need to make sure the source code zip is updated with each release?
image

63

I don’t quite understand your concern. The action outputs all hashes to the SHA256CHECKSUMS.txt file.

Need to check how to include the source code.

64

Since there have been multiple workflows, it’s not easy for a user to confirm which one uploaded the releases.

One can assume “the latest workflow produced the files” but it would be better to see in the action output which flow is related to those hashes.

1 Like
65

Oh, I see. Please let me think about it.

66

@sol check this out:

https://github.com/alienc0der/syrius/releases/tag/v0.0.6-alphanet

I don’t know why it didn’t put the body with the information from the GA job:

sc
sc2138×1358 196 KB

67

It’s looking good, but…

I checked the actions and it should be easier for people to determine when the releases were generated. Thank you! :+1:

68

It’s not perfect… yet.

I think I solved it. The only problem that remains is that the tag is created from the master branch, instead of cicd - pending issue.

69

This week I’m preparing to submit the AZ Github Actions Project.

So far I think we have a robust CICD pipeline. The next step will be to implement reproducible builds.

2 Likes
70

Topic moved to ╰ Funding | Staging

71

Hi @aliencoder,

I looked at the cicd github workflows and I’m concerned with some of the more minor dependencies not used by many people. Could we somehow refactor the code / isolate them in a separate job / reference a commit hash instead of using a specified version? or a combination of those workarounds / solutions?

The goal would be to minimize the possible vulnerabilities from including these third-party repositories in our build process.

I see you mentioned harden-runner in your opening post, so it’s clear this is something you already considered.

I hope you understand and look forward to reviewing and testing more of the less critical syrius bug fixes and improvements contributed :slight_smile:

2 Likes
72

I’ve implemented security hardening for Github Actions.

Hope everybody will support my PRs and my proposals :smiley:

4 Likes
73

Thank you for all your contributions and hard work!!

1 Like
74

Thank you, zir :alien:

75

Unfortunately govulncheck fails

I’ve commented out the govulncheck tool because the fix is to use latest Go version (even Go 1.20.1 returns a vulnerability).

At the moment xgo uses Go 1.20.0.

76

Created pull request for go-zenon: cicd: Github Actions workflow by alienc0der · Pull Request #15 · zenon-network/go-zenon · GitHub

77

4 posts were split to a new topic: Growing memory usage in go-zenon

78
  • Added iOS Simulator ARM64 architecture in the argon2_ffi.xcframework and pow_links.xcframework
  • Added Android x86_64 architecture for both argon2_ffi and pow_links libraries
  • Updated upload-action svenstaro/upload-release-action to latest version
2 Likes
79

Syrius Mobile?