sanitize_email 2.0.2 → 2.0.4

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 82a7d76730f21c110754deb5dad21214eaee70a24ff7e92c6e284182881da13d
4
- data.tar.gz: ead74f1cd6c3d6587f850269393856a5bcc2e8aff247bafc9d69108d1eed7271
3
+ metadata.gz: d3ded29cb641327aee8c303ec9eb805fac032b68d3d82b7791e542c03577f05d
4
+ data.tar.gz: 97ee5eb56dd5b88498c2e9e9054609960927453ce52b8740113380b2935208d8
5
5
  SHA512:
6
- metadata.gz: d2028df00162c856e68736b98ecb54041d2a4db1bc094706f779a27e7747bc82e9fa5acb755f86d8e2ad24ae18ceff88906fde728c2c847a79124be84da9af80
7
- data.tar.gz: 28ee29a3ff23ff4bdb21ead8d4016e2419bcb00222df00c4d27e42ba43d0096100aab8459607533f8725ae3fc43219efe5c367684e65deed44f4d07e7e4c256d
6
+ metadata.gz: 21b23105d986537545b5c99738843dd7f16ff84626b6bffdb8870d6f479020084944abd1a4907ccf0eb9db07e3d37ae8756284bb223178f55ee0585ef041609f
7
+ data.tar.gz: 94c2a2944691dcced263a0db6d1af7c17d2e36d64820c90512938b642f247c299831c0be35ff5c7827b1c87ecbfd212052dcc22f119c5cdc70f037baea247bf4
checksums.yaml.gz.sig ADDED
@@ -0,0 +1,3 @@
1
+ ��vJ1�����%��8������}Io3"
2
+ ��Ϋ#����?���@2��:��t+���x6˾W12FL������żۛiXy��Y�)i:-���O�7j=��"�X->`��m_`sϗ��@+�@����BD%^� ����Uز"�O����`R}n�
3
+ � 'j�:�8c>C�Y��z1���a.�/�L�N2q��2>�x?'�}�y�D�P�z��p�I�wQ�T�90�u��Õ+�����}}�F�=ؒ�
data/CHANGELOG.md CHANGED
@@ -1,13 +1,71 @@
1
- HEAD
2
-
3
- *UNRELEASED*
4
- * Drop support for MRI Ruby 1.9, 2.0, 2.1, and 2.2 by Peter Boling
5
- * Drop support for JRuby 1.7 and 9.0, while still supporting 9.1 by Peter Boling
6
- * Drop support for Rails 3.0, 3.1, 3.2, 4.0, 4.1, while still supporting 4.2 by Peter Boling
7
- * Add testing for Rails 5.1 and 5.2 by Peter Boling
8
-
9
- Version 1.2.2 - FEB.17.2017
10
- * Improve handling of frozen strings, which are becoming more common by @milgner
1
+ # Changelog
2
+ All notable changes to this project will be documented in this file.
3
+
4
+ Since version 2.0.0, the format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
5
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
+
7
+ ## [Unreleased]
8
+ ### Added
9
+ ### Changed
10
+ ### Fixed
11
+ ### Removed
12
+
13
+ ## [2.0.4] - 2024-03-22 ([tag][2.0.4t])
14
+ ### Added
15
+ * mail gem dependency (@pboling)
16
+ * version_gem dependency (@pboling)
17
+ * new RSpec Matchers (@pboling)
18
+ * `have_sanitized_to_header`
19
+ * `have_sanitized_cc_header`
20
+ * Contributor [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) (@pboling)
21
+ * Security Policy in [SECURITY.md](SECURITY.md) (@pboling)
22
+ * More documentation (@pboling)
23
+ ### Changed
24
+ * Switched from Travis-CI to GitHub Actions
25
+ * Testing for
26
+ ### Fixed
27
+ * [#64](https://github.com/pboling/sanitize_email/issues/64) Automatically dedup recipients in cascading fashion: To > CC > BCC (@pboling)
28
+ * Set sanitized email headers with decoded values from Mail gem
29
+ ### Removed
30
+ * Dependency on git in gemspec (@pboling)
31
+ * Coveralls development gem dependecy
32
+
33
+ ## [2.0.3] - 2018-09-08 ([tag][2.0.3t])
34
+ ### Changed
35
+ * Nothing
36
+
37
+ ## [2.0.2] - 2018-09-08 ([tag][2.0.2t])
38
+ ### Added
39
+ * More and fixed badges (@pboling)
40
+ * Code Coverage reporting (@pboling)
41
+ ### Changed
42
+ * begin following SemVer for dependency requirements (@pboling)
43
+ ### Fixed
44
+ * [#47](https://github.com/pboling/sanitize_email/pull/47) Don't use #prepend on subject (@mslade-fairfax)
45
+ ### Removed
46
+ * Ability to install on Ruby 2.2 (@pboling)
47
+
48
+ ## [2.0.1] - 2018-03-07 ([tag][2.0.1t])
49
+ ### Fixed
50
+ * [#32](https://github.com/pboling/sanitize_email/pull/32) A better fix for the frozen subject bug (@pboling)
51
+ ### Removed
52
+ * Ruby 2.2 is really no longer supported (@pboling)
53
+
54
+ ## [2.0.0] - 2018-03-07 ([tag][2.0.0t])
55
+ ### Added
56
+ * Add testing for Rails 5.1 and 5.2 (@pboling)
57
+ * More and fixed badges (@pboling)
58
+ ### Changed
59
+ * Drop support for MRI Ruby 1.9, 2.0, 2.1, and 2.2 (@pboling)
60
+ * Drop support for JRuby 1.7 and 9.0, while still supporting 9.1 (@pboling)
61
+ * Drop support for Rails 3.0, 3.1, 3.2, 4.0, 4.1, while still supporting 4.2 (@pboling)
62
+ ### Fixed
63
+ * Frozen subject bug (@pboling)
64
+ ### Removed
65
+ * Ruby 2.2 is no longer supported (@pboling)
66
+
67
+ Version 1.2.2 - FEB.20.2017
68
+ * Improve handling of frozen strings, which are becoming more common (@milgner)
11
69
 
12
70
  Version 1.2.1 - NOV.03.2016
13
71
  * 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
162
220
 
163
221
  Version 1.0.0.rc1
164
222
 
165
- * Added a good_list and a bad_list (whitelist and blacklist)
223
+ * Added a good_list and a bad_list (i.e. allowlist and blocklist)
166
224
  * Added Deprecation library
167
225
  * Refactored Sanitization module into Hook class
168
226
  * Renamed Hook Class to Bleach Class
@@ -178,7 +236,7 @@ Version 1.0.0.alpha2
178
236
  * NinthBit namespace is now SanitizeEmail namespace
179
237
  * Now has a first class Config class
180
238
 
181
- XXXXXXXXXXXXXXXXXXXXXXX Rail 3.0+ Only Form here on up! XXXXXXXXXXXXXXXXXXXXXXX
239
+ XXXXXXXXXXXXXXXXXXXXXXX Rails 3.0+ Only From here on up! XXXXXXXXXXXXXXXXXXXXXXX
182
240
 
183
241
  Version 0.3.8
184
242
 
@@ -201,3 +259,15 @@ Old version?
201
259
 
202
260
  * Fixed require paths
203
261
  * added about.yml and this CHANGELOG
262
+
263
+ [Unreleased]: https://github.com/pboling/sanitize_email/compare/v2.0.4...HEAD
264
+ [2.0.4]: https://github.com/pboling/sanitize_email/compare/v2.0.3...v2.0.4
265
+ [2.0.4t]: https://github.com/pboling/sanitize_email/tags/v2.0.4
266
+ [2.0.3]: https://github.com/pboling/sanitize_email/compare/v2.0.2...v2.0.3
267
+ [2.0.3t]: https://github.com/pboling/sanitize_email/tags/v2.0.3
268
+ [2.0.2]: https://github.com/pboling/sanitize_email/compare/v2.0.1...v2.0.2
269
+ [2.0.2t]: https://github.com/pboling/sanitize_email/tags/v2.0.2
270
+ [2.0.1]: https://github.com/pboling/sanitize_email/compare/v2.0.0...v2.0.1
271
+ [2.0.1t]: https://github.com/pboling/sanitize_email/tags/v2.0.1
272
+ [2.0.0]: https://github.com/pboling/sanitize_email/compare/v1.2.2...v2.0.0
273
+ [2.0.0t]: https://github.com/pboling/sanitize_email/tags/v2.0.0
@@ -0,0 +1,84 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ 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.
6
+
7
+ We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
8
+
9
+ ## Our Standards
10
+
11
+ Examples of behavior that contributes to a positive environment for our community include:
12
+
13
+ * Demonstrating empathy and kindness toward other people
14
+ * Being respectful of differing opinions, viewpoints, and experiences
15
+ * Giving and gracefully accepting constructive feedback
16
+ * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
+ * Focusing on what is best not just for us as individuals, but for the overall community
18
+
19
+ Examples of unacceptable behavior include:
20
+
21
+ * The use of sexualized language or imagery, and sexual attention or
22
+ advances of any kind
23
+ * Trolling, insulting or derogatory comments, and personal or political attacks
24
+ * Public or private harassment
25
+ * Publishing others' private information, such as a physical or email
26
+ address, without their explicit permission
27
+ * Other conduct which could reasonably be considered inappropriate in a
28
+ professional setting
29
+
30
+ ## Enforcement Responsibilities
31
+
32
+ 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.
33
+
34
+ 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.
35
+
36
+ ## Scope
37
+
38
+ 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.
39
+
40
+ ## Enforcement
41
+
42
+ 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.
43
+
44
+ All community leaders are obligated to respect the privacy and security of the reporter of any incident.
45
+
46
+ ## Enforcement Guidelines
47
+
48
+ Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
49
+
50
+ ### 1. Correction
51
+
52
+ **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
53
+
54
+ **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.
55
+
56
+ ### 2. Warning
57
+
58
+ **Community Impact**: A violation through a single incident or series of actions.
59
+
60
+ **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.
61
+
62
+ ### 3. Temporary Ban
63
+
64
+ **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
65
+
66
+ **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.
67
+
68
+ ### 4. Permanent Ban
69
+
70
+ **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.
71
+
72
+ **Consequence**: A permanent ban from any sort of public interaction within the community.
73
+
74
+ ## Attribution
75
+
76
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
77
+ available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
78
+
79
+ Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
80
+
81
+ [homepage]: https://www.contributor-covenant.org
82
+
83
+ For answers to common questions about this code of conduct, see the FAQ at
84
+ https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,47 @@
1
+ ## Contributing
2
+
3
+ Bug reports and pull requests are welcome on GitHub at [https://github.com/pboling/sanitize_email][🚎src-main]
4
+ . This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
5
+ the [code of conduct][🤝conduct].
6
+
7
+ To submit a patch, please fork the project and create a patch with tests. Once you're happy with it send a pull request
8
+ and post a message to the [gitter chat][🏘chat].
9
+
10
+ ## Release
11
+
12
+ To release a new version:
13
+
14
+ 1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check
15
+ 2. Update the version number in `version.rb`
16
+ 3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
17
+ 4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
18
+ 5. Run `git push` to trigger the final CI pipeline before release, & merge PRs
19
+ a. NOTE: Remember to [check the build][🧪build]!
20
+ 6. Run `git checkout main` (Or whichever branch is considered `trunk`, e.g. `master`)
21
+ 7. Run `git pull origin main` to ensure you will release the latest trunk code.
22
+ 8. Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use same timestamp, and generate same checksums
23
+ a. Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS` (you'll need the zsh/datetime module, if running zsh)
24
+ 9. Run `bundle exec rake build`
25
+ 10. Run [`bin/checksums`](https://github.com/rubygems/guides/pull/325) to create SHA-256 and SHA-512 checksums
26
+ a. Checksums will be committed automatically by the script, but not pushed
27
+ 11. Run `bundle exec rake release` which will create a git tag for the version,
28
+ push git commits and tags, and push the `.gem` file to [rubygems.org][💎rubygems]
29
+
30
+ NOTE: You will need to have a public key in `certs/`, and list your cert in the
31
+ `gemspec`, in order to sign the new release.
32
+ See: [RubyGems Security Guide][🔒️rubygems-security-guide]
33
+
34
+ ## Contributors
35
+
36
+ [![Contributors](https://contrib.rocks/image?repo=pboling/sanitize_email)][🖐contributors]
37
+
38
+ Made with [contributors-img][🖐contrib-rocks].
39
+
40
+ [🧪build]: https://github.com/pboling/sanitize_email/actions
41
+ [🏘chat]: https://matrix.to/#/#pboling_sanitize_email:gitter.im
42
+ [🤝conduct]: https://github.com/pboling/sanitize_email/blob/main/CODE_OF_CONDUCT.md
43
+ [🖐contrib-rocks]: https://contrib.rocks
44
+ [🖐contributors]: https://github.com/pboling/sanitize_email/graphs/contributors
45
+ [💎rubygems]: https://rubygems.org
46
+ [🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
47
+ [🚎src-main]: https://github.com/pboling/sanitize_email
@@ -1,6 +1,6 @@
1
1
  MIT License
2
2
 
3
- Copyright (c) 2008 - 2018 Peter H. Boling, http://railsbling.com
3
+ Copyright (c) 2008 - 2018, 2024 Peter H. Boling, http://railsbling.com
4
4
 
5
5
  Permission is hereby granted, free of charge, to any person obtaining a copy
6
6
  of this software and associated documentation files (the "Software"), to deal