simplycop 2.42.0 → 2.42.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 15025c48c319e254bf2a2a9ab8ce3046a0f3884265951ec4b1a910bc870d7ff1
-  data.tar.gz: 1dfef42348722c0f3640a275e10f5a1666b2676979f208c06299203afa00a8d8
+  metadata.gz: eb25f96ac78cff744a69b8a59c401d35a912332b8ff46a8e4d70ecbbd5f417b1
+  data.tar.gz: 39a304d2fcb5a6e552e908d05e31e514170d3cfbfd4acf5f1c43d2510e41091c
 SHA512:
-  metadata.gz: 04cc60d11999e3390cdc25a67b739bd0847ab929ade54c40244689c13309734627719547849872194b5a0e06118110c3d7f82b9ae1dfc5de104f0a4cc79d614b
-  data.tar.gz: d9d0fc8dcabd8b57654b1c98fa0d522fefe2884188a9de523e2205a1344c95a2d0ab421e2c9e27fcbd3a33865d80a3f80d32314cec670cb33422b7281cbd279c
+  metadata.gz: d5d4f1d95416cd0720cff0efd4d906c43e2f6a4580cf80654f22b672e1be1dd38c0e6cd88bb2054a42875abf68bb1c3c59d921e1495d798da727c4011aee29e1
+  data.tar.gz: 6892eb7441bf17c44d08a344aba5960e0572885793ff72d5cc7c437a0070070a083d5bcd85818c907fce606fedf5f816e5da2052d2bfd489c8b0a606e43d57d5

data/.github/workflows/update-codacy.yml

@@ -40,8 +40,8 @@ jobs:
           gem-version: ${{ steps.version.outputs.version }}
           codacy-token: ${{ secrets.CODACY_TOKEN }}
           github-token: ${{ secrets.GITHUB_TOKEN }}
-          dry-run: 'true'
-          set-as-default: 'false'
+          dry-run: 'false'
+          set-as-default: 'true'
       
       - name: Print Summary
         env:

data/.simplycop_style.yml

@@ -74,6 +74,8 @@ Style/CaseLikeIf:
 Style/CharacterLiteral:
   Enabled: true
 
+# When enabled, this causes errors in Codacy after our config has been converted to their format.
+# The problem is on their end and has not been resolved as of 17/2/26.
 Style/ClassAndModuleChildren:
   Enabled: false
 

data/docs/index.md

@@ -306,7 +306,55 @@ If you prefer to manually version, you can do so by editing the `lib/simplycop/v
 
 ## Simplycop & Codacy
 
-Codacy's Rubocop configuration may not be fully up-to-date with Simplycop. Therefore you may find things pass in your local Simplycop run that then fail in the CI/CD pipeline. This will mainly be the case for newer cops that have been added. If this causes major issues for your PR, please consult engineering leads to arrange a Codacy override.
+### Codacy Integration Overview
+
+Simplycop configurations are automatically synchronized with Codacy to ensure consistent code quality checks across the organization. This integration keeps Codacy's RuboCop analysis aligned with the latest Simplycop rules and configurations.
+
+### Pipeline Workflow
+
+When a new version of Simplycop is released, the following automated process occurs:
+
+1. **Release Trigger**: The "Create GitHub Release" workflow completes successfully on the master branch
+2. **Delay Period**: A 20-second delay ensures the gem release is fully published and available
+3. **Version Extraction**: The pipeline extracts the new version number from `lib/simplycop/version.rb`
+4. **Codacy Update**: The `codacy-simplycop-update-action` is invoked to:
+   - Create or update a Codacy coding standard with the new Simplycop configuration
+   - Apply the patterns from the new version to all repositories
+   - Migrate repositories to use the new standard
+   - Disable any outdated Simplycop standards in Codacy
+5. **Summary Report**: A summary is generated showing:
+   - The Simplycop version deployed
+   - The coding standard name created
+   - Number of patterns applied
+   - Number of repositories migrated
+   - Number of old standards disabled
+
+This automation ensures that all projects using Codacy for code quality checks will automatically receive the latest Simplycop rules without manual intervention.
+
+### Configuration Considerations
+
+**RuboCop Version Compatibility**: Codacy's RuboCop container may lag behind the latest RuboCop version. This can occasionally cause:
+- Warnings about deprecated configuration syntax (e.g., `require:` vs `plugins:` for extensions)
+- Errors with newer configuration options not yet supported by Codacy's version
+
+**Handling Codacy-Specific Issues**: 
+
+**Important**: Codacy ignores repository-specific RuboCop configuration, including local `.rubocop.yml` overrides and `.rubocop_todo.yml` files. This means code may pass locally but fail in the Codacy pipeline because:
+- Rules you've disabled or overridden in your local configuration are still enforced by Codacy
+- Violations listed in `.rubocop_todo.yml` are not ignored by Codacy
+- Codacy uses only the centrally-managed Simplycop configuration
+
+If you encounter issues where code passes locally but fails in Codacy:
+1. **Check for local overrides**: Review your `.rubocop.yml` and `.rubocop_todo.yml` for disabled cops or relaxed settings that Codacy doesn't respect
+2. **Fix violations**: Address the violations reported by Codacy, even if they're locally disabled
+3. **Request Codacy override**: If a rule causes significant issues across your project, consult engineering leads to arrange a Codacy-level override
+4. **Wait for updates**: For new Simplycop releases, the automatic Codacy update pipeline usually completes within minutes
+
+### Monitoring Updates
+
+To track Codacy configuration updates:
+- Check the [GitHub Actions workflow runs](https://github.com/simplybusiness/simplycop/actions/workflows/update-codacy.yml) for the "Update Codacy Configuration" workflow
+- Review the workflow summary for details about applied patterns and migrated repositories
 
 ## FAQ
 

data/lib/simplycop/version.rb

@@ -7,5 +7,5 @@
 #
 
 module Simplycop
-  VERSION = '2.42.0'
+  VERSION = '2.42.1'
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: simplycop
 version: !ruby/object:Gem::Version
-  version: 2.42.0
+  version: 2.42.1
 platform: ruby
 authors:
 - Simply Business
 bindir: bin
 cert_chain: []
-date: 2026-02-16 00:00:00.000000000 Z
+date: 2026-02-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: benchmark