specguard-rspec 0.2.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 8df0db27fb3830ed9d13feb79f169746ca21b6985bc62b84a69d7285425e1cb6
+  data.tar.gz: a2e9c814cac4514eb74eda9e0ae56fafb0e6aa2bf2ff204ee5eae1fd5af92729
+SHA512:
+  metadata.gz: 26c40b33f81916fc72014d2b96f34d65326af41583e0095c12db91759b64d742c766db8e138bc127b298002f067176ad19753d28f538c6b544d5d38fcf1dc4d1
+  data.tar.gz: 010c652c2f9ef9fc44fc5deeca844d0704da92b4cb719a35e28b85faab0456c0db4c7c16bf79a7408d8911b00dd4377bcdcc2953c5f0bff04a51de628175f2f0

data/.github/workflows/release.yml

@@ -0,0 +1,100 @@
+# Release specguard-rspec. Triggered manually from the Actions UI ("Run
+# workflow" button) — no tags, no push triggers. Click → run the suite → bump
+# patch version → build the gem → push to RubyGems → publish a GitHub Release.
+#
+# Mirrors warden's release strategy (one-click workflow_dispatch, patch bump by
+# script/bump-version.sh, github-actions[bot] commit, assets on the vX.Y.Z tag),
+# with one addition that the others do not need: this repo publishes to a public
+# package registry, and **a published gem version is immutable**. RubyGems
+# refuses a re-push of the same number, and yanking does not free it. So the
+# suite runs BEFORE the bump — a red build costs nothing, a bad push costs the
+# version forever.
+#
+# Required repo secret:
+#   RUBYGEMS_API_KEY - an API key from rubygems.org with the "Push rubygem"
+#                      scope, ideally scoped to the specguard-rspec gem.
+name: Release (Bump Version & Publish Gem)
+
+on:
+  workflow_dispatch:        # one-click from Actions UI; no inputs needed
+
+permissions:
+  contents: write           # bump commit + vX.Y.Z tag + GitHub Release
+
+jobs:
+  release:
+    name: Test, bump, publish
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout main
+        uses: actions/checkout@v4
+        with:
+          ref: main
+          token: ${{ secrets.GITHUB_TOKEN }}
+          fetch-depth: 0      # full history for the rebase-and-push, and tags
+                              # so bump-version.sh's tag-reuse check is real
+
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.2'
+          bundler-cache: true
+
+      # Before the bump on purpose: see the header. This is the last point at
+      # which failing is free.
+      - name: Run the suite
+        run: bundle exec rspec
+
+      - name: Fail early if the publish credential is missing
+        # gem push with no credential fails AFTER the bump has been committed,
+        # tagged and pushed — leaving a released-looking tag with nothing on
+        # RubyGems. Check first; the version number is not recoverable.
+        run: |
+          if [ -z "${{ secrets.RUBYGEMS_API_KEY }}" ]; then
+            echo "::error::RUBYGEMS_API_KEY is not set — refusing to bump a version that cannot be published"
+            exit 1
+          fi
+
+      - name: Configure Git
+        run: |
+          git config --global user.name  "github-actions[bot]"
+          git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
+
+      - name: Bump version (commit + tag + push)
+        id: bump
+        run: |
+          # setup-ruby's bundler-cache rewrites Gemfile.lock, and the suite may
+          # leave artefacts behind; show what the tree looks like before the
+          # script's clean-tree check runs, so a refusal here is diagnosable
+          # from the log rather than only reproducible by re-running.
+          echo "--- git status ---"
+          git status --porcelain
+          echo "------------------"
+          chmod +x script/bump-version.sh
+          ./script/bump-version.sh
+
+      - name: Build the gem
+        run: gem build specguard-rspec.gemspec
+
+      - name: Push to RubyGems
+        env:
+          GEM_HOST_API_KEY: ${{ secrets.RUBYGEMS_API_KEY }}
+        run: gem push "specguard-rspec-${{ steps.bump.outputs.version }}.gem"
+
+      - name: Publish GitHub Release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          gh release create "${{ steps.bump.outputs.tag }}" \
+            --title "${{ steps.bump.outputs.tag }}" \
+            --notes "Published to RubyGems as \`specguard-rspec ${{ steps.bump.outputs.version }}\`.
+
+          \`\`\`ruby
+          # Gemfile
+          group :test do
+            gem \"specguard-rspec\", \"~> ${{ steps.bump.outputs.version }}\", require: false
+          end
+          \`\`\`
+
+          Two independent tools: an additive RSpec formatter that ships test-run telemetry, and \`specguard-lint\`, which validates OpenTestIntent \`@intent\` annotations." \
+            "specguard-rspec-${{ steps.bump.outputs.version }}.gem"

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 yatfa
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.