snaky_hash 2.0.1 → 2.0.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2e85d5cdcbe75012d4230e8cf2444461cb395187250dba8a2c5dfb925f0ad547
-  data.tar.gz: 40f046fd2560be655d0e330c3e3239121b8a2044a0ddc157ceb462ca720cc005
+  metadata.gz: 3d7ba970e956310051542f6433aeca0bc5c98ee6bc2a3e85ed71c5b10ddd2330
+  data.tar.gz: d26b882458ccc1860b98bebb9391f917c245812fbda4eee3e2941d2f487a8be9
 SHA512:
-  metadata.gz: c548df1650e90ab683271e79efe82d7c5748c1359d004a339d28daa448f0478066c33462c7d29c1e1c2dec7770b31ae9d08550cff6d270d4307c174918479d89
-  data.tar.gz: 17126cb28e0d3563f02742f717a01f11d3fc570583b168b7145fc798e2d86163e18b5fe33c5a40956448cfcc4febb4e74dfec60b979e0f39e7268491d78c00b5
+  metadata.gz: 6abac6e9dca6aae24b6362f4b2b0be36ded0c11f628911338ee21b5d8d962cf6ff7603b2dd586fb1f64c2f11dee34dd2a5f2074f1cbc5fafae9f859829ec3a47
+  data.tar.gz: f241d80a2a0ef0970cdfd37a522ac6e24bce5d3ced1167df919d1c705e9fd73fb7fcace1df2ca51bbeb39bdb5a80d67504e7e4919ff39617936dad73c54d1bb9

data/CHANGELOG.md

@@ -1,48 +1,217 @@
 # Changelog
+
+[![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
+
 All notable changes to this project will be documented in this file.
 
-The format (since v2) 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).
+The format is based on [Keep a Changelog][📗keep-changelog],
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
+and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
+Please file a bug if you notice a violation of semantic versioning.
+
+[📌semver]: https://semver.org/spec/v2.0.0.html
+[📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
+[📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
+[📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
+[📗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
 
 ## [Unreleased]
+
 ### Added
+
 ### Changed
-### Fixed
+
+### Deprecated
+
 ### Removed
 
-## [2.0.1] - 2022-09-23 ([tag][2.0.1t])
+### Fixed
+
+### Security
+
+## [2.0.7] - 2026-07-14
+
+- TAG: [v2.0.7][2.0.7t]
+- COVERAGE: 100.00% -- 133/133 lines in 7 files
+- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
+- 92.86% documented
+
+### Added
+
+- Added support for JRuby 10.1 and TruffleRuby 34.0.
+
+### Changed
+
+- Retemplated generated project metadata, support documentation, CI workflows,
+  binstubs, and development dependency floors with `kettle-jem` v7.0.0.
+
+### Fixed
+
+- Corrected RubyGems homepage metadata to point at the gem documentation site.
+- Corrected persisted Open Collective and repository topology metadata used by
+  future template runs.
+
+- Package configured license files in gem release file lists.
+
+- Removed stale local-path `version_gem` state from the main lockfile.
+
+## [2.0.6] - 2026-06-11
+
+- TAG: [v2.0.6][2.0.6t]
+- COVERAGE: 100.00% -- 133/133 lines in 7 files
+- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
+- 92.86% documented
+
+### Fixed
+
+- Restored `docs/CNAME` so the generated documentation site keeps its custom domain.
+- Removed stale legacy CI workflows and duplicate extracted-stdlib gem
+  declarations from generated Appraisal gemfiles.
+
+## [2.0.5] - 2026-06-07
+
+- TAG: [v2.0.5][2.0.5t]
+- COVERAGE: 100.00% -- 133/133 lines in 7 files
+- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
+- 92.86% documented
+
+### Changed
+
+- Refreshed project scaffolding with the current `kettle-jem` template, including
+  updated CI workflows, modular gemfiles, and development tooling floors.
+
+## [2.0.4] - 2026-05-16
+
+- TAG: [v2.0.4][2.0.4t]
+- COVERAGE: 100.00% -- 133/133 lines in 7 files
+- BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
+- 100.00% documented
+
+### Added
+
+- Incident Response Plan in IRP.md
+- SnakyHash::VERSION (Traditional Constant Location)
+- kettle-dev & kettle-test dev harnesses
+
+### Changed
+
+- Contributor Conenant updated to version 2.1
+
+### Fixed
+
+- Specs
+
+## [2.0.3] - 2025-05-23
+
+- TAG: [v2.0.3][2.0.3t]
+-  COVERAGE: 100.00% -- 132/132 lines in 7 files
+-  BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
+- 100.00% documented
+
+### Added
+
+- `#dump` instance method injected by `extend SnakyHash::Serializer` (@pboling)
+- `dump_hash_extensions` - new feature, analogous to `load_hash_extensions` (@pboling)
+- `dump_value_extensions` - alternate name for `dump_extensions` (@pboling)
+- `load_value_extensions` - alternate name for `load_extensions` (@pboling)
+- Clarifying documentation (@pboling)
+
+### Fixed
+
+- [gh4](https://github.com/oauth-xx/snaky_hash/pull/4) - Serializer extensions dump and load empty values properly (@pboling)
+  - Fixed `dump_extensions`, `load_extensions`, `load_hash_extensions`
+  - Intended usage is primarily JSON, and oauth2 gem
+  - OAuth2 spec can have legitimately empty values (e.g. scopes could be empty)
+  - Previous logic was inherited from design decisions made by `serialized_hashie` gem; doesn't apply here
+
+## [2.0.2] - 2025-05-21
+
+- TAG: [v2.0.2][2.0.2t]
+- COVERAGE: 100.00% -- 119/119 lines in 7 files
+- BRANCH COVERAGE: 100.00% -- 35/35 branches in 7 files
+- 100.00% documented
+
+### Added
+
+- Gem is signed by 20-year cert (@pboling)
+  - Expires 2045-04-29
+- Gemspec metadata updates (@pboling)
+- Documentation updates (@pboling)
+- CI covering all code, and all key versions of runtime dependencies (@pboling)
+  - Including Hashie v0, v1, v2, v3, v4, v5, and HEAD
+- [gh2](https://github.com/oauth-xx/snaky_hash/pull/2) - Serializer option (@pboling)
+- [gh3](https://github.com/oauth-xx/snaky_hash/pull/3) - Serializer Extensions (@pboling)
+- Documentation site at [snaky-hash.galtzo.com](https://snaky-hash.galtzo.com) (@pboling)
+- 100% documented! (@pboling)
+
+## [2.0.1] - 2022-09-23
+
+- TAG: [v2.0.1][2.0.1t]
+
 ### Added
+
 - Certificate for signing gem releases (@pboling)
 - Gemspec metadata (@pboling)
     - funding_uri
     - mailing_list_uri
 - Checksums for released gems (@pboling)
+
 ### Changed
+
 - Gem releases are now cryptographically signed (@pboling)
 
-## [2.0.0] - 2022-08-29 ([tag][2.0.0t])
+## [2.0.0] - 2022-08-29
+
+- TAG: [v2.0.0][2.0.0t]
+
 ### Changed
+
 - **BREAKING**: `SnakeHash::Snake` is now a mixin, now with support for symbol or string keys
 ```ruby
 class MySnakedHash < Hashie::Mash
   include SnakyHash::Snake.new(key_type: :string) # or :symbol
 end
 ```
+
 ### Added
+
 - `SnakyHash::StringKeyed`: a Hashie::Mash class with snake-cased String keys
 - `SnakyHash::SymbolKeyed`: a Hashie::Mash class with snake-cased Symbol keys
 
-## [1.0.1] - 2022-08-26 ([tag][1.0.1t])
+## [1.0.1] - 2022-08-26
+
+- TAG: [v1.0.1][1.0.1t]
+
 ### Added
+
 - Missing LICENSE.txt file to release
+
 ### Removed
+
 - Accidentally added bundler dependency (vestige of transpec process) is now removed
 
-## [1.0.0] - 2022-08-26 ([tag][1.0.0t])
+## [1.0.0] - 2022-08-26
+
+- TAG: [v1.0.0][1.0.0t]
+
 ### Added
+
 - Initial release
 
-[Unreleased]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.1...main
+[Unreleased]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.7...HEAD
+[2.0.7]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.6...v2.0.7
+[2.0.7t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.7
+[2.0.6]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.5...v2.0.6
+[2.0.6t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.6
+[2.0.5]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.4...v2.0.5
+[2.0.5t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.5
+[2.0.4]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.3...v2.0.4
+[2.0.4t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.4
+[2.0.3]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.2...v2.0.3
+[2.0.3t]: https://gitlab.com/oauth-xx/snaky_hash/-/releases/tag/v2.0.3
+[2.0.2]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.1...v2.0.2
+[2.0.2t]: https://gitlab.com/oauth-xx/snaky_hash/-/releases/tag/v2.0.2
 [2.0.1]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.0...v2.0.1
 [2.0.1t]: https://gitlab.com/oauth-xx/snaky_hash/-/releases/tag/v2.0.1
 [2.0.0]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v1.0.1...v2.0.0

data/CITATION.cff

@@ -0,0 +1,20 @@
+cff-version: 1.2.0
+title: "snaky_hash"
+message: >-
+  If you use this work and you want to cite it,
+  then you can use the metadata from this file.
+type: software
+authors:
+  - given-names: "Peter H."
+    family-names: "Boling"
+    email: "floss@galtzo.com"
+    affiliation: "galtzo.com"
+    orcid: 'https://orcid.org/0009-0008-8519-441X'
+identifiers:
+  - type: url
+    value: 'https://github.com/ruby-oauth/snaky_hash'
+    description: "snaky_hash"
+repository-code: 'https://github.com/ruby-oauth/snaky_hash'
+abstract: >-
+  snaky_hash
+license: See license file

data/CODE_OF_CONDUCT.md

@@ -2,83 +2,133 @@
 
 ## 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 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, 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.
+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:
+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
+* 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
+* 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
 
 ## 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 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.
+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.
+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 email 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.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
+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.
+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:
+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.
+**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.
+**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.
+**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.
+**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.
+**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.
+**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.
+**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.
+**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.
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+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](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
+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. Translations are available at https://www.contributor-covenant.org/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.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
+[🚂maint-contact]: http://www.railsbling.com/contact
+[🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red