Implement automated changelog generation from conventional commits - #293
Open
Johnsource-hub wants to merge 2 commits into
Conversation
|
@renoschubert is attempting to deploy a commit to the Topmatrixmor2014 Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
please resolve these conflicts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#closes
#274
Summary
Implements automated changelog generation and release management using standard-version, commitlint, and husky. This completely replaces manual changelog maintenance by parsing conventional commits, generating release notes, and triggering GitHub Actions seamlessly.
Type of change
Bug fix
New feature
Documentation update
Refactor / chore
Smart contract change
Changes
standard-version integration: Added standard-version as a devDependency with .versionrc.json to properly parse feat, fix, docs, chore, perf, refactor, test, ci, and build commit types according to conventional commit guidelines.
npm release script: Added an npm run release script to package.json that automatically bumps the package version based on the commits, updates CHANGELOG.md, creates a git tag, and pushes the new tag and commit.
commitlint and husky setup: Initialized husky and added a commit-msg hook (.husky/commit-msg) along with @commitlint/config-conventional to enforce the conventional commit format locally before commits are accepted.
GitHub Actions synergy: Validated that .github/workflows/release.yml automatically triggers on version tags (tags: ["v*.."]) and uses generate_release_notes: true to auto-generate GitHub releases from the pushed tag.