-
-
Notifications
You must be signed in to change notification settings - Fork 3k
fix(deps): bump to @netlify/functions v5 to shave 82 MB from @astrojs/netlify
#14716
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
Open
serhalp
wants to merge
3
commits into
withastro:main
Choose a base branch
from
serhalp:fix/bump-netlify-functions
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+8
−37
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@astrojs/netlify': patch | ||
| --- | ||
|
|
||
| Upgrades `@netlify/functions` to v5. This removes 82 MB and 310 dependencies from the dependency tree. See [the relevant release notes](https://github.com/netlify/primitives/releases/tag/functions-v5.0.0). | ||
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Just wanted to be clear about no breaking changes for us, since this is a major dependency upgrade. (e.g. Ema's first reaction was to question this, so it should go in the notes so that people aren't wondering the same thing themselves!) So maybe something like above? (Please correct if the wording could be more accurate)
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.
🤔 As a developer, I would be surprised if I saw release notes for my dependency that mentioned a lack of breaking changes in an upgrade of one of its dependencies.
A dependency's dependencies are an implementation detail (until they aren't 😆). So I would personally suggest just documenting what the impact of the change is for
@astrojs/netlify's users—in this case, it's a smaller dependency tree and faster install size.Of course this is just my opinion! Let me know 🙂.