rspec-block_is_expected 1.0.4 → 1.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a811433ebee4f90c89a910b8943d64eebf7382707a7cc816ac98457111d4c1de
-  data.tar.gz: 46988de21adb0276656dbdc4a08dcccda9130898b6a6f312da05e6764b680661
+  metadata.gz: 29d909e2873766b37f4471c2aed8edf9078432b514f964ae8cab5e534e89a4e2
+  data.tar.gz: e83daabfe2ba4bf79bb085c816b02bf033e9367285d52a315db41a0b7ed9fc6c
 SHA512:
-  metadata.gz: 9670493137ff9827d1b72de9c29e2c317923d34040e6ad681183ea1bec578481b9f31c21a5173f7c8fa35929b6e9373ba8296cf4a043c78d5511e3f9672129ee
-  data.tar.gz: 63af4754c61daf83d23eae24f853f7ed91ba05c741c8f4f0ca772e96040f56d22bd0ef76ebee9188bdfca0ee37a62caa7ac1412080a696842183d46424630031
+  metadata.gz: e2ddbefcfec8932992996837096e1f64af24ff09a1777fa278d6f880ca3c553758d0f8b3edf841bb0dd4efa4a0855a9a36392a7a1a2c774dd4185f863705d192
+  data.tar.gz: 9adad062146654efa05b2cfb61706afead7a763b9c8b52a153b824cf5550f16b17116c000f97093c90691b89c1a2a0becc145edc96a2e335254084edbfe3bf04

data/CHANGELOG.md

@@ -1,5 +1,5 @@
 # Changelog
-All notable changes to this project will be documented in this file.
+All notable changes to this project since v1.0.3 will be documented in this file.
 
 The format is based on [Keep a Changelog v1](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.0.0.html).
@@ -10,16 +10,60 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 ### Fixed
 ### Removed
 
-## [1.0.4] - 2023-03-23
+## [1.0.6] 2024-06-23 ([tag][1.0.6t])
+### Added
+- Security policy (SECURITY.md)
+- Random ordering of test suite
+- shared examples:
+  - `block_is_expected to not raise`
+  - `block_is_expected to raise error`
+- Appraisals for testing on every Ruby supported by GHA (2.0 - 3.3)
+- Signed release
+
+## [1.0.5] - 2023-04-01 ([tag][1.0.5t])
+### Added
+- Structured gemfiles
+- Rubocop with standard, gradual, & more
+- Releases are now signed
+- Releases now have checksums
+### Changed
+- TravisCI => GitHub Actions
+- CODE_OF_CONDUCT.md upgraded to v2.0
+- Moved from master to main default branch
+### Fixed
+- README Badges (CI status)
+
+## [1.0.4] - 2023-03-23 ([tag][1.0.4t])
 ### Added
 - Required ruby version in gemspec >= 1.8.7
+  - not bumping major version, because this was already the de-facto minimum
 ### Changed
 - Moved rubocop config to root
 ### Fixed
 - documentation of rubocop config
 - Copyright years
 
-## [1.0.3] - 2023-03-23
+## [1.0.3] - 2023-03-23 ([tag][1.0.3t])
 ### Added
 - negated matchers
 - rubocop config
+
+## [1.0.2] - 2018-10-03
+
+## [1.0.1] - 2018-10-01
+
+## 1.0.0 - 2018-10-01
+### Added
+- Initial Release
+
+[Unreleased]: https://github.com/pboling/rspec-block_is_expected/compare/v1.0.6...HEAD
+[1.0.6]: https://github.com/pboling/rspec-block_is_expected/compare/v1.0.5...v1.0.6
+[1.0.6t]: https://github.com/pboling/rspec-block_is_expected/tags/v1.0.6
+[1.0.5]: https://github.com/pboling/rspec-block_is_expected/compare/v1.0.4...v1.0.5
+[1.0.5t]: https://github.com/pboling/rspec-block_is_expected/tags/v1.0.5
+[1.0.4]: https://github.com/pboling/rspec-block_is_expected/compare/v1.0.3...v1.0.4
+[1.0.4t]: https://github.com/pboling/rspec-block_is_expected/tags/v1.0.4
+[1.0.3]: https://github.com/pboling/rspec-block_is_expected/compare/v1.0.2...v1.0.3
+[1.0.3t]: https://github.com/pboling/rspec-block_is_expected/tags/v1.0.3
+[1.0.2]: https://github.com/pboling/rspec-block_is_expected/compare/v1.0.1...v1.0.2
+[1.0.1]: https://github.com/pboling/rspec-block_is_expected/compare/v1.0.0...v1.0.1

data/CODE_OF_CONDUCT.md

@@ -2,73 +2,83 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
+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 creating a positive environment
-include:
+Examples of behavior that contributes to a positive environment for our community include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+* 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 by participants include:
+Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
+* 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 electronic
-  address, without explicit permission
+* 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
 
-## Our Responsibilities
+## Enforcement Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+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.
 
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors 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 both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+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 by contacting the project team at peter.boling@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+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.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+**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 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+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
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+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,51 @@
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at [https://github.com/pboling/rspec-block_is_expected][🚎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`
+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 && echo $SOURCE_DATE_EPOCH`
+   b. If the echo above has no output, then it didn't work.
+   c. Note that you'll need the `zsh/datetime` module, if running `zsh`.
+9. Run `bundle exec rake build`
+10. Run [`bin/checksums`][🔒️rubygems-checksums-pr] 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][🖐contributors-img]][🖐contributors]
+
+Made with [contributors-img][🖐contrib-rocks].
+
+[🧪build]: https://github.com/pboling/rspec-block_is_expected/actions
+[🏘chat]: https://matrix.to/#/%23pboling_rspec-block_is_expected:gitter.im
+[🤝conduct]: https://github.com/pboling/rspec-block_is_expected/blob/main/CODE_OF_CONDUCT.md
+[🖐contrib-rocks]: https://contrib.rocks
+[🖐contributors]: https://github.com/pboling/rspec-block_is_expected/graphs/contributors
+[🖐contributors-img]: https://contrib.rocks/image?repo=pboling/rspec-block_is_expected
+[💎rubygems]: https://rubygems.org
+[🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
+[🔒️rubygems-checksums-pr]: https://github.com/rubygems/guides/pull/325
+[🚎src-main]: https://github.com/pboling/rspec-block_is_expected

data/{LICENSE → LICENSE.txt}

@@ -1,4 +1,4 @@
-Copyright (c) 2018, 2020, 2023 Peter H. Boling of RailsBling.com
+Copyright © 2018, 2020, 2023 - 2024 Peter H. Boling of RailsBling.com
 
 MIT License