-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bump nokogiri from 1.10.10 to 1.11.1 #214
Conversation
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.10 to 1.11.1. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](sparklemotion/nokogiri@v1.10.10...v1.11.1) Signed-off-by: dependabot[bot] <support@github.com>
Hmm... after merging this and
|
Related stuff:
I'm gonna commit |
Both CI and deploy went fine, from the deploy log: |
I wonder if we need to add back the vendoring workflow, but run it on macOS? 🤔 Or will Dependabot be able to update both vendored native (or @greysteil as you just commented in the old issue 😆 (I know you are not as involved in Dependabot anymore as before)) |
Too complicated for me - I'll leave that one for @jurre and @feelepxyz! |
Hmm, I know that a feature was added to the latest version of Bundler to support updating all platforms, but we don't run that version of Bundler yet. I'll try to find some time this week to look into how we can support this in the current version of bundler. Adding back the vendoring workflow and running it on macOS would probably work, but I'm pretty sure we can tell bundler to do the right thing, maybe by running Edit: I wonder if having the OSX version installed before running this ensures that it'll be present in subsequent updates. Currently I'm mostly wondering how Dependabot can tell which versions to install 🤔 |
@jurre or @feelepxyz, has there been any progress in this area? Dependabot PR #256
The Lines 137 to 138 in 4431e97
Maybe because Bundler 1.17.3 was used? Not sure if Dependabot cares about this or not, either way I'm gonna update that to 2.2.23 today. Lines 172 to 173 in 4431e97
|
@dentarg yes this should be fixed in bundler 2. Let us know if you run into issues with it. |
#273 added |
Bumps nokogiri from 1.10.10 to 1.11.1.
Release notes
Sourced from nokogiri's releases.
... (truncated)
Changelog
Sourced from nokogiri's changelog.
... (truncated)
Commits
7be6f04
version bump to v1.11.1aa0c399
dev: overhaul .gitignore3d90c6d
Merge pull request #2169 from sparklemotion/2168-active-support-test-failurebbf850c
changelog: update for #2168ee69772
ci: another valgrind suppressionf9a2c4e
fix: restore proper error handling in the SAX push parser35aa88b
fix(cruby): reset libxml2's error handler in sax and push parsers07459fd
fix(test): clobber libxml2's global error handler before every testb682ac5
ci: ensure all tests are runningsetup
007662f
github: update "installation difficulty" issue templateDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.