Non-Breaking Upgrade of Ruby Gems #3142
Merged
Conversation
This file contains 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
zinduolis
had a problem deploying
to
Integrate Pull Request
GitHub Actions
Failure
stephenakq
temporarily deployed
to
github-pages
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request
Thanks for submitting a PR! Please fill in this template where appropriate:
Category
Dependency upgrade
Feature/Issue Description
Q: Please give a brief summary of your feature/fix
A: Non breaking upgrade of ruby gems
Q: Give a technical rundown of what you have changed (if applicable)
A: Running ./install in my Ubuntu environment updated multiple dependencies in the Gemfile.lock, including three packages flagged by Dependabot: rexml, curb, and selenium-webdriver.
Test Cases
Q: Describe your test cases, what you have covered and if there are any use cases that still need addressing.
A: I successfully ran bundle exec rake, with all 131 non-pending test cases passing. The framework started without any issues. I accessed the interface through Firefox, opened another Firefox window, connected the browser to the framework, and verified that browser information was being logged. I then successfully executed several modules, including Google phishing, browser fingerprinting and all the debug modules.
Wiki Page
If you are adding a new feature that is not easily understood without context, please draft a section to be added to the Wiki below.