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.

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

Update assetgraph to version 2.7.0 πŸš€ #98

Merged
merged 1 commit into from
May 14, 2016

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello πŸ‘‹

πŸš€πŸš€πŸš€

assetgraph just published its new version 2.7.0, which is not covered by your current version range.

If this pull request passes your tests you can publish your software with the latest version of assetgraph – otherwise use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


The new version differs by 8 commits .

  • 9f0e110 2.7.0
  • 69516a6 Merge branch 'contentSecurityPolicy'
  • 0384bfa Merge pull request #530 from assetgraph/greenkeeper-eslint-2.10.0
  • 5ddb8e9 chore(package): update eslint to version 2.10.0
  • 967e424 loadAssets: Replace seq with async.
  • 936efcf resolveAssetConfig: Replace seq with async.
  • 53c71b3 Added reviewSubResourceIntegrity transform.
  • 2272eee Add a reviewContentSecurityPolicy transform and some helper methods to Html.

See the full diff.


This pull request was created by greenkeeper.io.
It keeps your software up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚑

@coveralls
Copy link

coveralls commented May 14, 2016

Coverage Status

Coverage remained the same at 94.276% when pulling 669e302 on greenkeeper-assetgraph-2.7.0 into bedf982 on master.

@papandreou papandreou merged commit 9759776 into master May 14, 2016
@papandreou papandreou deleted the greenkeeper-assetgraph-2.7.0 branch May 14, 2016 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants