Skip to content

chore(deps): update dependency rubocop-on-rbs to v2 - #35

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rubocop-on-rbs-2.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rubocop-on-rbs-2.x

Conversation

@renovate

@renovate renovate Bot commented Apr 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rubocop-on-rbs (changelog) '~> 1.8' → '~> 2.0' age adoption passing confidence

Release Notes

ksss/rubocop-on-rbs (rubocop-on-rbs)

v2.2.0

Compare Source

  • Mark all RBSInline/* cops as Enabled: pending by @​ksss in #​164
    • They will be enabled by default in v3.0.0. Use NewCops: enable to enable them now.
  • Add RBSInline department for RBS inline annotations in Ruby files by @​ksss in #​159
    • RBSInline/Lint/Syntax
    • RBSInline/Lint/UnusedAnnotation
  • Replace crc32 cache with ObjectSpace::WeakKeyMap and drop zlib dependency by @​ksss in #​160
  • Add RBSInline/Style department by @​ksss in #​161
    • RBSInline/Style/BlockReturnBoolish
    • RBSInline/Style/ClassWithSingleton
    • RBSInline/Style/ClassicType
    • RBSInline/Style/DuplicatedType
    • RBSInline/Style/EmptyArgument
    • RBSInline/Style/InitializeReturnType
    • RBSInline/Style/InstanceWithInstance
    • RBSInline/Style/OptionalNil
    • RBSInline/Style/RedundantParentheses
    • RBSInline/Style/TrueFalse
  • Drop steep by @​ksss in #​162
  • Add RBSInline/Lint cops sharing implementation with RBS/Lint by @​ksss in #​163
    • RBSInline/Lint/AmbiguousKeywordArgumentKey
    • RBSInline/Lint/DuplicateOverload
    • RBSInline/Lint/LiteralIntersection
    • RBSInline/Lint/NewReturnsVoid
    • RBSInline/Lint/RestKeywordHash
    • RBSInline/Lint/UnusedOverloadTypeParams

v2.1.0

Compare Source

v2.0.0

Compare Source


Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Apr 17, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile.lock
Writing lockfile to /tmp/renovate/repos/github/poporonnet/mrubyc_types/Gemfile.lock
Fetching gem metadata from https://rubygems.org/...........
Resolving dependencies...

Could not find compatible versions

Because steep >= 1.10.0, < 2.0.0 depends on rbs ~> 3.9
  and rubocop-on-rbs >= 2.0.0 depends on rbs ~> 4.0,
  steep >= 1.10.0, < 2.0.0 is incompatible with rubocop-on-rbs >= 2.0.0.
So, because Gemfile depends on rubocop-on-rbs ~> 2.0
  and Gemfile depends on steep ~> 1.10,
  version solving has failed.

@renovate
renovate Bot force-pushed the renovate/rubocop-on-rbs-2.x branch from df45805 to 9a25c79 Compare May 18, 2026 10:07
@renovate
renovate Bot force-pushed the renovate/rubocop-on-rbs-2.x branch from 9a25c79 to ec8b86b Compare July 17, 2026 11:32
@renovate
renovate Bot force-pushed the renovate/rubocop-on-rbs-2.x branch from ec8b86b to 1494522 Compare August 12, 2026 01:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants