Skip to content
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

Add semantic release #22

Merged
merged 7 commits into from
May 29, 2024
Merged

Add semantic release #22

merged 7 commits into from
May 29, 2024

Conversation

sebbonnet
Copy link
Collaborator

@sebbonnet sebbonnet commented May 29, 2024

Use semantic-release to automate versioning, tag and create GitHub releases based on the commit message.
semantic-release works from release branches, not pull requests. As a result, nothing will be released on pull requests.

Commit messages must follow Angular Commit Message Conventions

Also improve the docs to make the limitations clearer and describe the improvements we want to work on

To make the limitations clearer
and describe the improvements we want to work on
Copy link

github-actions bot commented May 29, 2024

Test Results

32 tests  ±0   32 ✅ ±0   12s ⏱️ -3s
 5 suites ±0    0 💤 ±0 
 2 files   ±0    0 ❌ ±0 

Results for commit 04a9cbd. ± Comparison against base commit 50bc86b.

♻️ This comment has been updated with latest results.

@sebbonnet sebbonnet force-pushed the semantic-release branch 3 times, most recently from 1bffd50 to 84fe97e Compare May 29, 2024 07:53
@sebbonnet sebbonnet force-pushed the semantic-release branch 2 times, most recently from 94a7504 to fc6061e Compare May 29, 2024 08:30
@sebbonnet sebbonnet force-pushed the semantic-release branch 2 times, most recently from 4add6cd to f7f13b7 Compare May 29, 2024 09:29
@sebbonnet
Copy link
Collaborator Author

I've considered building the distros in parallel in 9442ed8 to speed things up and add a bit more structure to our workflow.
Although we gain about 4mins, it adds some duplication as we need to setup up nix , but also increases complexity as we need to store the distros as artifacts in the new job, so we can download and publish them in the release job. So in the end I preferred going for a simple approach and have all the release steps in the same job.

@sebbonnet sebbonnet marked this pull request as ready for review May 29, 2024 09:46
@sebbonnet sebbonnet merged commit 33c83fb into main May 29, 2024
2 checks passed
@sebbonnet sebbonnet deleted the semantic-release branch May 29, 2024 15:00
Copy link

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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