-
Notifications
You must be signed in to change notification settings - Fork 25
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
release: chore - add new release workflow using magefiles #453
Conversation
Didn't run the rest of the pipeline? |
don't know why is not running, @matheusalcantarazup @wiliansilvazup @nathanmartinszup help? |
Try to close and reopen the PR. Something weird is happening in some PRs on github. |
I believe our workflows don't run for FORK. |
you're right check api workflow only runs on pushs, i will open another PR then rebase this |
I really think that we should delete the old and new release files, this way is kinda messy. |
This commit updates the platform actual version in all dependent files, add a new release process with two new files and one refactor and the usage of magefile project https://magefile.org/. In the magefile part added some privates commands in deployments/mage and imported some from horusec-devkit mageutils pkg New files are release-beta.yml and release-rc.yml and refactor was made to release.yml Signed-off-by: Ian Cardoso <[email protected]>
This commit updates the platform actual version in all dependent files, add a new release process with two new files and one refactor and the usage of magefile project https://magefile.org/.
In the magefile part added some privates commands in deployments/mage and imported some from horusec-devkit mageutils pkg
New files are release-beta.yml and release-rc.yml and refactor was made to new-release.yml now named release-new.yml to match the standards to be named only release.yml in a tested future.
Signed-off-by: Ian Cardoso [email protected]
- What I did
- How to verify it
- Description for the changelog