Replies: 2 comments 3 replies
-
I really want to know your thoughts on this @qvalentin |
Beta Was this translation helpful? Give feedback.
-
Sounds great. I'm a fan of sematic versioning. I've basically just delayed until we say that the project is no longer in early development. But I would say we've reached that point. Setting up I also know release-please which is quite similar. |
Beta Was this translation helpful? Give feedback.
-
Overview
As our project grows, maintaining consistent and meaningful versioning is crucial for both developers and users.
To automate this process, I propose integrating semantic-release into our CI/CD pipeline.
This tool automatically manages versioning, changelogs, and package publishing based on commit messages following the Angular Commit Message Conventions specification (which we're already following).
Proposal
Objective: Automatically update the project version, more importantly generate changelogs, and publish releases whenever changes are pushed to the main branch.
Tools
We will use
semantic-release
along with relevant plugins for GitHub and Git.Expected Outcome
By integrating semantic-release, every push to main will:
This will ensure consistent version management and reduce the manual effort required for release management.
Feedback
I welcome any feedback or suggestions on this proposal.
If you have experience with
semantic-release
or see potential issues with this approach, please share your thoughts!Thanks.
Beta Was this translation helpful? Give feedback.
All reactions