-
Notifications
You must be signed in to change notification settings - Fork 0
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
build: specify commits that trigger a release #174
Conversation
WalkthroughThe changes introduced in the Changes
Poem
TipsChat with CodeRabbit Bot (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- .releaserc.yml (1 hunks)
Additional comments: 1
.releaserc.yml (1)
- 4-30: The changes to the
releaseRules
section of theplugins
configuration are well-structured and follow the guidelines provided by the semantic-release/commit-analyzer. The new rules forbuild(deps)
,build(deps-dev)
, anddocs(schema)
commits are clear and should help automate the release process more effectively. The alignment of nested properties also improves readability.
2754fed
to
9448776
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- .releaserc.yml (1 hunks)
Additional comments: 1
.releaserc.yml (1)
- 4-29: The changes to the semantic-release configuration look good. The addition of specific release rules for different commit types and scopes will help in automating the versioning process based on commit messages. The new rule for "docs" type with "schema" scope indicating a minor release is a good addition. Just ensure that the commit messages are written following the specified types and scopes for the rules to work as expected.
🎉 This PR is included in version 1.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Specify the commits that should trigger a release (cf. semantic-release/commit-analyzer), especially those affecting the project's behavior, for instance
build(deps)
,build(deps-dev)
anddocs(schema)
categories.@amimart Need this to enable a new release of the indexer based on the latest subql dependencies.
Summary by CodeRabbit