Skip to content

Auto Release Part I: CLI#998

Open
superboyiii wants to merge 18 commits intoneo-project:master-n3from
superboyiii:auto-release
Open

Auto Release Part I: CLI#998
superboyiii wants to merge 18 commits intoneo-project:master-n3from
superboyiii:auto-release

Conversation

@superboyiii
Copy link
Member

@superboyiii superboyiii commented Feb 5, 2026

Since neo-node is using immutable release now. It's necessary to make auto-release workflow because we can only release once and it can never be changed. This is the first part of neo-node auto-release workflow (only for CLI now, I will add plugins in Part II). It automatically build & pack CLI & upload to release draft. Most OS can run it without installing any additional dependency. For mac users, they may need brew install gperftools, no more others. I've tried this on my own repo and it works well.

How to test this:

  1. Fork it to your own repo, checkout master-n3.
  2. Replace neo-project with your own user name.
  3. For quick test, you can comment out Publish to NuGet part.
  4. Change neo-node\src\Directory.Build.props, make <VersionPrefix>3.9.3</VersionPrefix> as <Version>3.9.3</Version>.

@github-actions github-actions bot added the N3 label Feb 5, 2026
@coveralls
Copy link

coveralls commented Feb 5, 2026

Pull Request Test Coverage Report for Build 21708162795

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 38.917%

Totals Coverage Status
Change from base Build 21707655558: 0.0%
Covered Lines: 7122
Relevant Lines: 16952

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants