-
Notifications
You must be signed in to change notification settings - Fork 38
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
workflows: add build/release workflow #2743
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2743 +/- ##
==========================================
- Coverage 28.88% 28.86% -0.02%
==========================================
Files 415 415
Lines 32478 32478
==========================================
- Hits 9380 9376 -4
- Misses 22255 22258 +3
- Partials 843 844 +1 ☔ View full report in Codecov by Sentry. |
33847c3
to
293d68b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tested it?
- name: Set up Go | ||
uses: actions/setup-go@v5 | ||
with: | ||
go-version: '1.21' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it means the latest one we adopted? so after the #2738 it gonna be 1.22?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, as usual. Except that 1.22 will be added when we're to drop 1.20, not when it's the minimal one (go.mod).
GOARCH: ${{ matrix.arch }} | ||
|
||
- name: Rename binaries | ||
run: for i in ./bin/*; do mv $i $i-${{ matrix.os.bin-name }}-${{ matrix.arch }}${{ (matrix.os.bin-name == 'windows' && '.exe') || '' }}; done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we are changing our release binaries now? do we need to mention this (changelog?)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They'll be exactly the same (that's why they're renamed) except for missing .tar.gz. I know .tar.gz is used in some cases, but those can be reworked and this duplication was never good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the new "linux" word in the binary name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check the binaries from https://github.com/nspcc-dev/neofs-node/actions/runs/7979125234?pr=2743, do we have correct number of linuxes there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated CHANGELOG as well, btw.
There were some fixes, but release can be tested only with a release. It at the same time is very similar to what NeoGo does. |
293d68b
to
7b5e058
Compare
And rework release procedure a bit. Don't rely on external tools and make CHANGELOGs better. Signed-off-by: Roman Khimov <[email protected]>
7b5e058
to
9c3c93e
Compare
Save artifacts, not just build them. Attach to releases. Push images. Similar to nspcc-dev/neofs-node#2743. Signed-off-by: Roman Khimov <[email protected]>
And rework release procedure a bit. Don't rely on external tools and make CHANGELOGs better.