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.

Sign up for GitHub

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

Jump to bottom

Allow limiting a package to a list of scopes. #154

Closed
Tracked by #98
dbanty opened this issue Mar 10, 2022 · 1 comment · Fixed by #262
Closed
Tracked by #98

Allow limiting a package to a list of scopes. #154

dbanty opened this issue Mar 10, 2022 · 1 comment · Fixed by #262
Labels
🥚 breaking change This change will require existing users to change something about their config 🎸 Feature New feature or request

Comments

@dbanty
Copy link
Member

dbanty commented Mar 10, 2022 •
edited
Loading

Only consider commits from those scopes or no scope for those packages. No scope = all scopes.
@dbanty dbanty mentioned this issue Mar 10, 2022
Closed
7 tasks
@dbanty dbanty changed the title Allow limiting a package to a list of scopes. Only consider commits from those scopes or no scope for those packages. No scope = all scopes. Allow limiting a package to a list of scopes. Mar 10, 2022
@dbanty dbanty added the 🎸 Feature New feature or request label Mar 10, 2022
@dbanty dbanty modified the milestones: 0.2.0, 0.3.0 Mar 26, 2022
@dbanty dbanty removed this from the 0.3.0 milestone Jun 10, 2022
@dbanty dbanty added the 🥚 breaking change This change will require existing users to change something about their config label Sep 5, 2022
dbanty added a commit that referenced this issue Sep 5, 2022
@dbanty
feat: Support limiting commits to scopes per package.
0744bc7 
Closes: #154

BREAKING-CHANGE: `PrepareRelease` will now error if no version-altering changes are detected.
@dbanty
Copy link
Member Author

dbanty commented Sep 5, 2022

It won't make sense to generate empty versions now—if only one package has scoped changes, only it should be updated. This could be done without breaking by only applying this rule when scopes are in effect, but I think that would be too confusing.

@dbanty dbanty mentioned this issue Sep 5, 2022
Merged
dbanty added a commit that referenced this issue Sep 5, 2022
@dbanty
feat: Support limiting commits to scopes per package. (#262)
53966d0 
Closes #154 

BREAKING CHANGE: `PrepareRelease` will now error if no version-altering changes are detected.

Co-authored-by: Dylan Anthony <dbanty@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🥚 breaking change This change will require existing users to change something about their config 🎸 Feature New feature or request
Projects
Monorepo Support
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Support limiting commits to scopes per package. knope-dev/knope
1 participant
@dbanty