pact-foundation / pact-foundation/pact-ruby-e2e-example
Dependency Dashboard
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
Detected Dependencies
bundler (9)
e2e-pact-ruby-v1/Gemfile (5)
pact "~> 1.63"→ [Updates:"~> 2.0"]rake "~> 13"rspec "~> 3"faraday "~> 2.0", "< 3.0"pry-byebug "~> 3"e2e/Gemfile
e2e/pact_broker/Gemfile
grpc/Gemfile (3)
rake '~> 13'gruf '>= 2.18'gruf-rspec '>= 0.6.0'http/Gemfile (2)
faraday '~> 2.0', '< 3.0'rake '~> 13'kafka/Gemfile (5)
rake '~> 13'sbmt-kafka_consumer ">= 2.0.1"sbmt-kafka_producer ">= 1.0"gruf '>= 2.18'gruf-rspec '>= 0.6.0'message/Gemfile
mixed/Gemfile (6)
faraday '~> 2.0', '< 3.0'rake '~> 13'sbmt-kafka_consumer ">= 2.0.1"sbmt-kafka_producer ">= 1.0"gruf '>= 2.18'gruf-rspec '>= 0.6.0'pact_broker/Gemfile (1)
padrino-core ">= 0.16.0.pre3"
github-actions (3)
.github/workflows/test-broker.yml (2)
actions/checkout v7ruby/setup-ruby v1.github/workflows/test-e2e.yml (2)
actions/checkout v7ruby/setup-ruby v1.github/workflows/test-examples.yml (2)
actions/checkout v7ruby/setup-ruby v1
- Check this box to trigger a request for Renovate to run again on this repository
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the dependency entries for the e2e-pact-ruby-v1/Gemfile and the .github/workflows files, then inspect pull request 42 for the pact v2 update. Start by checking the listed dependency changes and CI results; done means the update is resolved and the relevant workflows pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, ruby
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100