Update rack-cors: 1.0.2 → 1.1.1 (minor) #118
Open
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rack-cors (1.0.2 → 1.1.1) · Repo · Changelog
Release Notes
1.1.1 (from changelog)
1.1.0 (from changelog)
1.0.6 (from changelog)
1.0.5 (from changelog)
1.0.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 40 commits:
Up gem versionAllow more flexible <resource>/* matchingBump puma from 3.12.1 to 3.12.2 in /examples/rails5Bump rack from 2.0.6 to 2.0.8 in /examples/rackBump rack from 2.0.7 to 2.0.8 in /examples/rails5Remove Rails 4 exampleUpdate Rails/Rack examplesReturn 400 on preflight for invalid requestsDon’t attempt to clean path if it is invalidCheck to see if path is valid before cleaningUse escape instead of escape_pathUp rack requirementUpdating Gems to hopefully get rid of alerts in GHReduce default max_age to a more sensible valueUnescape and resolve paths before resource checks[CI] Test against Ruby 2.6Version 1.0.3Clean up gemspecUpdate rack gemUpdate Rails4 exampleRemove unnecessary :require option from Gemfile exampleAdd an :if example to the README (based on https://github.com/cyu/rack-cors/issues/70#issuecomment-75392790)Remove CONTENT_TYPE constantremove content-type header from preflight responseUpdate rails4 example to 4.2.10Updated deps to fix more vulnerabilitiesUpdated Rails4 deps to fix vulnerabilitiesUpdated rack exampleRemoving Rails 3 exampleUpdating dev dependenciesTest PATCH supportAdd test for arrays of upstream Vary headersHandle arrays of vary headersfix readme typoUpdate README.md with ruby 1.9+ hash syntax[CI] Test against Ruby 2.4 and 2.5Add test coverage for loggerFixing some grammerzRename CHANGELOG to CHANGELOG.mdUpdate changelog👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.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.All Depfu comment commands