snaky_hash 2.0.3 → 2.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 7a4ebce56adbdd1bb1cd6ac0fe46f3b891e0c0cf689ec611e6ca00e03c503fc1
4
- data.tar.gz: ae1ffc55d9c653904a2c65bdfeb1b1724c6bce5eab251a225b036baaa5c165c5
3
+ metadata.gz: 3d7ba970e956310051542f6433aeca0bc5c98ee6bc2a3e85ed71c5b10ddd2330
4
+ data.tar.gz: d26b882458ccc1860b98bebb9391f917c245812fbda4eee3e2941d2f487a8be9
5
5
  SHA512:
6
- metadata.gz: 21e5beae61652b1307f346b676618562e1a713ff3db552e6dfc379683088e6e9de721eaca35dd32788564c77113d015af0d592def73697a2b25b5d8258a337b7
7
- data.tar.gz: 26327dc66ec45f4ab558e1cd383615107a72587b700df71837302ddef530d7b83acd5b70fb9601ad2c14f3d9c26290c956e99e941f1ce0568fed075317dacd81
6
+ metadata.gz: 6abac6e9dca6aae24b6362f4b2b0be36ded0c11f628911338ee21b5d8d962cf6ff7603b2dd586fb1f64c2f11dee34dd2a5f2074f1cbc5fafae9f859829ec3a47
7
+ data.tar.gz: f241d80a2a0ef0970cdfd37a522ac6e24bce5d3ced1167df919d1c705e9fd73fb7fcace1df2ca51bbeb39bdb5a80d67504e7e4919ff39617936dad73c54d1bb9
checksums.yaml.gz.sig CHANGED
Binary file
data/CHANGELOG.md CHANGED
@@ -1,29 +1,124 @@
1
1
  # Changelog
2
+
3
+ [![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
4
+
2
5
  All notable changes to this project will be documented in this file.
3
6
 
4
- The format (since v2) is based on [Keep a Changelog v1](https://keepachangelog.com/en/1.0.0/),
5
- and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.0.0.html).
7
+ The format is based on [Keep a Changelog][📗keep-changelog],
8
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
9
+ and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
10
+ Please file a bug if you notice a violation of semantic versioning.
11
+
12
+ [📌semver]: https://semver.org/spec/v2.0.0.html
13
+ [📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
14
+ [📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
15
+ [📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
16
+ [📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
17
+ [📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
6
18
 
7
19
  ## [Unreleased]
20
+
8
21
  ### Added
22
+
9
23
  ### Changed
24
+
10
25
  ### Deprecated
26
+
11
27
  ### Removed
28
+
12
29
  ### Fixed
30
+
13
31
  ### Security
14
32
 
33
+ ## [2.0.7] - 2026-07-14
34
+
35
+ - TAG: [v2.0.7][2.0.7t]
36
+ - COVERAGE: 100.00% -- 133/133 lines in 7 files
37
+ - BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
38
+ - 92.86% documented
39
+
40
+ ### Added
41
+
42
+ - Added support for JRuby 10.1 and TruffleRuby 34.0.
43
+
44
+ ### Changed
45
+
46
+ - Retemplated generated project metadata, support documentation, CI workflows,
47
+ binstubs, and development dependency floors with `kettle-jem` v7.0.0.
48
+
49
+ ### Fixed
50
+
51
+ - Corrected RubyGems homepage metadata to point at the gem documentation site.
52
+ - Corrected persisted Open Collective and repository topology metadata used by
53
+ future template runs.
54
+
55
+ - Package configured license files in gem release file lists.
56
+
57
+ - Removed stale local-path `version_gem` state from the main lockfile.
58
+
59
+ ## [2.0.6] - 2026-06-11
60
+
61
+ - TAG: [v2.0.6][2.0.6t]
62
+ - COVERAGE: 100.00% -- 133/133 lines in 7 files
63
+ - BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
64
+ - 92.86% documented
65
+
66
+ ### Fixed
67
+
68
+ - Restored `docs/CNAME` so the generated documentation site keeps its custom domain.
69
+ - Removed stale legacy CI workflows and duplicate extracted-stdlib gem
70
+ declarations from generated Appraisal gemfiles.
71
+
72
+ ## [2.0.5] - 2026-06-07
73
+
74
+ - TAG: [v2.0.5][2.0.5t]
75
+ - COVERAGE: 100.00% -- 133/133 lines in 7 files
76
+ - BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
77
+ - 92.86% documented
78
+
79
+ ### Changed
80
+
81
+ - Refreshed project scaffolding with the current `kettle-jem` template, including
82
+ updated CI workflows, modular gemfiles, and development tooling floors.
83
+
84
+ ## [2.0.4] - 2026-05-16
85
+
86
+ - TAG: [v2.0.4][2.0.4t]
87
+ - COVERAGE: 100.00% -- 133/133 lines in 7 files
88
+ - BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
89
+ - 100.00% documented
90
+
91
+ ### Added
92
+
93
+ - Incident Response Plan in IRP.md
94
+ - SnakyHash::VERSION (Traditional Constant Location)
95
+ - kettle-dev & kettle-test dev harnesses
96
+
97
+ ### Changed
98
+
99
+ - Contributor Conenant updated to version 2.1
100
+
101
+ ### Fixed
102
+
103
+ - Specs
104
+
15
105
  ## [2.0.3] - 2025-05-23
106
+
16
107
  - TAG: [v2.0.3][2.0.3t]
17
108
  - COVERAGE: 100.00% -- 132/132 lines in 7 files
18
109
  - BRANCH COVERAGE: 100.00% -- 38/38 branches in 7 files
19
110
  - 100.00% documented
111
+
20
112
  ### Added
113
+
21
114
  - `#dump` instance method injected by `extend SnakyHash::Serializer` (@pboling)
22
115
  - `dump_hash_extensions` - new feature, analogous to `load_hash_extensions` (@pboling)
23
116
  - `dump_value_extensions` - alternate name for `dump_extensions` (@pboling)
24
117
  - `load_value_extensions` - alternate name for `load_extensions` (@pboling)
25
118
  - Clarifying documentation (@pboling)
119
+
26
120
  ### Fixed
121
+
27
122
  - [gh4](https://github.com/oauth-xx/snaky_hash/pull/4) - Serializer extensions dump and load empty values properly (@pboling)
28
123
  - Fixed `dump_extensions`, `load_extensions`, `load_hash_extensions`
29
124
  - Intended usage is primarily JSON, and oauth2 gem
@@ -31,11 +126,14 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
31
126
  - Previous logic was inherited from design decisions made by `serialized_hashie` gem; doesn't apply here
32
127
 
33
128
  ## [2.0.2] - 2025-05-21
129
+
34
130
  - TAG: [v2.0.2][2.0.2t]
35
131
  - COVERAGE: 100.00% -- 119/119 lines in 7 files
36
132
  - BRANCH COVERAGE: 100.00% -- 35/35 branches in 7 files
37
133
  - 100.00% documented
134
+
38
135
  ### Added
136
+
39
137
  - Gem is signed by 20-year cert (@pboling)
40
138
  - Expires 2045-04-29
41
139
  - Gemspec metadata updates (@pboling)
@@ -48,42 +146,68 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
48
146
  - 100% documented! (@pboling)
49
147
 
50
148
  ## [2.0.1] - 2022-09-23
149
+
51
150
  - TAG: [v2.0.1][2.0.1t]
151
+
52
152
  ### Added
153
+
53
154
  - Certificate for signing gem releases (@pboling)
54
155
  - Gemspec metadata (@pboling)
55
156
  - funding_uri
56
157
  - mailing_list_uri
57
158
  - Checksums for released gems (@pboling)
159
+
58
160
  ### Changed
161
+
59
162
  - Gem releases are now cryptographically signed (@pboling)
60
163
 
61
164
  ## [2.0.0] - 2022-08-29
165
+
62
166
  - TAG: [v2.0.0][2.0.0t]
167
+
63
168
  ### Changed
169
+
64
170
  - **BREAKING**: `SnakeHash::Snake` is now a mixin, now with support for symbol or string keys
65
171
  ```ruby
66
172
  class MySnakedHash < Hashie::Mash
67
173
  include SnakyHash::Snake.new(key_type: :string) # or :symbol
68
174
  end
69
175
  ```
176
+
70
177
  ### Added
178
+
71
179
  - `SnakyHash::StringKeyed`: a Hashie::Mash class with snake-cased String keys
72
180
  - `SnakyHash::SymbolKeyed`: a Hashie::Mash class with snake-cased Symbol keys
73
181
 
74
182
  ## [1.0.1] - 2022-08-26
183
+
75
184
  - TAG: [v1.0.1][1.0.1t]
185
+
76
186
  ### Added
187
+
77
188
  - Missing LICENSE.txt file to release
189
+
78
190
  ### Removed
191
+
79
192
  - Accidentally added bundler dependency (vestige of transpec process) is now removed
80
193
 
81
194
  ## [1.0.0] - 2022-08-26
195
+
82
196
  - TAG: [v1.0.0][1.0.0t]
197
+
83
198
  ### Added
199
+
84
200
  - Initial release
85
201
 
86
- [Unreleased]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.3...main
202
+ [Unreleased]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.7...HEAD
203
+ [2.0.7]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.6...v2.0.7
204
+ [2.0.7t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.7
205
+ [2.0.6]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.5...v2.0.6
206
+ [2.0.6t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.6
207
+ [2.0.5]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.4...v2.0.5
208
+ [2.0.5t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.5
209
+ [2.0.4]: https://github.com/ruby-oauth/snaky_hash/compare/v2.0.3...v2.0.4
210
+ [2.0.4t]: https://github.com/ruby-oauth/snaky_hash/releases/tag/v2.0.4
87
211
  [2.0.3]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.2...v2.0.3
88
212
  [2.0.3t]: https://gitlab.com/oauth-xx/snaky_hash/-/releases/tag/v2.0.3
89
213
  [2.0.2]: https://gitlab.com/oauth-xx/snaky_hash/-/compare/v2.0.1...v2.0.2
data/CITATION.cff ADDED
@@ -0,0 +1,20 @@
1
+ cff-version: 1.2.0
2
+ title: "snaky_hash"
3
+ message: >-
4
+ If you use this work and you want to cite it,
5
+ then you can use the metadata from this file.
6
+ type: software
7
+ authors:
8
+ - given-names: "Peter H."
9
+ family-names: "Boling"
10
+ email: "floss@galtzo.com"
11
+ affiliation: "galtzo.com"
12
+ orcid: 'https://orcid.org/0009-0008-8519-441X'
13
+ identifiers:
14
+ - type: url
15
+ value: 'https://github.com/ruby-oauth/snaky_hash'
16
+ description: "snaky_hash"
17
+ repository-code: 'https://github.com/ruby-oauth/snaky_hash'
18
+ abstract: >-
19
+ snaky_hash
20
+ license: See license file
data/CODE_OF_CONDUCT.md CHANGED
@@ -1,4 +1,3 @@
1
-
2
1
  # Contributor Covenant Code of Conduct
3
2
 
4
3
  ## Our Pledge
@@ -7,8 +6,8 @@ We as members, contributors, and leaders pledge to make participation in our
7
6
  community a harassment-free experience for everyone, regardless of age, body
8
7
  size, visible or invisible disability, ethnicity, sex characteristics, gender
9
8
  identity and expression, level of experience, education, socio-economic status,
10
- nationality, personal appearance, race, religion, or sexual identity
11
- and orientation.
9
+ nationality, personal appearance, race, caste, color, religion, or sexual
10
+ identity and orientation.
12
11
 
13
12
  We pledge to act and interact in ways that contribute to an open, welcoming,
14
13
  diverse, inclusive, and healthy community.
@@ -23,17 +22,17 @@ community include:
23
22
  * Giving and gracefully accepting constructive feedback
24
23
  * Accepting responsibility and apologizing to those affected by our mistakes,
25
24
  and learning from the experience
26
- * Focusing on what is best not just for us as individuals, but for the
27
- overall community
25
+ * Focusing on what is best not just for us as individuals, but for the overall
26
+ community
28
27
 
29
28
  Examples of unacceptable behavior include:
30
29
 
31
- * The use of sexualized language or imagery, and sexual attention or
32
- advances of any kind
30
+ * The use of sexualized language or imagery, and sexual attention or advances of
31
+ any kind
33
32
  * Trolling, insulting or derogatory comments, and personal or political attacks
34
33
  * Public or private harassment
35
- * Publishing others' private information, such as a physical or email
36
- address, without their explicit permission
34
+ * Publishing others' private information, such as a physical or email address,
35
+ without their explicit permission
37
36
  * Other conduct which could reasonably be considered inappropriate in a
38
37
  professional setting
39
38
 
@@ -53,7 +52,7 @@ decisions when appropriate.
53
52
 
54
53
  This Code of Conduct applies within all community spaces, and also applies when
55
54
  an individual is officially representing the community in public spaces.
56
- Examples of representing our community include using an official e-mail address,
55
+ Examples of representing our community include using an official email address,
57
56
  posting via an official social media account, or acting as an appointed
58
57
  representative at an online or offline event.
59
58
 
@@ -61,7 +60,7 @@ representative at an online or offline event.
61
60
 
62
61
  Instances of abusive, harassing, or otherwise unacceptable behavior may be
63
62
  reported to the community leaders responsible for enforcement at
64
- [INSERT CONTACT METHOD].
63
+ [![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
65
64
  All complaints will be reviewed and investigated promptly and fairly.
66
65
 
67
66
  All community leaders are obligated to respect the privacy and security of the
@@ -83,15 +82,15 @@ behavior was inappropriate. A public apology may be requested.
83
82
 
84
83
  ### 2. Warning
85
84
 
86
- **Community Impact**: A violation through a single incident or series
87
- of actions.
85
+ **Community Impact**: A violation through a single incident or series of
86
+ actions.
88
87
 
89
88
  **Consequence**: A warning with consequences for continued behavior. No
90
89
  interaction with the people involved, including unsolicited interaction with
91
90
  those enforcing the Code of Conduct, for a specified period of time. This
92
91
  includes avoiding interactions in community spaces as well as external channels
93
- like social media. Violating these terms may lead to a temporary or
94
- permanent ban.
92
+ like social media. Violating these terms may lead to a temporary or permanent
93
+ ban.
95
94
 
96
95
  ### 3. Temporary Ban
97
96
 
@@ -107,27 +106,29 @@ Violating these terms may lead to a permanent ban.
107
106
  ### 4. Permanent Ban
108
107
 
109
108
  **Community Impact**: Demonstrating a pattern of violation of community
110
- standards, including sustained inappropriate behavior, harassment of an
109
+ standards, including sustained inappropriate behavior, harassment of an
111
110
  individual, or aggression toward or disparagement of classes of individuals.
112
111
 
113
- **Consequence**: A permanent ban from any sort of public interaction within
114
- the community.
112
+ **Consequence**: A permanent ban from any sort of public interaction within the
113
+ community.
115
114
 
116
115
  ## Attribution
117
116
 
118
117
  This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119
- version 2.0, available at
120
- [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
118
+ version 2.1, available at
119
+ [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121
120
 
122
121
  Community Impact Guidelines were inspired by
123
122
  [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124
123
 
125
124
  For answers to common questions about this code of conduct, see the FAQ at
126
- [https://www.contributor-covenant.org/faq][FAQ]. Translations are available
127
- at [https://www.contributor-covenant.org/translations][translations].
125
+ [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126
+ [https://www.contributor-covenant.org/translations][translations].
128
127
 
129
128
  [homepage]: https://www.contributor-covenant.org
130
- [v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
129
+ [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131
130
  [Mozilla CoC]: https://github.com/mozilla/diversity
132
131
  [FAQ]: https://www.contributor-covenant.org/faq
133
132
  [translations]: https://www.contributor-covenant.org/translations
133
+ [🚂maint-contact]: http://www.railsbling.com/contact
134
+ [🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red