sanitize_email 2.0.3 → 2.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e25f12614ad4231a0be13d8f6f22a48830f24be382bf03196240d3d08616c682
-  data.tar.gz: 67387be7fac711a737820749837f066a42edd18a781dc5bb43223d9f0a51afa1
+  metadata.gz: d3ded29cb641327aee8c303ec9eb805fac032b68d3d82b7791e542c03577f05d
+  data.tar.gz: 97ee5eb56dd5b88498c2e9e9054609960927453ce52b8740113380b2935208d8
 SHA512:
-  metadata.gz: a25b33b344cc858fc87635716cdd02a6f3bedc923778ed26670a26dc6024b64e7a63776fb6c2b9ec03d41d606f50d35a6e1216b879e18bfc412f76b920f9714a
-  data.tar.gz: 2b6df4a108d72e20ed38089898dc1443c53c985843faa86091d7d71c2e5dda4b79dde123dc0672f55d17822804bf5cee0174dc537c3a64c949010b923a26de32
+  metadata.gz: 21b23105d986537545b5c99738843dd7f16ff84626b6bffdb8870d6f479020084944abd1a4907ccf0eb9db07e3d37ae8756284bb223178f55ee0585ef041609f
+  data.tar.gz: 94c2a2944691dcced263a0db6d1af7c17d2e36d64820c90512938b642f247c299831c0be35ff5c7827b1c87ecbfd212052dcc22f119c5cdc70f037baea247bf4

checksums.yaml.gz.sig

@@ -0,0 +1,3 @@
+��vJ1�����%��8������}Io3"
+��Ϋ#����?���@2��:��t+���x6˾W12FL�
�����żۛiXy��Y�)i:-���O�7j=��"�X->`��m_`sϗ��@+�@����BD%^� ����Uز"�O����`R}n�
+� 'j�:�8c>C�Y��z1���a.�/�L�N2q��2>�x?'�}�y�D�P�z��p�I�wQ�T�90�u��Õ+�����}}�F�=ؒ�

data/CHANGELOG.md

@@ -1,13 +1,71 @@
-HEAD
-
-*UNRELEASED*
-* Drop support for MRI Ruby 1.9, 2.0, 2.1, and 2.2 by Peter Boling
-* Drop support for JRuby 1.7 and 9.0, while still supporting 9.1 by Peter Boling
-* Drop support for Rails 3.0, 3.1, 3.2, 4.0, 4.1, while still supporting 4.2 by Peter Boling
-* Add testing for Rails 5.1 and 5.2 by Peter Boling
-
-Version 1.2.2 - FEB.17.2017
-* Improve handling of frozen strings, which are becoming more common by @milgner
+# Changelog
+All notable changes to this project will be documented in this file.
+
+Since version 2.0.0, the format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+### Added
+### Changed
+### Fixed
+### Removed
+
+## [2.0.4] - 2024-03-22 ([tag][2.0.4t])
+### Added
+* mail gem dependency (@pboling)
+* version_gem dependency (@pboling)
+* new RSpec Matchers (@pboling)
+  * `have_sanitized_to_header`
+  * `have_sanitized_cc_header`
+* Contributor [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) (@pboling)
+* Security Policy in [SECURITY.md](SECURITY.md) (@pboling)
+* More documentation (@pboling)
+### Changed
+* Switched from Travis-CI to GitHub Actions
+  * Testing for
+### Fixed
+* [#64](https://github.com/pboling/sanitize_email/issues/64) Automatically dedup recipients in cascading fashion: To > CC > BCC (@pboling)
+* Set sanitized email headers with decoded values from Mail gem
+### Removed
+* Dependency on git in gemspec (@pboling)
+* Coveralls development gem dependecy
+
+## [2.0.3] - 2018-09-08 ([tag][2.0.3t])
+### Changed
+* Nothing
+
+## [2.0.2] - 2018-09-08 ([tag][2.0.2t])
+### Added
+* More and fixed badges (@pboling)
+* Code Coverage reporting (@pboling)
+### Changed
+* begin following SemVer for dependency requirements (@pboling)
+### Fixed
+* [#47](https://github.com/pboling/sanitize_email/pull/47) Don't use #prepend on subject (@mslade-fairfax)
+### Removed
+* Ability to install on Ruby 2.2 (@pboling)
+
+## [2.0.1] - 2018-03-07 ([tag][2.0.1t])
+### Fixed
+* [#32](https://github.com/pboling/sanitize_email/pull/32) A better fix for the frozen subject bug (@pboling)
+### Removed
+* Ruby 2.2 is really no longer supported (@pboling)
+
+## [2.0.0] - 2018-03-07 ([tag][2.0.0t])
+### Added
+* Add testing for Rails 5.1 and 5.2 (@pboling)
+* More and fixed badges (@pboling)
+### Changed
+* Drop support for MRI Ruby 1.9, 2.0, 2.1, and 2.2 (@pboling)
+* Drop support for JRuby 1.7 and 9.0, while still supporting 9.1 (@pboling)
+* Drop support for Rails 3.0, 3.1, 3.2, 4.0, 4.1, while still supporting 4.2 (@pboling)
+### Fixed
+* Frozen subject bug (@pboling)
+### Removed
+* Ruby 2.2 is no longer supported (@pboling)
+
+Version 1.2.2 - FEB.20.2017
+* Improve handling of frozen strings, which are becoming more common (@milgner)
 
 Version 1.2.1 - NOV.03.2016
 * Fix bug where non-array to address would not get prepended to subject when that feature is turned on
@@ -162,7 +220,7 @@ Version 1.0.0.rc2 - AUG.08.2012 - botched
 
 Version 1.0.0.rc1
 
-* Added a good_list and a bad_list (whitelist and blacklist)
+* Added a good_list and a bad_list (i.e. allowlist and blocklist)
 * Added Deprecation library
 * Refactored Sanitization module into Hook class
 * Renamed Hook Class to Bleach Class
@@ -178,7 +236,7 @@ Version 1.0.0.alpha2
 * NinthBit namespace is now SanitizeEmail namespace
 * Now has a first class Config class
 
-XXXXXXXXXXXXXXXXXXXXXXX Rail 3.0+ Only Form here on up! XXXXXXXXXXXXXXXXXXXXXXX
+XXXXXXXXXXXXXXXXXXXXXXX Rails 3.0+ Only From here on up! XXXXXXXXXXXXXXXXXXXXXXX
 
 Version 0.3.8
 
@@ -201,3 +259,15 @@ Old version?
 
 * Fixed require paths
 * added about.yml and this CHANGELOG
+
+[Unreleased]: https://github.com/pboling/sanitize_email/compare/v2.0.4...HEAD
+[2.0.4]: https://github.com/pboling/sanitize_email/compare/v2.0.3...v2.0.4
+[2.0.4t]: https://github.com/pboling/sanitize_email/tags/v2.0.4
+[2.0.3]: https://github.com/pboling/sanitize_email/compare/v2.0.2...v2.0.3
+[2.0.3t]: https://github.com/pboling/sanitize_email/tags/v2.0.3
+[2.0.2]: https://github.com/pboling/sanitize_email/compare/v2.0.1...v2.0.2
+[2.0.2t]: https://github.com/pboling/sanitize_email/tags/v2.0.2
+[2.0.1]: https://github.com/pboling/sanitize_email/compare/v2.0.0...v2.0.1
+[2.0.1t]: https://github.com/pboling/sanitize_email/tags/v2.0.1
+[2.0.0]: https://github.com/pboling/sanitize_email/compare/v1.2.2...v2.0.0
+[2.0.0t]: https://github.com/pboling/sanitize_email/tags/v2.0.0

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at peter.boling@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/CONTRIBUTING.md

@@ -0,0 +1,47 @@
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at [https://github.com/pboling/sanitize_email][🚎src-main]
+. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
+the [code of conduct][🤝conduct].
+
+To submit a patch, please fork the project and create a patch with tests. Once you're happy with it send a pull request
+and post a message to the [gitter chat][🏘chat].
+
+## Release
+
+To release a new version:
+
+1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check
+2. Update the version number in `version.rb`
+3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
+4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
+5. Run `git push` to trigger the final CI pipeline before release, & merge PRs
+   a. NOTE: Remember to [check the build][🧪build]!
+6. Run `git checkout main` (Or whichever branch is considered `trunk`, e.g. `master`)
+7. Run `git pull origin main` to ensure you will release the latest trunk code.
+8. Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use same timestamp, and generate same checksums
+   a. Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS` (you'll need the zsh/datetime module, if running zsh)
+9. Run `bundle exec rake build`
+10. Run [`bin/checksums`](https://github.com/rubygems/guides/pull/325) to create SHA-256 and SHA-512 checksums
+    a. Checksums will be committed automatically by the script, but not pushed
+11. Run `bundle exec rake release` which will create a git tag for the version,
+    push git commits and tags, and push the `.gem` file to [rubygems.org][💎rubygems]
+
+NOTE: You will need to have a public key in `certs/`, and list your cert in the
+`gemspec`, in order to sign the new release.
+See: [RubyGems Security Guide][🔒️rubygems-security-guide]
+
+## Contributors
+
+[![Contributors](https://contrib.rocks/image?repo=pboling/sanitize_email)][🖐contributors]
+
+Made with [contributors-img][🖐contrib-rocks].
+
+[🧪build]: https://github.com/pboling/sanitize_email/actions
+[🏘chat]: https://matrix.to/#/#pboling_sanitize_email:gitter.im
+[🤝conduct]: https://github.com/pboling/sanitize_email/blob/main/CODE_OF_CONDUCT.md
+[🖐contrib-rocks]: https://contrib.rocks
+[🖐contributors]: https://github.com/pboling/sanitize_email/graphs/contributors
+[💎rubygems]: https://rubygems.org
+[🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
+[🚎src-main]: https://github.com/pboling/sanitize_email

data/{LICENSE → LICENSE.txt}

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2008 - 2018 Peter H. Boling, http://railsbling.com
+Copyright (c) 2008 - 2018, 2024 Peter H. Boling, http://railsbling.com
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal