omniauth-identity 3.1.1 → 3.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e2a7eb266545d5ae300646af12c8557a414f49872f05850793ebd1c7b2cc17ca
-  data.tar.gz: 44b4dabec7425f586b1e9b731ea5a14b08902f7c782a360a3bb3ff9c829fa041
+  metadata.gz: ec83ecf143cd1670379934132cb2b2de9eda9728e78bde08e840d7484e4c4355
+  data.tar.gz: 320de15529ce6c80a164ccb8b6cd648be02470080d3991a3d3b20bcf90b779bb
 SHA512:
-  metadata.gz: ba1eafc9b744438b11dc71db4c8b8e8ec731568413f8dc461fa08df0956903015976669e66ce0402b064259a675db06f325548a54c86a3197f77bee4d1b4d438
-  data.tar.gz: 73e8367e8cb0fe207214cc8fbca53bbe800a76d4770ac0ef4f6b650eab2c2534ea28eb7371efa7537160c89a21d3812c37e6c4c39d4dce91caa826a87cb4518f
+  metadata.gz: 20b49fef66e63c724a5307cf80c1fd8d8d632ad604ed0a8bd309b7c4ec480ee29b2bd231832d5404cfe56f59a4fb35ac28dfb9296cfbc21da44a6d0372b9a3ba
+  data.tar.gz: b3fdaec1504f8b8ccfe1f730c765ceae51c24e35ab4405098a6731405c90533eebdd52ae48e05c944cfdb83ecb189359f99d483915e8a3a609ae037375a66ff7

data/CHANGELOG.md

@@ -8,12 +8,45 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 ## [Unreleased]
 ### Added
 ### Changed
-### Fixed
+### Deprecated
 ### Removed
+### Fixed
+### Security
 
-## [3.1.1] - 2024-11-18 ([tag][3.1.1t])
-- COVERAGE:  92.00% -- 345/375 lines in 15 files
-- BRANCH COVERAGE:  80.26% -- 61/76 branches in 15 files
+## [3.1.3] - 2025-06-08
+- TAG: [v3.1.3][3.1.3t]
+- COVERAGE: 92.06% -- 348/378 lines in 15 files
+- BRANCH COVERAGE: 79.49% -- 62/78 branches in 15 files
+- 44.44% documented
+### Added
+- More documentation by @pboling
+- Expanded test suite, covering many more points of the dependency matrix by @pboling
+- Test workflows with latest dependencies and more platform and dep HEADs
+### Changed
+- Updated Code of Conduct to Contributor Covenant v2.1
+### Fixed
+- Set `SKIP_GEM_SIGNING` in env to allow `gem build` without cryptographic signing requirement by @pboling
+  - Useful for linux distros whose package managers sign packages independently
+
+## [3.1.2] - 2025-05-07
+- TAG: [v3.1.2][3.1.2t]
+- COVERAGE: 92.02% -- 346/376 lines in 15 files
+- BRANCH COVERAGE: 79.49% -- 62/78 branches in 15 files
+### Added
+- 20 year signing cert expires 2045-04-29 by @pboling
+- Added CITATION.cff by @pboling
+- devcontainer for easier maintenance by @pboling
+- Improved documentation by @pboling
+- Greatly improved spec suite and CI config by @pboling
+  - Testing against JRuby 9.2, 9.3, 9.4, 10.0, and head
+  - Testing against many more combinations of Databases, ORMs, Rails, and Ruby versions
+### Changed
+- Upgraded Code of Conduct based on Contributor Covenant v2.1 by @pboling
+
+## [3.1.1] - 2024-11-18
+- TAG: [v3.1.1][3.1.1t]
+- COVERAGE: 92.00% -- 345/375 lines in 15 files
+- BRANCH COVERAGE: 80.26% -- 61/76 branches in 15 files
 - 44.44% documented
 ### Added
 - [PR 130][130] Add SECURITY.md policy by @pboling
@@ -23,9 +56,10 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 
 [130]: https://github.com/omniauth/omniauth-identity/pull/130
 
-## [3.1.0] - 2024-11-18 ([tag][3.1.0t])
-- COVERAGE:  91.98% -- 344/374 lines in 15 files
-- BRANCH COVERAGE:  80.26% -- 61/76 branches in 15 files
+## [3.1.0] - 2024-11-18
+- TAG: [v3.1.0][3.1.0t]
+- COVERAGE: 91.98% -- 344/374 lines in 15 files
+- BRANCH COVERAGE: 80.26% -- 61/76 branches in 15 files
 - 44.44% documented
 ### Added
 - [PR #123][123] Improve readability in #identity method of OmniAuth::Strategies::Identity by @Xeragus
@@ -49,26 +83,28 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 [122]: https://github.com/omniauth/omniauth-identity/pull/122
 [120]: https://github.com/omniauth/omniauth-identity/pull/120
 
-## [3.0.9] - 2021-06-16 ([tag][3.0.9t])
+## [3.0.9] - 2021-06-16
+- TAG: [v3.0.9][3.0.9t]
 ### Fixed
 - \[Sequel\] Fixes loading the Sequel adapter, issue reported as [#112](https://github.com/omniauth/omniauth-identity/issues/112)
 ### Added
 - 📝 Document the Database adapters and drivers the gem currently works with
 
-## [3.0.8] - 2021-03-24 ([tag][3.0.8t])
+## [3.0.8] - 2021-03-24
+- TAG: [v3.0.8][3.0.8t]
 ### Fixed
 - \[Model\] Fixes 2 issues raised in a comment on PR [#108](https://github.com/omniauth/omniauth-identity/pull/108#issuecomment-804456604)
   - When `options[:on_validation]` is set `new`/`save`/`persisted?` logic is used.
   - When `options[:on_validation]` is not set `create`/`persisted?` logic is used.
 
-## [3.0.7] - 2021-03-23 ([tag][3.0.7t])
+## [3.0.7] - 2021-03-23
+- TAG: [v3.0.7][3.0.7t]
 ### Fixed
 - \[ActiveRecord\] Fixed [#110](https://github.com/omniauth/omniauth-identity/issues/110) which prevented `OmniAuth::Identity::Models::ActiveRecord`-based records from saving.
 - \[CouchPotato\] Fixed `OmniAuth::Identity::Models::CouchPotato`'s `#save`.
 - \[Sequel\] Fixed `OmniAuth::Identity::Models::Sequel`'s `#save`.
 - \[Model\] Only define `::create`, `#save`, and `#persisted?` when not already defined.
 - \[Model\] Restore original `info` functionality which set `name` based on `first_name`, `last_name`, or `nickname`
-
 ### Changed
 - Upgraded to a newer `OmniAuth::Identity::SecurePassword` ripped from [Rails 6-1-stable](https://github.com/rails/rails/blob/6-1-stable/activemodel/lib/active_model/secure_password.rb)
   - Aeons ago the original was ripped from Rails 3.1, and frozen in time.
@@ -83,7 +119,8 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
   - Mongoid (MongoDB)
   - NoBrainer (RethinkDB)
 
-## [3.0.6] - 2021-03-20 ([tag][3.0.6t])
+## [3.0.6] - 2021-03-20
+- TAG: [v3.0.6][3.0.6t]
 ### Fixed
 - Fix breaking changes introduced by [#108](https://github.com/omniauth/omniauth-identity/pull/108) which prevented `:on_validation` from firing
 ### Added
@@ -94,7 +131,8 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
   - `:title` defaults to `'Identity Verification'`
   - `:registration_form_title` defaults to `'Register Identity'`
 
-## [3.0.5] - 2021-03-19 ([tag][3.0.5t])
+## [3.0.5] - 2021-03-19
+- TAG: [v3.0.5][3.0.5t]
 ### Fixed
 - Fix breaking changes introduced by [#86's](https://github.com/omniauth/omniauth-identity/pull/86) introduction of `:on_validation`
 ### Added
@@ -103,11 +141,13 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 - Refactor `Omniauth::Strategies::Identity.registration_phase` to support `Omniauth::Identity::Model`-inheriting classes that do not define `#save`.
   - This support will be dropped in v4.0.
 
-## [3.0.4] - 2021-02-14 ([tag][3.0.4t])
+## [3.0.4] - 2021-02-14
+- TAG: [v3.0.4][3.0.4t]
 ### Added
 - Add support for [sequel ORM](http://sequel.jeremyevans.net/)
 
-## [3.0.3] - 2021-02-14 ([tag][3.0.3t])
+## [3.0.3] - 2021-02-14
+- TAG: [v3.0.3][3.0.3t]
 ### Added
 - Add option `:on_validation`, which can be used to add a Captcha
   - See [example here](https://github.com/omniauth/omniauth-identity/pull/86#issue-63225122)
@@ -116,7 +156,8 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 ### Removed
 - ruby-head build... simply too slow
 
-## [3.0.2] - 2021-02-14 ([tag][3.0.2t])
+## [3.0.2] - 2021-02-14
+- TAG: [v3.0.2][3.0.2t]
 ### Fixed
 - Github Actions CI Build for Ruby 2.4, 3.0 and ruby-head
 - Updated copyright
@@ -124,11 +165,13 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 - Added Code Climate "Quality"
 - Updated Readme
 
-## [3.0.1] - 2021-02-14 ([tag][3.0.1t])
+## [3.0.1] - 2021-02-14
+- TAG: [v3.0.1][3.0.1t]
 ### Fixed
 - Github Actions CI Build for various Rubies
 
-## [3.0.0] - 2021-02-13 ([tag][3.0.0t])
+## [3.0.0] - 2021-02-13
+- TAG: [v3.0.0][3.0.0t]
 ### Added
 - Compatibility with Ruby 3
 - Add option `:enable_login` to bypass OmniAuth disabling of GET method (default `true`)
@@ -145,7 +188,8 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 - Support for DataMapper, which died long ago.
 - Unwanted git artifacts
 
-## [2.0.0] - 2020-09-01 ([tag][2.0.0t])
+## [2.0.0] - 2020-09-01
+- TAG: [v2.0.0][2.0.0t]
 ### Added
 - CHANGELOG to maintain a history of changes.
 - Include mongoid-rspec gem.
@@ -162,7 +206,11 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
 - Gemfile.lock file
 - MongoMapper support; unable to satisfy dependencies of both MongoMapper and Mongoid now that MongoMapper is no longer actively maintained.
 
-[Unreleased]: https://github.com/omniauth/omniauth-identity/compare/v3.1.1...HEAD
+[Unreleased]: https://github.com/omniauth/omniauth-identity/compare/v3.1.3...HEAD
+[3.1.3]: https://github.com/omniauth/omniauth-identity/compare/v3.1.2...v3.1.3
+[3.1.3t]: https://github.com/omniauth/omniauth-identity/tags/v3.1.3
+[3.1.2]: https://github.com/omniauth/omniauth-identity/compare/v3.1.1...v3.1.2
+[3.1.2t]: https://github.com/omniauth/omniauth-identity/tags/v3.1.2
 [3.1.1]: https://github.com/omniauth/omniauth-identity/compare/v3.1.0...v3.1.1
 [3.1.1t]: https://github.com/omniauth/omniauth-identity/tags/v3.1.1
 [3.1.0]: https://github.com/omniauth/omniauth-identity/compare/v3.0.9...v3.1.0

data/CODE_OF_CONDUCT.md

@@ -7,8 +7,8 @@ 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.
+nationality, personal appearance, race, caste, color, 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.
@@ -23,17 +23,17 @@ community include:
 * 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
+* 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
+* 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
+* 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
 
@@ -53,7 +53,7 @@ decisions when appropriate.
 
 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,
+Examples of representing our community include using an official email address,
 posting via an official social media account, or acting as an appointed
 representative at an online or offline event.
 
@@ -61,7 +61,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[INSERT CONTACT METHOD].
+[![Contact BDFL][🚂bdfl-contact-img]][🚂bdfl-contact].
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -83,15 +83,15 @@ behavior was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series
-of actions.
+**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.
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
 
 ### 3. Temporary Ban
 
@@ -107,27 +107,29 @@ 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
+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.
+**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][v2.0].
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
 
 Community Impact Guidelines were inspired by
 [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
 
 For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
-at [https://www.contributor-covenant.org/translations][translations].
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
 
 [homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
 [Mozilla CoC]: https://github.com/mozilla/diversity
 [FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations
+[🚂bdfl-contact]: http://www.railsbling.com/contact
+[🚂bdfl-contact-img]: https://img.shields.io/badge/Contact-BDFL-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red

data/CONTRIBUTING.md

@@ -1,53 +1,58 @@
 # Contributing
 
-Bug reports and pull requests are welcome on GitHub at [https://github.com/omniauth/omniauth-identity][🚎src-main]
-. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
+Bug reports and pull requests are welcome on GitHub at [https://github.com/omniauth/omniauth-identity][🚎src-main].
+This project should be a safe, welcoming space for collaboration, so contributors agree 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.
+To submit a patch, please fork the project, create a patch with tests, and send a pull request.
 
-## You can help!
+Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog].
+
+## Help out!
 
 Take a look at the `reek` list which is the file called `REEK` and find something to improve.
 
-Simply follow these instructions:
+Follow these instructions:
 
 1. Fork the repository
-2. Create your feature branch (`git checkout -b my-new-feature`)
+2. Create a feature branch (`git checkout -b my-new-feature`)
 3. Make some fixes.
-4. Commit your changes (`git commit -am 'Added some feature'`)
+4. Commit changes (`git commit -am 'Added some feature'`)
 5. Push to the branch (`git push origin my-new-feature`)
-6. Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
+6. Make sure to add tests for it. This is important, so it doesn't break in a future release.
 7. Create new Pull Request.
 
-## Contributors
-
-Your picture could be here!
+## Appraisals
 
-[![Contributors][🖐contributors-img]][🖐contributors]
+From time to time the appraisal gemfiles in `gemfiles/` will need to be updated.
 
-Made with [contributors-img][🖐contrib-rocks].
+NOTE: The `eval_gemfile` feature comes from a [fork][🚎appraisal-fork] of Appraisal.
 
-## The Reek List
+Please upvote the PR for `eval_gemfile` [support][🚎appraisal-eval-gemfile-pr]
 
-To refresh the `reek` list:
+Create or update them with the commands:
 
-```bash
-bundle exec reek > REEK
+```shell
+BUNDLE_GEMFILE=Appraisal.root.gemfile bundle
+BUNDLE_GEMFILE=Appraisal.root.gemfile bundle exec appraisal update
+bundle exec rake rubocop_gradual:autocorrect
 ```
 
-## Appraisal & Combustion
+When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
 
-### Generate a new set of Appraisal gemfiles:
+## The Reek List
+
+Take a look at the `reek` list which is the file called `REEK` and find something to improve.
+
+To refresh the `reek` list:
 
 ```bash
-BUNDLE_GEMFILE=Appraisal.root.gemfile appraisal update
+bundle exec reek > REEK
 ```
 
 ## Run Tests
 
-NOTE: In order to run *all* the tests you will need to have the following databases installed, configured, and running.
+NOTE: To run *all* tests have the following databases installed, configured, and running.
 
 1. [RethinkDB](https://rethinkdb.com), an open source, real-time, web database, [installed](https://rethinkdb.com/docs/install/) and [running](https://rethinkdb.com/docs/start-a-server/), e.g.
    ```bash
@@ -86,7 +91,7 @@ To run all tests on all databases (except RethinkDB):
 bundle exec rake spec:orm:all
 ```
 
-To run all tests that do not require any additional services, like MongoDB, CouchDB, or RethinkDB:
+To run all tests that do not require any additional services, i.e. excluding MongoDB, CouchDB, & RethinkDB:
 ```bash
 bundle exec rake test
 ```
@@ -118,41 +123,54 @@ bundle exec rake
 ```
 
 Or just run the linter.
+
 ```bash
-bundle exec rubocop_gradual:autocorrect
+bundle exec rake rubocop_gradual:autocorrect
 ```
 
-## Release
+## Contributors
+
+[![Contributors][🖐contributors-img]][🖐contributors]
+
+Made with [contributors-img][🖐contrib-rocks].
+
+## For Maintainers
 
 ### One-time, Per-maintainer, Setup
 
-**IMPORTANT**: Your public key for signing gems will need to be picked up by the line in the
-`gemspec` defining the `spec.cert_chain` (check the relevant ENV variables there),
-in order to sign the new release.
+**IMPORTANT**: To sign a build,
+a public key for signing gems will need to be picked up by the line in the
+`gemspec` defining the `spec.cert_chain` (check the relevant ENV variables there).
+All releases to RubyGems.org are signed releases.
 See: [RubyGems Security Guide][🔒️rubygems-security-guide]
 
+NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in the environment.
+
 ### 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`
+1. Run `bin/setup && bin/rake` as a "test, coverage, & linting" sanity check
+2. Update the version number in `version.rb`, and ensure `CHANGELOG.md` reflects changes
 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
-   - NOTE: Remember to [check the build][🧪build]!
+5. Run `git push` to trigger the final CI pipeline before release, and merge PRs
+    - NOTE: Remember to [check the build][🧪build].
 6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
 7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
-8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure you will release the latest trunk code
+8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
 9. Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use same timestamp, and generate same checksums
-   - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
-   - If the echo above has no output, then it didn't work.
-   - Note that you'll need the `zsh/datetime` module, if running `zsh`.
-   - In `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
+    - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
+    - If the echo above has no output, then it didn't work.
+    - Note: `zsh/datetime` module is needed, if running `zsh`.
+    - In older versions of `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
 10. Run `bundle exec rake build`
-11. Run `bin/checksums` (more [context][🔒️rubygems-checksums-pr]) to create SHA-256 and SHA-512 checksums
-    - Checksums will be committed automatically by the script, but not pushed
+11. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
+    to create SHA-256 and SHA-512 checksums. This functionality is provided by the `stone_checksums`
+    [gem][💎stone_checksums].
+    - The script automatically commits but does not push the checksums
 12. 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]
 
+13. [🚎src-main]: https://github.com/omniauth/omniauth-identity
 [🧪build]: https://github.com/omniauth/omniauth-identity/actions
 [🤝conduct]: https://github.com/omniauth/omniauth-identity/blob/main/CODE_OF_CONDUCT.md
 [🖐contrib-rocks]: https://contrib.rocks
@@ -160,5 +178,11 @@ See: [RubyGems Security Guide][🔒️rubygems-security-guide]
 [🖐contributors-img]: https://contrib.rocks/image?repo=omniauth/omniauth-identity
 [💎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/omniauth/omniauth-identity
+[🔒️rubygems-checksums-pr]: https://github.com/rubygems/rubygems/pull/6022
+[🔒️rubygems-guides-pr]: https://github.com/rubygems/guides/pull/325
+[💎stone_checksums]: https://github.com/pboling/stone_checksums
+[📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
+[📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
+[🚎appraisal-eval-gemfile-pr]: https://github.com/thoughtbot/appraisal/pull/248
+[🚎appraisal-fork]: https://github.com/pboling/appraisal/tree/galtzo
+[🏃‍♂️runner-tool-cache]: https://github.com/ruby/ruby-builder/releases/tag/toolcache

data/LICENSE.txt

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2021, 2024 Peter H. Boling, and OmniAuth-Identity Maintainers
+Copyright (c) 2021, 2024-2025 Peter H. Boling, and omniauth-identity contributors
 Copyright (c) 2020 Peter H. Boling, Andrew Roberts, and Jellybooks Ltd.
 Copyright (c) 2010-2015 Michael Bleigh, and Intridea, Inc.