busser-bats 0.5.0 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 80dd7f4f2a1bdbedde3ed56dd1d06006cf12500493e324aff04f3cc97d6fc847
-  data.tar.gz: 624cb79b0320e718ab509df144b17abd454f0d7f98394398f73269577177c64a
+  metadata.gz: 50827f7c53a1bce1a7ddc9bda08aacd3d7a2388fefc183b7bdc3cbdd23bac07f
+  data.tar.gz: 3a22e249cc415c99bdfd3f922b0a4d13665f267eb14216f2c1d226f76354ade3
 SHA512:
-  metadata.gz: 04744f07800df27d669bad4cec84c8c5ff2988ae47dcf1a277bf3d57fc1652116c02503311e9c081a9f754456967576c45adc452a7e78ea7c8dc971b73a52164
-  data.tar.gz: 65fc095f1ad7197228ae0ea880f5cb03b3963d8ab1a3e1fa10b19adfd5c6596fa0779397ba30ad8594bbce5f7c92c6fa5c0dfbab6b0b85de6fb56aadc971c44c
+  metadata.gz: c00aef02c07f8518d484107f04165d2e320cc0a822c36b7e74350795c84ce5e3b7d7a221cf75e0e679a9623995db2f2ee44a058b729a73a73442b8a56c38855f
+  data.tar.gz: 65749c81f7d399d2a2ce2c64eda0bc3235c815e7e1a7c6a2b0beef4756d8db414589140cdfc8df02d00da757d426eaf2f61bbcf3ab0c2cdb0f122401d96593fd

data/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+---
+name: "Test"
+
+"on":
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+# The default token is granted write access to most of the repository.
+# Nothing here needs more than the checkout.
+permissions:
+  contents: read
+
+# Supersede in-flight runs for a branch. Pull requests cancel freely, but
+# pushes to main do not: every commit on main should keep a build of its own.
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  lint-unit:
+    # Pinned to a commit rather than @main so an upstream edit cannot reach
+    # this repository's CI without a reviewed pull request. The trailing
+    # comment names the release the commit belongs to, which is what lets
+    # Renovate track the pin by version and keep both in step.
+    uses: test-kitchen/.github/.github/workflows/lint-unit.yml@95ef7803cf23aae5ee68593de5b7e0a731c1a929  # v0.4.0
+    with:
+      # This gem requires Ruby 3.2, and so do busser 0.9 and cucumber 11.
+      # Without this the shared workflow would still start a Ruby 3.1 job and
+      # bundler would refuse to resolve there.
+      ruby_versions: '["3.2", "3.3", "3.4", "4.0"]'

data/.github/workflows/pr-title.yml

@@ -0,0 +1,28 @@
+---
+name: "PR Title"
+
+"on":
+  pull_request_target:
+    types: [opened, edited, reopened, synchronize]
+
+permissions:
+  contents: read
+
+jobs:
+  conventional-title:
+    name: "Conventional commit title"
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: read
+    steps:
+      # Pull requests here are squash merged, so the pull request title becomes
+      # the commit subject on main. That makes the title the one place worth
+      # checking: release-please reads those subjects to decide the next
+      # version and to build the changelog.
+      #
+      # pull_request_target is used so the check also runs for pull requests
+      # from forks. No repository code is checked out in this job, so none of
+      # the usual pull_request_target risk applies.
+      - uses: amannn/action-semantic-pull-request@48f256284bd46cdaab1048c3721360e808335d50  # v6.1.1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

data/.github/workflows/publish.yml

@@ -0,0 +1,67 @@
+---
+name: "Release"
+
+"on":
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write        # tag the release and commit the version bump
+      pull-requests: write   # open and update the release pull request
+      packages: write        # push the gem to GitHub Packages
+    steps:
+      # Opens and maintains a release pull request. Merging that pull request
+      # is what actually cuts a release, so every step below is skipped until
+      # release_created is set.
+      - uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7  # v5.0.0
+        id: release
+        with:
+          token: ${{ secrets.PORTER_GITHUB_TOKEN }}
+
+      - name: Checkout code
+        if: ${{ steps.release.outputs.release_created }}
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+
+      # These two steps are handed publishing credentials, so they are pinned
+      # to a commit rather than a branch. A floating ref would let whoever
+      # controls that branch run code with a token that can push this gem.
+      - name: Publish to GitHub Packages
+        if: ${{ steps.release.outputs.release_created }}
+        uses: actionshub/publish-gem-to-github@86eb0ce1ced1072298bf68776a32a5c9703ad9aa  # v1.0.13
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          owner: ${{ github.repository_owner }}
+
+      - name: Publish to RubyGems
+        if: ${{ steps.release.outputs.release_created }}
+        uses: actionshub/publish-gem-to-rubygems@f9126f7a2d36a4fd31a13e78fde5fbdcc4b7b251  # v2.0.6
+        with:
+          token: ${{ secrets.RUBYGEMS_API_KEY }}
+
+      # actionshub/publish-gem-to-rubygems logs a rejected push and still exits
+      # 0, so a release that never reached RubyGems shows up as a green job.
+      # Ask RubyGems directly instead of trusting the step. The v2 endpoint is
+      # 404 until the exact version is indexed, so -f turns "not there" into a
+      # non-zero exit rather than a substring match on `gem list` output.
+      - name: Verify the release reached RubyGems
+        if: ${{ steps.release.outputs.release_created }}
+        env:
+          VERSION: ${{ steps.release.outputs.version }}
+        run: |
+          set -euo pipefail
+          name="$(basename "$(ls ./*.gemspec)" .gemspec)"
+          for _ in $(seq 1 12); do
+            if curl -fsS -o /dev/null "https://rubygems.org/api/v2/rubygems/${name}/versions/${VERSION}.json"; then
+              echo "${name} ${VERSION} is on RubyGems"
+              exit 0
+            fi
+            sleep 15
+          done
+          echo "::error::${name} ${VERSION} never reached RubyGems. A permissions failure in the push step above does not fail that step -- read its log."
+          exit 1

data/.gitignore

@@ -6,7 +6,6 @@
 Gemfile.lock
 InstalledFiles
 _yardoc
-coverage
 doc/
 lib/bundler/man
 pkg

data/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.7.0"
+}

data/.rubocop.yml

@@ -1,11 +1,6 @@
 ---
 require:
-  - chefstyle
+  - cookstyle/chefstyle
 
 AllCops:
-  TargetRubyVersion: 2.7
-  Include:
-    - "**/*.rb"
-  Exclude:
-    - "vendor/**/*"
-    - "spec/**/*"
+  TargetRubyVersion: 3.2

data/.yamllint

@@ -0,0 +1,6 @@
+---
+extends: default
+rules:
+  line-length:
+    max: 256
+    level: warning

data/CHANGELOG.md

@@ -1,5 +1,27 @@
 # busser-bats Changelog
 
+## [0.7.0](https://github.com/test-kitchen/busser-bats/compare/v0.6.0...v0.7.0) (2026-08-28)
+
+
+### ⚠ BREAKING CHANGES
+
+* the vendored bats goes from 0.4.0 to 1.14.0. Suites relying on bats 0.4 behaviour may need updating; see the bats-core changelog.
+
+### Features
+
+* vendor bats-core instead of the archived sstephenson/bats ([#59](https://github.com/test-kitchen/busser-bats/issues/59)) ([377240c](https://github.com/test-kitchen/busser-bats/commit/377240cbf04dee7bdec158fc306bbc5a7e7fe509))
+
+## [0.6.0](https://github.com/test-kitchen/busser-bats/compare/v0.5.0...v0.6.0) (2026-08-28)
+
+
+### ⚠ BREAKING CHANGES
+
+* Ruby 3.1 and busser releases older than 0.9.0 are no longer supported.
+
+### Features
+
+* require Ruby 3.2 and busser 0.9, adopt release-please ([#44](https://github.com/test-kitchen/busser-bats/issues/44)) ([3aa285e](https://github.com/test-kitchen/busser-bats/commit/3aa285e63f0b2f0b79666525022308eb14eee1c3))
+
 ## [0.5.0](https://github.com/test-kitchen/busser-bats/compare/v0.4.0...v0.5.0) (2023-11-30)
 
 
@@ -28,7 +50,7 @@
 
 * Upgrade vendored bats version to 0.4.0. ([@fnichol][])
 
-### Improvments
+### Improvements
 
 * Update testing dependencies, upgrade to RSpec 3.x, freshen TravisCI build matrix, add style and complexity support. ([@fnichol][])
 * Allow Aruba tests to wait 20 seconds (vs. 10). ([@fnichol][])

data/CONTRIBUTING.md

@@ -0,0 +1,86 @@
+# Contributing to busser-bats
+
+Thanks for taking the time to contribute. This document covers how to get the
+project running locally, how to check your work before opening a pull request,
+and the commit convention releases depend on.
+
+## Getting set up
+
+This plugin requires **Ruby 3.2 or newer**. Clone the repository and install the
+development dependencies:
+
+```bash
+git clone https://github.com/test-kitchen/busser-bats.git
+cd busser-bats
+bundle install
+```
+
+## Running the tests
+
+`rake` runs the whole suite:
+
+```bash
+bundle exec rake test
+```
+
+The tests are [cucumber](https://cucumber.io) features in `features/`. They
+drive the real `busser` executable through
+[aruba](https://github.com/cucumber/aruba) rather than calling the plugin's
+classes, so they cover it end to end: install the plugin into a throwaway
+Busser root, write a suite, run it, and check what came out. The step
+definitions they use are published by busser itself, in `lib/busser/cucumber.rb`.
+
+## Linting
+
+CI runs three linters, all of which you can run locally:
+
+```bash
+bundle exec cookstyle --chefstyle   # Ruby
+yamllint --strict .                 # YAML
+markdownlint-cli2 "**/*.md" "!**/CHANGELOG*.md"
+```
+
+## Commit messages
+
+This project uses [Conventional Commits](https://www.conventionalcommits.org).
+Releases are automated, and the commit subject on `main` is what decides the
+next version number and what appears in the changelog.
+
+Pull requests are **squash merged, so the pull request title becomes that
+subject**. A CI check enforces the format on the title; the individual commits
+on your branch are not checked.
+
+| Prefix | Effect on the next release |
+| --- | --- |
+| `fix:` | Patch version bump |
+| `feat:` | Minor version bump |
+| `feat!:`, or a `BREAKING CHANGE:` footer | Minor bump, until this gem reaches 1.0 |
+| `chore:`, `docs:`, `ci:`, `test:`, `refactor:` | No release |
+
+For example:
+
+```text
+fix: install the plugin into GEM_HOME rather than the bundle
+feat: support a Gemfile alongside the suite
+ci: pin the shared workflow to a release
+```
+
+## Opening a pull request
+
+1. Fork the repository and create a branch for your change.
+2. Add or update tests. A bug fix should come with a test that fails without it.
+3. Run `bundle exec rake test` and the linters above.
+4. Open a pull request with a Conventional Commits title.
+
+## Releases
+
+Releases are handled by
+[release-please](https://github.com/googleapis/release-please). It watches
+commits landing on `main` and keeps a release pull request open with the next
+version number and the accumulated changelog. Merging that pull request tags the
+release and publishes the gem to RubyGems and GitHub Packages.
+
+Maintainers do not bump `lib/busser/bats/version.rb` or edit
+`CHANGELOG.md` by hand; release-please owns both files. This gem is still pre-1.0, so
+`bump-minor-pre-major` is set and a breaking change takes the minor rather than
+graduating it to 1.0.

data/Gemfile

@@ -2,23 +2,19 @@ source "https://rubygems.org"
 
 gemspec
 
-group :guard do
-  gem "guard-cucumber"
-  gem "guard-cane"
-  gem "guard-rubocop"
+group :cookstyle do
+  gem "cookstyle", ">= 9.0"
 end
 
 group :test do
-  gem "rake", ">= 11.0"
-  gem "rspec", "~> 3.2"
-  gem "aruba"
+  gem "aruba", ">= 2.4"
+  gem "base64", ">= 0.3" # cucumber needs it; not a default gem on Ruby 4.0
+  gem "cucumber", ">= 11.1"
+  gem "minitest", ">= 6.0"
+  gem "mocha", ">= 2.7"
+  gem "rake", ">= 13.4"
 end
 
 group :development do
-  gem "countloc"
-  gem "simplecov"
-end
-
-group :chefstyle do
-  gem "chefstyle", "2.2.3"
+  gem "yard", ">= 0.9.37"
 end

data/README.md

@@ -1,52 +1,122 @@
-# Busser::RunnerPlugin::Bats
+# busser-bats
 
-[![Gem Version](https://badge.fury.io/rb/busser-bats.png)](http://badge.fury.io/rb/busser-bats)
-[![Build Status](https://travis-ci.org/test-kitchen/busser-bats.png?branch=master)](https://travis-ci.org/test-kitchen/busser-bats)
-[![Code Climate](https://codeclimate.com/github/test-kitchen/busser-bats.png)](https://codeclimate.com/github/test-kitchen/busser-bats)
+[![Gem Version](https://badge.fury.io/rb/busser-bats.svg)](https://badge.fury.io/rb/busser-bats)
 
-A Busser runner plugin for [Bats][bats_site]
+A [Busser](https://github.com/test-kitchen/busser) runner plugin that runs
+[Bats](https://github.com/bats-core/bats-core) test files.
+
+Bats is a TAP-producing test harness for bash. This plugin vendors a copy of it,
+installs that copy onto the machine under test during postinstall, and then runs
+it against the suite's `bats` directory — so the machine under test needs
+nothing beyond bash.
+
+The vendored copy is [bats-core](https://github.com/bats-core/bats-core), which
+is the maintained fork; `vendor/bats/VERSION.txt` records the exact release.
+`rake bats:vendor` refreshes it, and `BATS_VERSION` selects a different tag.
 
 ## Status
 
-This software project is no longer under active development as it has no active maintainers. The software may continue to work for some or all use cases, but issues filed in GitHub will most likely not be triaged. If a new maintainer is interested in working on this project please come chat with us in #test-kitchen on Chef Community Slack.
+This software project is no longer under active development as it has no active
+maintainers. The software may continue to work for some or all use cases, but
+issues filed in GitHub will most likely not be triaged. If a new maintainer is
+interested in working on this project please come chat with us in #test-kitchen
+on Chef Community Slack.
+
+## Requirements
+
+Ruby 3.2 or newer, and busser 0.9.0 or newer.
+
+## Installation
 
-## Installation and Setup
+Busser installs the plugin for you when Test Kitchen runs the suite, so there is
+usually nothing to do. To install it by hand:
 
-Until proper reference documentation is complete, the [Writing a Test](http://kitchen.ci/docs/getting-started/writing-test) section of the Test Kitchen's [Getting Started Guide](http://kitchen.ci/docs/getting-started/) gives a working example of creating a bats test.
+```bash
+busser plugin install busser-bats
+```
 
 ## Usage
 
-**TODO:** Write documentation explaining the structure/format of testing files.
+Put your `.bats` files in the `bats` directory of a suite:
 
-## Development
+```text
+test
+`-- integration
+    `-- default          # suite name
+        `-- bats
+            `-- default.bats
+```
 
-* Source hosted at [GitHub][repo]
-* Report issues/questions/feature requests on [GitHub Issues][issues]
+The whole directory is handed to `bats`, which picks up every `*.bats` file in
+it. A test is a `@test` block, and it passes when every command in it succeeds:
 
-Pull requests are very welcome! Make sure your patches are well tested.
-Ideally create a topic branch for every separate change you make. For
-example:
+```bash
+@test "foobar.txt was created" {
+  run cat /usr/local/foobar.txt
+  [ "$status" -eq 0 ]
+  [ "$output" = "hello" ]
+}
+```
 
-1. Fork the repo
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Added some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+See the [Bats documentation](https://bats-core.readthedocs.io) for the full
+assertion and helper vocabulary.
 
-## Authors
+Test Kitchen picks the plugin up from the suite directory name — no verifier
+configuration is needed beyond the default busser verifier.
 
-Created and maintained by [Fletcher Nichol][author] (<fnichol@nichol.ca>)
+## Using it with Test Kitchen
 
-## License
+This is how most people run it, and it needs no Busser commands of your own.
+Select the verifier in `kitchen.yml`:
+
+```yaml
+verifier:
+  name: busser
+
+suites:
+  - name: default
+```
+
+Then put your tests in a `bats` directory inside the suite:
 
-Apache 2.0 (see [LICENSE][license])
+```text
+test/integration/default/bats/default.bats
+```
 
-[Bats][bats_site] is released under an MIT-style license, copyright Sam Stephenson.
+`kitchen verify` installs Busser and this plugin on the instance and runs them.
+The directory name is what selects this plugin -- there is nothing else to
+configure.
+
+## When nothing runs
+
+If the suite files do not match what this plugin looks for, the run prints one
+line and **exits `0`**:
+
+```text
+-----> Running bats test suite
+```
+
+No tests ran, and nothing said so. Work through these in order:
+
+1. **Is the directory named `bats`?** That name alone selects this plugin.
+   `batss/`, `tests/` or anything else is not picked up.
+2. **Do the filenames match?** Every `*.bats` file in the directory is run
+   -- `smoke.sh` is *not* picked up.
+3. **Is the plugin installed?** `busser plugin list` shows what is available.
+4. **Is `BUSSER_ROOT` what you think?** `busser suite path` prints where suites
+   are actually being looked for.
+
+## Contributing
+
+Bug reports and pull requests are welcome. See
+[CONTRIBUTING.md](CONTRIBUTING.md) for how to set up the project, run the test
+suite, and format your commits.
+
+## License
 
+Apache License 2.0. See [LICENSE](LICENSE).
 
-[author]:           https://github.com/fnichol
-[issues]:           https://github.com/fnichol/busser-bats/issues
-[license]:          https://github.com/fnichol/busser-bats/blob/master/LICENSE
-[repo]:             https://github.com/fnichol/busser-bats
+The vendored copy of Bats is released under an MIT-style license, copyright Sam
+Stephenson and the bats-core contributors.
 
-[bats_site]:  https://github.com/sstephenson/bats
+Originally created by [Fletcher Nichol](https://github.com/fnichol).

data/Rakefile

@@ -1,12 +1,17 @@
 require "bundler/gem_tasks"
-require "open-uri"
-
 namespace :bats do
-  version = ENV.fetch("BATS_VERSION", "v0.4.0")
-  url = "https://github.com/sstephenson/bats/archive/#{version}.tar.gz"
+  # bats moved. sstephenson/bats was archived in 2016 at v0.4.0; bats-core is
+  # the maintained fork and where every release since has come from.
+  version = ENV.fetch("BATS_VERSION", "v1.14.0")
+  url = "https://github.com/bats-core/bats-core/archive/refs/tags/#{version}.tar.gz"
   tarball = "tmp/bats-#{version}.tar.gz"
   vendor = "vendor/bats"
 
+  # install.sh needs bin, libexec, lib and the two man pages. Everything else in
+  # the tarball -- the test suite, the docs site, Docker and CI scaffolding --
+  # is weight in a gem that gets copied onto every machine under test.
+  keep = %w{bin libexec lib man install.sh uninstall.sh LICENSE.md README.md}
+
   desc "Vendors bats #{version} source code into gem codebase"
   task vendor: "#{vendor}/VERSION.txt"
 
@@ -14,19 +19,16 @@ namespace :bats do
   directory vendor
 
   file tarball => File.dirname(tarball) do |t|
-    src = open(url).binmode
-    dst = open(t.name, "wb")
-    IO.copy_stream(src, dst)
-  ensure
-    src.close
-    dst.close
+    sh "curl", "--fail", "--silent", "--location", url, "--output", t.name
   end
 
   file "#{vendor}/VERSION.txt" => [vendor, tarball] do |t|
     abs_tarball = File.expand_path(tarball)
-    Dir.chdir(vendor) { sh "tar xzf #{abs_tarball} --strip-components=1" }
-    rm_rf "#{vendor}/test"
-    IO.write(t.name, url + "\n")
+    Dir.chdir(vendor) do
+      sh "tar", "xzf", abs_tarball, "--strip-components=1"
+      (Dir.glob("*", File::FNM_DOTMATCH) - [".", "..", *keep]).each { |f| rm_rf(f) }
+    end
+    File.write(t.name, "#{url}\n")
   end
 
   desc "Clean up a vendored bats in preparation for a new vendored version"
@@ -35,20 +37,37 @@ namespace :bats do
   end
 end
 
+require "rake/testtask"
+Rake::TestTask.new(:unit) do |t|
+  t.libs.push "lib"
+  t.test_files = FileList["spec/**/*_spec.rb"]
+  t.verbose = true
+end
+
 require "cucumber/rake/task"
 Cucumber::Rake::Task.new(:features) do |t|
-  t.cucumber_opts = ["features", "-x", "--format progress"]
+  t.cucumber_opts = ["features", "--format progress", "--fail-fast"]
 end
 
-desc "Run all test suites"
-task test: [:features]
-
-desc "Display LOC stats"
-task :stats do
-  puts "\n## Production Code Stats"
-  sh "countloc -r lib"
-  puts "\n## Test Code Stats"
-  sh "countloc -r features"
+# yard lives in the :development group, which CI omits when it runs the tests.
+# Requiring it unconditionally would make `rake test` fail there, so the real
+# task is only defined when yard is installed and a stub explains its absence
+# otherwise. Nothing in CI gates on documentation.
+begin
+  require "yard"
+
+  YARD::Rake::YardocTask.new(:doc) do |t|
+    t.files = ["lib/**/*.rb"]
+    t.options = ["--output-dir", "doc", "--markup", "markdown"]
+  end
+rescue LoadError
+  desc "Generate YARD documentation (install the development group first)"
+  task :doc do
+    abort "yard is not available. Run `bundle install --with development` first."
+  end
 end
 
-task default: %i{test quality}
+desc "Run all test suites"
+task test: %i{unit features}
+
+task default: %i{test}

data/busser-bats.gemspec

@@ -1,22 +1,30 @@
 lib = File.expand_path("lib", __dir__)
 $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 require "busser/bats/version"
-require "English"
 
-Gem::Specification.new do |gem|
-  gem.name          = "busser-bats"
-  gem.version       = Busser::Bats::VERSION
-  gem.authors       = ["Fletcher Nichol"]
-  gem.email         = ["fnichol@nichol.ca"]
-  gem.description   = "A Busser runner plugin for Bats"
-  gem.summary       = gem.description
-  gem.homepage      = "https://github.com/test-kitchen/busser-bats"
-  gem.license       = "Apache 2.0"
+Gem::Specification.new do |spec|
+  spec.name          = "busser-bats"
+  spec.version       = Busser::Bats::VERSION
+  spec.authors       = ["Fletcher Nichol"]
+  spec.email         = ["fnichol@nichol.ca"]
+  spec.description   = "A Busser runner plugin for Bats"
+  spec.summary       = spec.description
+  spec.homepage      = "https://github.com/test-kitchen/busser-bats"
+  spec.license       = "Apache-2.0"
 
-  gem.files         = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
-  gem.executables   = []
-  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
-  gem.require_paths = ["lib"]
+  spec.required_ruby_version = ">= 3.2"
 
-  gem.add_dependency "busser"
+  spec.files         = `git ls-files -z`.split("\x0")
+  spec.executables   = []
+  spec.require_paths = ["lib"]
+
+  spec.metadata = {
+    "bug_tracker_uri" => "#{spec.homepage}/issues",
+    "changelog_uri" => "#{spec.homepage}/blob/main/CHANGELOG.md",
+    "documentation_uri" => "#{spec.homepage}/blob/main/README.md",
+    "homepage_uri" => spec.homepage,
+    "source_code_uri" => spec.homepage,
+  }
+
+  spec.add_dependency "busser", ">= 0.9.0"
 end

data/config/features/support/env.rb

@@ -1,11 +1,6 @@
 require "aruba/cucumber"
 require "busser/cucumber"
 
-if ENV["COVERAGE"]
-  require "simplecov"
-  SimpleCov.command_name "features"
-end
-
 Before do
   @aruba_timeout_seconds = 20
 end