Update rubocop-packaging 0.5.2 → 0.6.0 (major) #24
Conversation
This file contains hidden or 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
Pull Request Test Coverage Report for Build 14028288450Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
✳️ rubocop-packaging (0.5.2 → 0.6.0) · Repo
Release Notes
0.6.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
Cut 0.6.0 releaseDrop .travis.yml in favor of GitHub actionsMerge pull request #52 from koic/suppress_rubocop_offenseMerge pull request #53 from koic/pluginfy_with_lint_rollerPluginfy rubocop-packagingSuppress a RuboCop's offenseMerge pull request #51 from utkarsh2102/remove-pry-dependencyRemove dependency on pryMerge pull request #50 from utkarsh2102/update-gemspec-runtime-dependenciesReplace soft-deprecated runtime dependency specificationMerge pull request #49 from utkarsh2102/fix-gemspec-git-specsDisable Gemspec/DevelopmentDependencies copEnsure consistent message format in specs for Packaging::GemspecGitMerge pull request #48 from micwoj92/patch-1Rename IgnoredMethods to AllowedMethodsMerge pull request #47 from r7kamura/feature/urlFix incorrect documentation URLs when using `rubocop --show-docs-url`Commits
See the full diff on Github. The new version differs by 10 commits:
Bump version.Update CI matrix, remove redundant `context`s from specs (#42)Replace bacon with rspec (#41)Use latest ruby versions on test job (#39)Bump actions/checkout (#38)Use `require_relative` instead of `require` (#37)Update Rubies in CI (#35)Fix usage example for Sexp (#36)Fix broken linkFixnum is now spelled Integer (#33)Release Notes
3.3.7.2 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 6 commits:
Update changelog.Bump version.+ add prism-specific node types (#1071)Document the current state of the project in the readme (#1069)- builder.rb: fix hash value omission considering some local vars as constants (#1064)Update changelog.Release Notes
1.41.0
1.40.0
1.39.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 18 commits:
Cut 1.41.0Update ChangelogAdd support for `itblock` node for Ruby 3.4 (#365)Revert "Don't show a deprecation warning for `EnsureNode#branch` just yet"Restore docs/antora.ymlCut 1.40.0Update ChangelogEnforce a minimum version for prismUse the custom builder provided by prismAdd a release note of 1.39.0Restore docs/antora.ymlCut 1.39.0Update ChangelogModify `def_callback` code to be easier to understandEnable reusable Prism parse result (#359)[Fix #348] Automate the process of GitHub release creationFix current Rubocop offenses (#362)Restore docs/antora.ymlDepfu 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