Release/2.0.9 (#122)

* 🔧 Cleanup coverage workflow

* 🔥 rails-caddy is long dead

* 🔖 Prepare release v2.0.9

.github/workflows/coverage.yml

@@ -4,13 +4,13 @@ env:
   K_SOUP_COV_MIN_BRANCH: 71
   K_SOUP_COV_MIN_LINE: 89
   K_SOUP_COV_MIN_HARD: true
+  K_SOUP_COV_DO: true
+  K_SOUP_COV_COMMAND_NAME: "RSpec Coverage"
 
 on:
   push:
     branches:
       - 'main'
-      - '*-stable'
-      - '*-dev'
     tags:
       - '!*' # Do not execute on tags
   pull_request:
@@ -62,7 +62,7 @@ jobs:
           ruby-version: "${{ matrix.ruby }}"
           rubygems: "${{ matrix.rubygems }}"
           bundler: "${{ matrix.bundler }}"
-          bundler-cache: true
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
 
       - name: CodeClimate Pre-build Notification
         run: cc-test-reporter before-build
@@ -89,7 +89,7 @@ jobs:
           hide_complexity: true
           indicators: true
           output: both
-          thresholds: '93 82'
+          thresholds: '90 71'
         continue-on-error: ${{ matrix.experimental != 'false' }}
 
       - name: Add Coverage PR Comment

CHANGELOG.md

@@ -10,17 +10,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Fixed
 ### Removed
 
+## [2.0.9] - 2024-11-09 ([tag][2.0.9t])
+- COVERAGE:  90.15% -- 247/274 lines in 8 files
+- BRANCH COVERAGE:  71.68% -- 81/113 branches in 8 files
+- 61.73% documented
+### Added
+* More & better documentation
+* Rails 8.0 to CI
+
 ## [2.0.8] - 2024-06-11 ([tag][2.0.8t])
 ### Fixed
-# [#110](https://github.com/pboling/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine (actual fix!)
+* [#110](https://github.com/pboling/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine (actual fix!)
 
 ## [2.0.7] - 2024-04-25 ([tag][2.0.7t])
 ### Added
 * More documentation
 ### Changed
 * Documentation is now via yard instead of rdoc
 ### Fixed
-# [#110](https://github.com/pboling/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine
+* [#110](https://github.com/pboling/sanitize_email/issues/110) - interceptor not working via Rails 6+ engine
 
 ## [2.0.6] - 2024-04-25 ([tag][2.0.6t])
 ### Added
@@ -303,7 +311,9 @@ Old version?
 * Fixed require paths
 * added about.yml and this CHANGELOG
 
-[Unreleased]: https://github.com/pboling/sanitize_email/compare/v2.0.8...HEAD
+[Unreleased]: https://github.com/pboling/sanitize_email/compare/v2.0.9...HEAD
+[2.0.9]: https://github.com/pboling/sanitize_email/compare/v2.0.8...v2.0.9
+[2.0.9t]: https://github.com/pboling/sanitize_email/tags/v2.0.9
 [2.0.8]: https://github.com/pboling/sanitize_email/compare/v2.0.7...v2.0.8
 [2.0.8t]: https://github.com/pboling/sanitize_email/tags/v2.0.8
 [2.0.7]: https://github.com/pboling/sanitize_email/compare/v2.0.6...v2.0.7

Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    sanitize_email (2.0.8)
+    sanitize_email (2.0.9)
       mail (~> 2.0)
       version_gem (~> 1.1, >= 1.1.4)
 

README.md

@@ -247,7 +247,7 @@ It's particularly helpful when you want to prevent the delivery of email (e.g. i
 
 ## Re-routing Email on a Staging or QA Server
 
-Another very important use case for me is to transparently re-route email generated from a staging or QA server to an appropriate person.  For example, it's common for us to set up a staging server for a client to use to view our progress and test out new features.  It's important for any email that is generated from our web application be delivered to the client's inbox so that they can review the content and ensure that it's acceptable.  Similarly, we set up QA instances for our own QA team and we use [rails-caddy](http://github.com/jtrupiano/rails-caddy) to allow each QA person to configure it specifically for them.
+Another very important use case for me is to transparently re-route email generated from a staging or QA server to an appropriate person.  For example, it's common for us to set up a staging server for a client to use to view our progress and test out new features.  It's important for any email that is generated from our web application be delivered to the client's inbox so that they can review the content and ensure that it's acceptable.  `dotenv` or `direnv` allows each developer to configure the local behavior specifically for them via ENV vars.
 
 ## Testing Email from a Hot Production Server
 

lib/sanitize_email/version.rb

@@ -5,6 +5,6 @@
 
 module SanitizeEmail
   module Version
-    VERSION = "2.0.8"
+    VERSION = "2.0.9"
   end
 end