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.
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
17.1.0 #337
17.1.0 #337
Changes from all commits
a53a9ae
4353487
8f88598
f269685
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I had thought it was our practice to ignore dependency updates in the changelog. I do have a hard time imagning how it could be relevant to consumers unless the update would be breaking by some other measure. @MajorLift @mcmire what's your thinking about this?
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.
It's been our practice to ignore dev dependencies, but not non-dev dependencies. Perhaps this is something we only do in the
core
repo and not elsewhere — but my thought is that it's useful to be able to look back at when a dependency was intentionally introduced or upgraded in case it causes an issue that we weren't aware of later on. Do you think this is information that can be gleaned elsewhere if need be?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.
Adding to the above, on core, we have a
reviewing-release-prs
doc that specifies dependency bumps as needing to be captured in the changelog.I think it's useful information to record in principle, but can get a bit noisy. Being able to record only the "important" bumps would be nice, but I guess to achieve the benefit @mcmire pointed out -- looking back to find the source of an error we didn't know about beforehand -- we can't pick and choose which bumps to record.