diff-lcs 2.0.0.beta.2 → 2.0.0
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 +4 -4
- data/CHANGELOG.md +3 -1
- data/CODE_OF_CONDUCT.md +152 -114
- data/README.md +17 -8
- data/SECURITY.md +2 -2
- data/lib/diff/lcs/version.rb +1 -1
- metadata +7 -10
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: b8edc3b3383f33e30269bdef56fd21d58ac8efe471bb202f129d659a4f1a5ead
|
|
4
|
+
data.tar.gz: 681426cabb34022d55a8335b4dcf095dc5b97faeddc4bbe82793a2cba36c6729
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: db895eb27c2215803f6da307375044c456fe7a09250d86d3be8fd176e22cc6aef71d3767fd6901c62c3a9a5c1035e282570a535fe365bff8af9ce1459d937687
|
|
7
|
+
data.tar.gz: 948fd71bb838124c75c594921a5225358785b40d36d4b3bae60bd0d17914f1b3aa9ab71715e25c488028a67fb660a41808036ffa955b3802505dc9dce83d13fc
|
data/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## 2.0.0
|
|
3
|
+
## 2.0.0 / 2026-02-01
|
|
4
4
|
|
|
5
5
|
This release has significant **breaking changes**.
|
|
6
6
|
|
|
@@ -56,6 +56,8 @@ This release has significant **breaking changes**.
|
|
|
56
56
|
(`rake integration`) were written with the assistance of [Kiro][kiro] and
|
|
57
57
|
verified manually, with portions changed as required.
|
|
58
58
|
|
|
59
|
+
- The code of conduct was updated to the Contributor Covenant 3.0.
|
|
60
|
+
|
|
59
61
|
## 1.6.2 / 2025-05-12
|
|
60
62
|
|
|
61
63
|
- Handle upcoming changes to the `cgi` gem in Ruby 3.5 ([#147][pull-147])
|
data/CODE_OF_CONDUCT.md
CHANGED
|
@@ -1,128 +1,166 @@
|
|
|
1
|
-
# Contributor Covenant Code of Conduct
|
|
1
|
+
# Contributor Covenant 3.0 Code of Conduct
|
|
2
2
|
|
|
3
3
|
## Our Pledge
|
|
4
4
|
|
|
5
|
-
We
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
identity
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
or
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
5
|
+
We pledge to make our community welcoming, safe, and equitable for all.
|
|
6
|
+
|
|
7
|
+
We are committed to fostering an environment that respects and promotes the
|
|
8
|
+
dignity, rights, and contributions of all individuals, regardless of
|
|
9
|
+
characteristics including race, ethnicity, caste, color, age, physical
|
|
10
|
+
characteristics, neurodiversity, disability, sex or gender, gender identity or
|
|
11
|
+
expression, sexual orientation, language, philosophy or religion, national or
|
|
12
|
+
social origin, socio-economic position, level of education, or other status. The
|
|
13
|
+
same privileges of participation are extended to everyone who participates in
|
|
14
|
+
good faith and in accordance with this Covenant.
|
|
15
|
+
|
|
16
|
+
## Encouraged Behaviors
|
|
17
|
+
|
|
18
|
+
While acknowledging differences in social norms, we all strive to meet our
|
|
19
|
+
community's expectations for positive behavior. We also understand that our
|
|
20
|
+
words and actions may be interpreted differently than we intend based on
|
|
21
|
+
culture, background, or native language.
|
|
22
|
+
|
|
23
|
+
With these considerations in mind, we agree to behave mindfully toward each
|
|
24
|
+
other and act in ways that center our shared values, including:
|
|
25
|
+
|
|
26
|
+
1. Respecting the **purpose of our community**, our activities, and our ways of
|
|
27
|
+
gathering.
|
|
28
|
+
2. Engaging **kindly and honestly** with others.
|
|
29
|
+
3. Respecting **different viewpoints** and experiences.
|
|
30
|
+
4. **Taking responsibility** for our actions and contributions.
|
|
31
|
+
5. Gracefully giving and accepting **constructive feedback**.
|
|
32
|
+
6. Committing to **repairing harm** when it occurs.
|
|
33
|
+
7. Behaving in other ways that promote and sustain the **well-being of our
|
|
34
|
+
community**.
|
|
35
|
+
|
|
36
|
+
## Restricted Behaviors
|
|
37
|
+
|
|
38
|
+
We agree to restrict the following behaviors in our community. Instances,
|
|
39
|
+
threats, and promotion of these behaviors are violations of this Code of
|
|
40
|
+
Conduct.
|
|
41
|
+
|
|
42
|
+
1. **Harassment.** Violating explicitly expressed boundaries or engaging in
|
|
43
|
+
unnecessary personal attention after any clear request to stop.
|
|
44
|
+
2. **Character attacks.** Making insulting, demeaning, or pejorative comments
|
|
45
|
+
directed at a community member or group of people.
|
|
46
|
+
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
|
|
47
|
+
behavior on the basis of immutable identities or traits.
|
|
48
|
+
4. **Sexualization.** Behaving in a way that would generally be considered
|
|
49
|
+
inappropriately intimate in the context or purpose of the community.
|
|
50
|
+
5. **Violating confidentiality**. Sharing or acting on someone's personal or
|
|
51
|
+
private information without their permission.
|
|
52
|
+
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm
|
|
53
|
+
toward any person or group.
|
|
54
|
+
7. Behaving in other ways that **threaten the well-being** of our community.
|
|
55
|
+
|
|
56
|
+
### Other Restrictions
|
|
57
|
+
|
|
58
|
+
1. **Misleading identity.** Impersonating someone else for any reason, or
|
|
59
|
+
pretending to be someone else to evade enforcement actions.
|
|
60
|
+
2. **Failing to credit sources.** Not properly crediting the sources of content
|
|
61
|
+
you contribute.
|
|
62
|
+
3. **Promotional materials**. Sharing marketing or other commercial content in a
|
|
63
|
+
way that is outside the norms of the community.
|
|
64
|
+
4. **Irresponsible communication.** Failing to responsibly present content which
|
|
65
|
+
includes, links or describes any other restricted behaviors.
|
|
66
|
+
|
|
67
|
+
## Reporting an Issue
|
|
68
|
+
|
|
69
|
+
Tensions can occur between community members even when they are trying their
|
|
70
|
+
best to collaborate. Not every conflict represents a code of conduct violation,
|
|
71
|
+
and this Code of Conduct reinforces encouraged behaviors and norms that can help
|
|
72
|
+
avoid conflicts and minimize harm.
|
|
73
|
+
|
|
74
|
+
When an incident does occur, it is important to report it promptly. To report a
|
|
75
|
+
possible violation, create a [private security advisory][advisory] — violations
|
|
76
|
+
of this code of conduct are considered security vulnerabilities.
|
|
77
|
+
|
|
78
|
+
Community Moderators take reports of violations seriously and will make every
|
|
79
|
+
effort to respond in a timely manner. They will investigate all reports of code
|
|
80
|
+
of conduct violations, reviewing messages, logs, and recordings, or interviewing
|
|
81
|
+
witnesses and other participants. Community Moderators will keep investigation
|
|
82
|
+
and enforcement actions as transparent as possible while prioritizing safety and
|
|
83
|
+
confidentiality. In order to honor these values, enforcement actions are carried
|
|
84
|
+
out in private with the involved parties, but communicating to the whole
|
|
85
|
+
community may be part of a mutually agreed upon resolution.
|
|
86
|
+
|
|
87
|
+
## Addressing and Repairing Harm
|
|
88
|
+
|
|
89
|
+
If an investigation by the Community Moderators finds that this Code of Conduct
|
|
90
|
+
has been violated, the following enforcement ladder may be used to determine how
|
|
91
|
+
best to repair harm, based on the incident's impact on the individuals involved
|
|
92
|
+
and the community as a whole. Depending on the severity of a violation, lower
|
|
93
|
+
rungs on the ladder may be skipped.
|
|
94
|
+
|
|
95
|
+
1. Warning
|
|
96
|
+
1. Event: A violation involving a single incident or series of incidents.
|
|
97
|
+
2. Consequence: A private, written warning from the Community Moderators.
|
|
98
|
+
3. Repair: Examples of repair include a private written apology,
|
|
99
|
+
acknowledgement of responsibility, and seeking clarification on
|
|
100
|
+
expectations.
|
|
101
|
+
|
|
102
|
+
2. Temporarily Limited Activities
|
|
103
|
+
1. Event: A repeated incidence of a violation that previously resulted in a
|
|
104
|
+
warning, or the first incidence of a more serious violation.
|
|
105
|
+
2. Consequence: A private, written warning with a time-limited cooldown
|
|
106
|
+
period designed to underscore the seriousness of the situation and give
|
|
107
|
+
the community members involved time to process the incident. The cooldown
|
|
108
|
+
period may be limited to particular communication channels or interactions
|
|
109
|
+
with particular community members.
|
|
110
|
+
3. Repair: Examples of repair may include making an apology, using the
|
|
111
|
+
cooldown period to reflect on actions and impact, and being thoughtful
|
|
112
|
+
about re-entering community spaces after the period is over.
|
|
113
|
+
|
|
114
|
+
3. Temporary Suspension
|
|
115
|
+
1. Event: A pattern of repeated violation which the Community Moderators have
|
|
116
|
+
tried to address with warnings, or a single serious violation.
|
|
117
|
+
2. Consequence: A private written warning with conditions for return from
|
|
118
|
+
suspension. In general, temporary suspensions give the person being
|
|
119
|
+
suspended time to reflect upon their behavior and possible corrective
|
|
120
|
+
actions.
|
|
121
|
+
3. Repair: Examples of repair include respecting the spirit of the
|
|
122
|
+
suspension, meeting the specified conditions for return, and being
|
|
123
|
+
thoughtful about how to reintegrate with the community when the suspension
|
|
124
|
+
is lifted.
|
|
125
|
+
|
|
126
|
+
4. Permanent Ban
|
|
127
|
+
1. Event: A pattern of repeated code of conduct violations that other steps
|
|
128
|
+
on the ladder have failed to resolve, or a violation so serious that the
|
|
129
|
+
Community Moderators determine there is no way to keep the community safe
|
|
130
|
+
with this person as a member.
|
|
131
|
+
2. Consequence: Access to all community spaces, tools, and communication
|
|
132
|
+
channels is removed. In general, permanent bans should be rarely used,
|
|
133
|
+
should have strong reasoning behind them, and should only be resorted to
|
|
134
|
+
if working through other remedies has failed to change the behavior.
|
|
135
|
+
3. Repair: There is no possible repair in cases of this severity.
|
|
136
|
+
|
|
137
|
+
This enforcement ladder is intended as a guideline. It does not limit the
|
|
138
|
+
ability of Community Managers to use their discretion and judgment, in keeping
|
|
139
|
+
with the best interests of our community.
|
|
50
140
|
|
|
51
141
|
## Scope
|
|
52
142
|
|
|
53
143
|
This Code of Conduct applies within all community spaces, and also applies when
|
|
54
|
-
an individual is officially representing the community in public
|
|
55
|
-
Examples of representing our community include using an official email
|
|
56
|
-
posting via an official social media account, or acting as an appointed
|
|
144
|
+
an individual is officially representing the community in public or other
|
|
145
|
+
spaces. Examples of representing our community include using an official email
|
|
146
|
+
address, posting via an official social media account, or acting as an appointed
|
|
57
147
|
representative at an online or offline event.
|
|
58
148
|
|
|
59
|
-
## Enforcement
|
|
60
|
-
|
|
61
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
62
|
-
reported to the community leaders responsible for enforcement at [INSERT CONTACT
|
|
63
|
-
METHOD]. All complaints will be reviewed and investigated promptly and fairly.
|
|
64
|
-
|
|
65
|
-
All community leaders are obligated to respect the privacy and security of the
|
|
66
|
-
reporter of any incident.
|
|
67
|
-
|
|
68
|
-
## Enforcement Guidelines
|
|
69
|
-
|
|
70
|
-
Community leaders will follow these Community Impact Guidelines in determining
|
|
71
|
-
the consequences for any action they deem in violation of this Code of Conduct:
|
|
72
|
-
|
|
73
|
-
### 1. Correction
|
|
74
|
-
|
|
75
|
-
**Community Impact**: Use of inappropriate language or other behavior deemed
|
|
76
|
-
unprofessional or unwelcome in the community.
|
|
77
|
-
|
|
78
|
-
**Consequence**: A private, written warning from community leaders, providing
|
|
79
|
-
clarity around the nature of the violation and an explanation of why the
|
|
80
|
-
behavior was inappropriate. A public apology may be requested.
|
|
81
|
-
|
|
82
|
-
### 2. Warning
|
|
83
|
-
|
|
84
|
-
**Community Impact**: A violation through a single incident or series of
|
|
85
|
-
actions.
|
|
86
|
-
|
|
87
|
-
**Consequence**: A warning with consequences for continued behavior. No
|
|
88
|
-
interaction with the people involved, including unsolicited interaction with
|
|
89
|
-
those enforcing the Code of Conduct, for a specified period of time. This
|
|
90
|
-
includes avoiding interactions in community spaces as well as external channels
|
|
91
|
-
like social media. Violating these terms may lead to a temporary or permanent
|
|
92
|
-
ban.
|
|
93
|
-
|
|
94
|
-
### 3. Temporary Ban
|
|
95
|
-
|
|
96
|
-
**Community Impact**: A serious violation of community standards, including
|
|
97
|
-
sustained inappropriate behavior.
|
|
98
|
-
|
|
99
|
-
**Consequence**: A temporary ban from any sort of interaction or public
|
|
100
|
-
communication with the community for a specified period of time. No public or
|
|
101
|
-
private interaction with the people involved, including unsolicited interaction
|
|
102
|
-
with those enforcing the Code of Conduct, is allowed during this period.
|
|
103
|
-
Violating these terms may lead to a permanent ban.
|
|
104
|
-
|
|
105
|
-
### 4. Permanent Ban
|
|
106
|
-
|
|
107
|
-
**Community Impact**: Demonstrating a pattern of violation of community
|
|
108
|
-
standards, including sustained inappropriate behavior, harassment of an
|
|
109
|
-
individual, or aggression toward or disparagement of classes of individuals.
|
|
110
|
-
|
|
111
|
-
**Consequence**: A permanent ban from any sort of public interaction within the
|
|
112
|
-
community.
|
|
113
|
-
|
|
114
149
|
## Attribution
|
|
115
150
|
|
|
116
|
-
This Code of Conduct is adapted from the
|
|
117
|
-
|
|
118
|
-
<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
|
|
151
|
+
This Code of Conduct is adapted from the Contributor Covenant, version 3.0,
|
|
152
|
+
permanently available at <https://www.contributor-covenant.org/version/3/0/>.
|
|
119
153
|
|
|
120
|
-
|
|
121
|
-
|
|
154
|
+
Contributor Covenant is stewarded by the Organization for Ethical Source and
|
|
155
|
+
licensed under CC BY-SA 4.0. To view a copy of this license, visit
|
|
156
|
+
<https://creativecommons.org/licenses/by-sa/4.0/>.
|
|
122
157
|
|
|
123
|
-
For answers to common questions about
|
|
124
|
-
<https://www.contributor-covenant.org/faq>. Translations are
|
|
125
|
-
<https://www.contributor-covenant.org/translations>.
|
|
158
|
+
For answers to common questions about Contributor Covenant, see the FAQ at
|
|
159
|
+
<https://www.contributor-covenant.org/faq>. Translations are provided at
|
|
160
|
+
<https://www.contributor-covenant.org/translations>. Additional enforcement and
|
|
161
|
+
community guideline resources can be found at
|
|
162
|
+
<https://www.contributor-covenant.org/resources>. The enforcement ladder was
|
|
163
|
+
inspired by the work of [Mozilla’s code of conduct team][inclusion].
|
|
126
164
|
|
|
127
|
-
[
|
|
128
|
-
[
|
|
165
|
+
[advisory]: https://github.com/halostatue/diff-lcs/security/advisories/new
|
|
166
|
+
[inclusion]: https://github.com/mozilla/inclusion
|
data/README.md
CHANGED
|
@@ -14,15 +14,23 @@ Diff::LCS computes the difference between two Enumerable sequences using the
|
|
|
14
14
|
McIlroy-Hunt longest common subsequence (LCS) algorithm. It includes utilities
|
|
15
15
|
to create a simple HTML diff output format and a standard diff-like tool.
|
|
16
16
|
|
|
17
|
-
This is release
|
|
18
|
-
|
|
19
|
-
of
|
|
17
|
+
This is release 2.0, which has significant breaking changes (removal of
|
|
18
|
+
deprecations and workarounds) and requires at least Ruby 3.2 or higher. See full
|
|
19
|
+
details in the `CHANGELOG`, but users of diff-lcs should not notice any
|
|
20
|
+
significant changes to the APIs.
|
|
20
21
|
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
22
|
+
### Performance and Compatibility
|
|
23
|
+
|
|
24
|
+
I have not run any benchmarks, but the use of immutable Data classes and the
|
|
25
|
+
removal of a number of inner loop conditionals related to encoding and String
|
|
26
|
+
handling (which have been unnecessary since at least Ruby 2.1 but kept for
|
|
27
|
+
strict compatibility) should allow better optimization by modern Ruby
|
|
28
|
+
implementations.
|
|
29
|
+
|
|
30
|
+
If you are using RSpec for your test suite, you are unlikely to be able to use
|
|
31
|
+
Diff::LCS 2.0 because of the minimum Ruby version unless the developers of RSpec
|
|
32
|
+
loosen their version constraints. I cannot control this and have raised
|
|
33
|
+
[rspec/rspec#290][rspec-issue-290].
|
|
26
34
|
|
|
27
35
|
## Synopsis
|
|
28
36
|
|
|
@@ -89,6 +97,7 @@ originally written for the Perl version, was written by Mark-Jason Dominus.
|
|
|
89
97
|
[ci-workflow]: https://github.com/halostatue/diff-lcs/actions/workflows/ci.yml
|
|
90
98
|
[coveralls]: https://coveralls.io/github/halostatue/diff-lcs?branch=main
|
|
91
99
|
[perl]: https://search.cpan.org/~nedkonz/Algorithm-Diff-1.15/
|
|
100
|
+
[rspec-issue-290]: https://github.com/rspec/rspec/issues/290
|
|
92
101
|
[rubygems]: https://rubygems.org/gems/diff-lcs
|
|
93
102
|
[shield-ci]: https://img.shields.io/github/actions/workflow/status/halostatue/diff-lcs/ci.yml?style=for-the-badge "Build Status"
|
|
94
103
|
[shield-coveralls]: https://img.shields.io/coverallsCoverage/github/halostatue/diff-lcs?style=for-the-badge
|
data/SECURITY.md
CHANGED
|
@@ -22,8 +22,8 @@ All issues raised must be demonstrated on the minimum supported Ruby version.
|
|
|
22
22
|
>
|
|
23
23
|
> | Version | Release Date | Support Ends | Security Support Ends |
|
|
24
24
|
> | ------- | ------------ | ------------ | --------------------- |
|
|
25
|
-
> | 1.x | 2010 | 2026-
|
|
26
|
-
> | 2.x | 2026-01
|
|
25
|
+
> | 1.x | 2010 | 2026-05-01 | 2027-02-01 |
|
|
26
|
+
> | 2.x | 2026-02-01 | - | - |
|
|
27
27
|
|
|
28
28
|
## Reporting a Vulnerability
|
|
29
29
|
|
data/lib/diff/lcs/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: diff-lcs
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 2.0.0
|
|
4
|
+
version: 2.0.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Austin Ziegler
|
|
@@ -189,20 +189,17 @@ dependencies:
|
|
|
189
189
|
- - "~>"
|
|
190
190
|
- !ruby/object:Gem::Version
|
|
191
191
|
version: '0.11'
|
|
192
|
-
description:
|
|
192
|
+
description: |
|
|
193
193
|
Diff::LCS computes the difference between two Enumerable sequences using the
|
|
194
194
|
McIlroy-Hunt longest common subsequence (LCS) algorithm. It includes utilities
|
|
195
195
|
to create a simple HTML diff output format and a standard diff-like tool.
|
|
196
196
|
|
|
197
|
-
This is release
|
|
198
|
-
|
|
199
|
-
of
|
|
197
|
+
This is release 2.0, which has significant breaking changes (removal of
|
|
198
|
+
deprecations and workarounds) and requires at least Ruby 3.2 or higher. See full
|
|
199
|
+
details in the `CHANGELOG`, but users of diff-lcs should not notice any
|
|
200
|
+
significant changes to the APIs.
|
|
200
201
|
|
|
201
|
-
|
|
202
|
-
no longer part of the CI test suite. If any changes have been introduced that
|
|
203
|
-
break those versions, bug reports and patches will be accepted, but it will be
|
|
204
|
-
up to the reporter to verify any fixes prior to release. The next major release
|
|
205
|
-
will completely break compatibility.
|
|
202
|
+
==== To Install:
|
|
206
203
|
email:
|
|
207
204
|
- halostatue@gmail.com
|
|
208
205
|
executables:
|