Upgrade assetgraph to version 5.3.0 #176
Merged
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.
We've upgraded a dependency and all tests pass. \o/
You should probably take a good look at this before merging this pull request, of course.
What changed?
✳️ assetgraph ( → 5.3.0) · Repo
Release Notes
5.3.0
Assetgraph will now include an HTTP Referer header when populating HTTP --> HTTP relations
Commits
See the full diff on Github. The new version differs by 15 commits:
5.3.0
Merge pull request #932 from assetgraph/feat/http-referer-header
Adapt to PR feedback
Add Rererer header to all HTTP populations that follow from an incoming relation from an HTTP based asset
Added failing test for HTTP Referer header in asset population
Merge pull request #931 from assetgraph/depfu/update/npm/postcss-values-parser-2.0.0
Update postcss-values-parser to version 2.0.0
Travis: Stick with node.js 8.11
Don't break because Function#toString omits the space after function in node 10
Merge remote-tracking branch 'DanielRuf/chore/add-nodejs-10'
.nvmrc: Bump node.js to 10.x
Merge pull request #930 from assetgraph/depfu/check/npm/lodash-4.17.11
Pin lodash to version 4.17.11
Update prettier to ~1.14.2
eslint --fix .
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.