hoe-halostatue 2.1.1 → 2.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '09d09b45270163489fd36ade505dcb66cf044390f8d9b63aea69cc49081810c5'
-  data.tar.gz: 9d8446c649e176013cb993e7117d4ece92f76b206484a7978db68332d2942182
+  metadata.gz: c93b2f03ae032c392bc6856ffbd2d06a350d631e3ff859d100e613c289bb57ce
+  data.tar.gz: 64031107e56a836f7546668403e47920f7a90545e921994e751e8dda0a0e1557
 SHA512:
-  metadata.gz: 947cba8ab26ebdd6aa08056ebd951bdfa8e19fa59c33ac68d9fb2ec4573d04c85f655e9e4aee1ae951461233c42e92f4d227968e80734155e2cb97dc12685287
-  data.tar.gz: bee5f811aea36c6123bb017555eb3c752760d7a52a18a78e8035242cfb3fa80d90bf9b6dd9a50aab6c57e9cb59c3b042ebe4782019a2e34af546ede07f55177c
+  metadata.gz: c8445ded0b456a5bac27a042c44f33c867a4055bf8df4116cbe0c9b2f24fa340eb90856eea7c4699c115a90e9121ea303d98cd3804418735d89560441cbcb028
+  data.tar.gz: 99d4f6c97b6fb790694259a44d1f57f55e7fcba833a8cf332807faae8a20f13780e687bd31733580eaae815194633f3ebfc405c6f0ee2931e2110bb5de9a4a7a

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # hoe-halostatue Changelog
 
+## 2.1.2 / 2026-01-17
+
+- Simplified several functions around git execution.
+
 ## 2.1.1 / 2025-06-26
 
 - Actually include strict warnings support files.

data/CODE_OF_CONDUCT.md

@@ -1,130 +1,166 @@
-# Contributor Covenant Code of Conduct
+# Contributor Covenant 3.0 Code of Conduct
 
 ## 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, 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.
-
-## Our Standards
-
-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
-
-Examples of unacceptable behavior include:
-
-- 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
-- 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 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.
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the
+dignity, rights, and contributions of all individuals, regardless of
+characteristics including race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex or gender, gender identity or
+expression, sexual orientation, language, philosophy or religion, national or
+social origin, socio-economic position, level of education, or other status. The
+same privileges of participation are extended to everyone who participates in
+good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our
+community's expectations for positive behavior. We also understand that our
+words and actions may be interpreted differently than we intend based on
+culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each
+other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of
+   gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our
+   community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances,
+threats, and promotion of these behaviors are violations of this Code of
+Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in
+   unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments
+   directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
+   behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered
+   inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or
+   private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm
+   toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or
+   pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content
+   you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a
+   way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which
+   includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their
+best to collaborate. Not every conflict represents a code of conduct violation,
+and this Code of Conduct reinforces encouraged behaviors and norms that can help
+avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a
+possible violation, create a [private security advisory][advisory] — violations
+of this code of conduct are considered security vulnerabilities.
+
+Community Moderators take reports of violations seriously and will make every
+effort to respond in a timely manner. They will investigate all reports of code
+of conduct violations, reviewing messages, logs, and recordings, or interviewing
+witnesses and other participants. Community Moderators will keep investigation
+and enforcement actions as transparent as possible while prioritizing safety and
+confidentiality. In order to honor these values, enforcement actions are carried
+out in private with the involved parties, but communicating to the whole
+community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct
+has been violated, the following enforcement ladder may be used to determine how
+best to repair harm, based on the incident's impact on the individuals involved
+and the community as a whole. Depending on the severity of a violation, lower
+rungs on the ladder may be skipped.
+
+1. Warning
+   1. Event: A violation involving a single incident or series of incidents.
+   2. Consequence: A private, written warning from the Community Moderators.
+   3. Repair: Examples of repair include a private written apology,
+      acknowledgement of responsibility, and seeking clarification on
+      expectations.
+
+2. Temporarily Limited Activities
+   1. Event: A repeated incidence of a violation that previously resulted in a
+      warning, or the first incidence of a more serious violation.
+   2. Consequence: A private, written warning with a time-limited cooldown
+      period designed to underscore the seriousness of the situation and give
+      the community members involved time to process the incident. The cooldown
+      period may be limited to particular communication channels or interactions
+      with particular community members.
+   3. Repair: Examples of repair may include making an apology, using the
+      cooldown period to reflect on actions and impact, and being thoughtful
+      about re-entering community spaces after the period is over.
+
+3. Temporary Suspension
+   1. Event: A pattern of repeated violation which the Community Moderators have
+      tried to address with warnings, or a single serious violation.
+   2. Consequence: A private written warning with conditions for return from
+      suspension. In general, temporary suspensions give the person being
+      suspended time to reflect upon their behavior and possible corrective
+      actions.
+   3. Repair: Examples of repair include respecting the spirit of the
+      suspension, meeting the specified conditions for return, and being
+      thoughtful about how to reintegrate with the community when the suspension
+      is lifted.
+
+4. Permanent Ban
+   1. Event: A pattern of repeated code of conduct violations that other steps
+      on the ladder have failed to resolve, or a violation so serious that the
+      Community Moderators determine there is no way to keep the community safe
+      with this person as a member.
+   2. Consequence: Access to all community spaces, tools, and communication
+      channels is removed. In general, permanent bans should be rarely used,
+      should have strong reasoning behind them, and should only be resorted to
+      if working through other remedies has failed to change the behavior.
+   3. Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the
+ability of Community Managers to use their discretion and judgment, in keeping
+with the best interests of our community.
 
 ## 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 email address,
-posting via an official social media account, or acting as an appointed
+an individual is officially representing the community in public or other
+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
-privately reported to the community leaders responsible for enforcement as a
-[security vulnerability][security vulnerability]. 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.
-
-**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 2.1, available at
-<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0,
+permanently available at <https://www.contributor-covenant.org/version/3/0/>.
 
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+Contributor Covenant is stewarded by the Organization for Ethical Source and
+licensed under CC BY-SA 4.0. To view a copy of this license, visit
+<https://creativecommons.org/licenses/by-sa/4.0/>.
 
-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>.
+For answers to common questions about Contributor Covenant, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are provided at
+<https://www.contributor-covenant.org/translations>. Additional enforcement and
+community guideline resources can be found at
+<https://www.contributor-covenant.org/resources>. The enforcement ladder was
+inspired by the work of [Mozilla’s code of conduct team][inclusion].
 
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[homepage]: https://www.contributor-covenant.org
-[security vulnerability]: https://github.com/halostatue/hoe-halostatue/security/advisories/new
+[advisory]: https://github.com/halostatue/hoe-halostatue/security/advisories/new
+[inclusion]: https://github.com/mozilla/inclusion

data/CONTRIBUTING.md

@@ -1,35 +1,124 @@
 # Contributing
 
-I value any contribution to Hoe::Halostatue you can provide: a bug report, a
-feature request, or code contributions. There are a few guidelines for
-contributing to Hoe::Halostatue:
-
-- Match my coding style.
-- Use a thoughtfully-named topic branch that contains your change. Rebase your
-  commits into logical chunks as necessary.
-- Use [quality commit messages][quality commit messages].
-- Do not change the version number; when your patch is accepted and a release is
-  made, the version will be updated at that point.
-- Submit a GitHub pull request with your changes.
-- New or changed behaviours require appropriate documentation.
-
-Hoe::Halostatue uses Ryan Davis's [Hoe][Hoe] to manage the release process, and
-it adds a number of rake tasks.
-
-## Workflow
-
-Here's the most direct way to get your work merged into the project:
-
-- Fork the project.
-- Clone your fork (`git clone git://github.com/<username>/hoe-halostatue.git`).
-- Create a topic branch to contain your change
-  (`git checkout -b my_awesome_feature`).
-- Hack away, add tests. Not necessarily in that order.
-- Make sure everything still passes by running `rake`.
-- If necessary, rebase your commits into logical chunks, without errors.
-- Push the branch up (`git push origin my_awesome_feature`).
-- Create a pull request against halostatue/hoe-halostatue and describe what your
-  change does and the why you think it should be merged.
+Contribution to hoe-halostatue is encouraged: bug reports, feature requests, or
+code contributions. New features should be proposed and discussed in an
+[issue][issues].
 
+Before contributing patches, please read the [Licence](./LICENCE.md).
+
+hoe-halostatue is governed under the
+[Contributor Covenant Code of Conduct][cccoc].
+
+## Code Guidelines
+
+I have several guidelines to contributing code through pull requests:
+
+- All code changes require tests. In most cases, this will be added or updated
+  unit tests. I use [Minitest][minitest].
+
+- I use code formatters, static analysis tools, and linting to ensure consistent
+  styles and formatting. There should be no warning output from test run
+  processes. I use [Standard Ruby][standardrb].
+
+- Proposed changes should be on a thoughtfully-named topic branch and organized
+  into logical commit chunks as appropriate.
+
+- Use [Conventional Commits][conventional] with my
+  [conventions](#commit-conventions).
+
+- Versions must not be updated in pull requests unless otherwise directed. This
+  means that you must not:
+
+  - Modify `VERSION` in `lib/hoe/halostatue/version.rb`. When your patch is
+    accepted and a release is made, the version will be updated at that point.
+
+  - Modify `hoe-halostatue.gemspec`; it is a generated file. (You _may_ use
+    `rake gemspec` to regenerate it if your change involves metadata related to
+    gem itself).
+
+  - Modify the `Gemfile`.
+
+- Documentation should be added or updated as appropriate for new or updated
+  functionality. The documentation is RDoc; hoe-halostatue does not use
+  extensions that may be present in alternative documentation generators.
+
+- All GitHub Actions checks marked as required must pass before a pull request
+  may be accepted and merged.
+
+- Add your name or GitHub handle to `CONTRIBUTORS.md` and a record in the
+  `CHANGELOG.md` as a separate commit from your main change. (Follow the style
+  in the `CHANGELOG.md` and provide a link to your PR.)
+
+- Include your DCO sign-off in each commit message (see [LICENCE](LICENCE.md)).
+
+## AI Contribution Policy
+
+hoe-halostatue is a library of intentional decisions (some of them possibly even
+wrong). It is extremely important that contributions of any sort be well
+understood by the submitter and that the developer can attest to the
+[Developer Certificate of Origin][dco] for each pull request (see
+[LICENCE](LICENCE.md)).
+
+Any contribution (bug, feature request, or pull request) that uses undeclared AI
+output will be rejected.
+
+## Test Dependencies
+
+hoe-halostatue naturally uses Ryan Davis's [Hoe][Hoe] to manage the release
+process, and it adds a number of rake tasks. You will mostly be interested in
+`rake`, which runs the tests the same way that `rake test` will do.
+
+To assist with the installation of the development dependencies for
+hoe-halostatue, I have provided the simplest possible Gemfile pointing to the
+(generated) `hoe-halostatue.gemspec` file. This will permit you to do
+`bundle install` to get the development dependencies.
+
+You can run tests with code coverage analysis by running `rake coverage`.
+
+## Commit Conventions
+
+hoe-halostatue has adopted a variation of the Conventional Commits format for
+commit messages. The following types are permitted:
+
+| Type    | Purpose                                               |
+| ------- | ----------------------------------------------------- |
+| `feat`  | A new feature                                         |
+| `fix`   | A bug fix                                             |
+| `chore` | A code change that is neither a bug fix nor a feature |
+| `docs`  | Documentation updates                                 |
+| `deps`  | Dependency updates, including GitHub Actions.         |
+
+I encourage the use of [Tim Pope's][tpope-qcm] or [Chris Beam's][cbeams]
+guidelines on the writing of commit messages
+
+I require the use of [git][trailers1] [trailers][trailers2] for specific
+additional metadata and strongly encourage it for others. The conditionally
+required metadata trailers are:
+
+- `Breaking-Change`: if the change is a breaking change. **Do not** use the
+  shorthand form (`feat!(scope)`) or `BREAKING CHANGE`.
+
+- `Signed-off-by`: this is required for all developers except me, as outlined in
+  the [Licence](./LICENCE.md#developer-certificate-of-origin).
+
+- `Fixes` or `Resolves`: If a change fixes one or more open [issues][issues],
+  that issue must be included in the `Fixes` or `Resolves` trailer. Multiple
+  issues should be listed comma separated in the same trailer:
+  `Fixes: #1, #5, #7`, but _may_ appear in separate trailers. While both `Fixes`
+  and `Resolves` are synonyms, only _one_ should be used in a given commit or
+  pull request.
+
+- `Related to`: If a change does not fix an issue, those issue references should
+  be included in this trailer.
+
+[cbeams]: https://cbea.ms/git-commit/
+[cccoc]: ./CODE_OF_CONDUCT.md
+[conventional]: https://www.conventionalcommits.org/en/v1.0.0/
+[dco]: licences/dco.txt
 [hoe]: https://github.com/seattlerb/hoe
-[quality commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[issues]: https://github.com/halostatue/hoe-halostatue/issues
+[minitest]: https://github.com/seattlerb/minitest
+[standardrb]: https://github.com/standardrb/standard
+[tpope-qcm]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[trailers1]: https://git-scm.com/docs/git-interpret-trailers
+[trailers2]: https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---trailerlttokengtltvaluegt

data/LICENCE.md

@@ -1,13 +1,15 @@
-## Licence
+# Licence
 
-Hoe::Halostatue is free software available under the MIT licence.
+- SPDX-License-Identifier: [MIT][mit]
 
-Copyright 2022-2025 Austin Ziegler (halostatue@gmail.com)
+- Copyright 2022-2025 Austin Ziegler. Portions copyright 2009 John Barnette.
 
-Portions copyright 2009 John Barnette
+The software in this repository is made available under the MIT license.
+
+## MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the 'Software'), to deal in
+this software and associated documentation files (the "Software"), to deal in
 the Software without restriction, including without limitation the rights to
 use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
 the Software, and to permit persons to whom the Software is furnished to do so,
@@ -16,9 +18,30 @@ subject to the following conditions:
 The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
 FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
 COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
 IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
 CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+## Developer Certificate of Origin
+
+All contributors **must** certify they are willing and able to provide their
+contributions under the terms of this project's licences with the certification
+of the [Developer Certificate of Origin (Version 1.1)](licences/dco.txt).
+
+Such certification is provided by ensuring that a `Signed-off-by`
+[commit trailer][trailer] is present on every commit:
+
+    Signed-off-by: FirstName LastName <email@example.org>
+
+The `Signed-off-by` trailer can be automatically added by git with the `-s` or
+`--signoff` option on `git commit`:
+
+```sh
+git commit --signoff
+```
+
+[mit]: https://spdx.org/licenses/MIT.html
+[trailer]: https://git-scm.com/docs/git-interpret-trailers

data/Manifest.txt

@@ -10,3 +10,4 @@ SECURITY.md
 lib/hoe/halostatue.rb
 lib/hoe/halostatue/strict_warnings.rb
 lib/hoe/halostatue/version.rb
+licences/dco.txt

data/README.md

@@ -41,9 +41,9 @@ automated release support.
 ### Improved Metadata URL Parsing
 
 Hoe::Halostatue provides an improved implementation for `Hoe#parse_urls`. The
-expected format is more or less the same, but accepts any left-aligned Markdown
-list (beginning with `-`, `+`, or `*`) and handles lists that wrap lines (such
-as the `changelog` entry at the top of this file).
+expected format is more or less the same, but accepts any left-aligned unordered
+Markdown list (beginning with `-`, `+`, or `*`) and handles lists that wrap
+lines (such as the `changelog` entry at the top of this file).
 
 It is more strict than the default `Hoe#parse_urls` because it only accepts the
 known aliases for the various RubyGems URI meta keys.
@@ -126,7 +126,7 @@ In the following example with no other configuration, a `v1.0.0.beta.1` tag will
 be created and pushed to the `origin` remote.
 
 ```console
-$ rake release VERSION=1.0.0 PRERELEASE=beta.1
+$ rake git:tag VERSION=1.0.0 PRERELEASE=beta.1
 ```
 
 The tag prefix can be with `self.git_release_tag_prefix`, which defaults to `v`.
@@ -134,6 +134,12 @@ The tag prefix can be with `self.git_release_tag_prefix`, which defaults to `v`.
 The created tag can be pushed to different remotes with `self.git_remotes`,
 which defaults to `["origin"]`.
 
+The tag will automatically be created when a release is pushed:
+
+```console
+$ rake release VERSION=1.0.0 PRERELEASE=beta.1
+```
+
 ### Trusted Release
 
 If `spec.trusted_release` is set to `true` changes will be made to the `release`

data/Rakefile

@@ -2,17 +2,24 @@
 
 $LOAD_PATH.unshift "lib"
 
+require "rubygems"
 require "hoe"
+require "rake/clean"
+require "rdoc/task"
 
 Hoe.plugin :halostatue
-
-Hoe.spec "hoe-halostatue" do
+Hoe.plugins.delete :debug
+Hoe.plugins.delete :git
+Hoe.plugins.delete :newb
+Hoe.plugins.delete :publish
+Hoe.plugins.delete :signing
+Hoe.plugins.delete :test
+
+hoe = Hoe.spec "hoe-halostatue" do
   developer "Austin Ziegler", "halostatue@gmail.com"
 
   self.trusted_release = ENV["rubygems_release_gem"] == "true"
 
-  self.extra_rdoc_files = FileList["*.rdoc"]
-
   license "MIT"
 
   spec_extras[:metadata] = ->(val) {
@@ -25,4 +32,19 @@ Hoe.spec "hoe-halostatue" do
   extra_deps << ["hoe-rubygems", "~> 1.0"]
 
   extra_dev_deps << ["standard", "~> 1.0"]
+  extra_dev_deps << ["rdoc", ">= 5.0", "< 8"]
+end
+
+task :version do
+  require "hoe/halostatue/version"
+  puts Hoe::Halostatue::VERSION
+end
+
+RDoc::Task.new do
+  _1.title = "Hoe::Halostatue -- Opinionated reconfiguration of Hoe"
+  _1.main = "README.md"
+  _1.rdoc_dir = "doc"
+  _1.rdoc_files = hoe.spec.require_paths - ["Manifest.txt"] + hoe.spec.extra_rdoc_files
+  _1.markup = "markdown"
 end
+task docs: :rerdoc

data/SECURITY.md

@@ -1,20 +1,16 @@
 # Hoe::Halostatue Security Policy
 
+## LLM-Generated Security Report Policy
+
+Absolutely no security reports will be accepted that have been generated by LLM
+agents.
+
 ## Supported Versions
 
 Security reports are accepted only for the most recent minor release.
 
 ## Reporting a Vulnerability
 
-Create a [draft security advisory][advisory]. Alternatively, send an email to
-[hoe-halostatue@halostatue.ca][email] with the text `hoe-halostatue` in the
-subject. Emails sent to this address should be encrypted using [age][age] with
-the following public key:
-
-```
-age1fc6ngxmn02m62fej5cl30lrvwmxn4k3q2atqu53aatekmnqfwumqj4g93w
-```
+Create a [private vulnerability report][advisory] with GitHub.
 
 [advisory]: https://github.com/halostatue/hoe-halostatue/security/advisories/new
-[age]: https://github.com/FiloSottile/age
-[email]: mailto:hoe-halostatue@halostatue.ca

data/lib/hoe/halostatue/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Hoe::Halostatue
-  VERSION = "2.1.1"
+  VERSION = "2.1.2" # :nodoc:
 end

data/lib/hoe/halostatue.rb

@@ -3,62 +3,75 @@
 require "shellwords"
 require_relative "halostatue/version"
 
+class Hoe; end # :nodoc:
+
 Hoe.plugin :gemspec2
 Hoe.plugin :markdown
 Hoe.plugin :rubygems
 
-# This module is a Hoe plugin. You can set its options in your Rakefile Hoe spec, like
-# this:
+# This module is a Hoe plugin which applies extremely opinionated reconfiguration to Hoe.
+# You can set its options in your Rakefile Hoe spec, like this:
+#
+# ```ruby
+# Hoe.plugin :halostatue
+#
+# Hoe.spec "myproj" do
+#   self.checklist = nil if ENV["rubygems_release_gem"] == "true"
+#   self.git_release_tag_prefix = "REL_"
+#   self.git_remotes << "myremote"
+# end
+# ```
+#
+# The `:git` plugin (built into Hoe since Hoe 4.5 or present in the `hoe-git` or
+# `hoe-git2` dependencies) should not be enabled as that implementation differs from what
+# is included here.
 #
-#    Hoe.plugin :git
+# ### Tasks
 #
-#    Hoe.spec "myproj" do
-#      self.checklist = nil if ENV["rubygems_release_gem"] == "true"
-#      self.git_release_tag_prefix = "REL_"
-#      self.git_remotes << "myremote"
-#    end
+# - `checklist`: Show the list of checklist questions.
+# - `git:manifest`: Update the manifest with Git's file list.
+# - `git:tag`: Create and push a tag.
 #
-# === Tasks
+# ### Options
 #
-# git:changelog:: Print the current changelog.
-# git:manifest::  Update the manifest with Git's file list.
-# git:tag::       Create and push a tag.
+# - `checklist`: An array of reminder questions that should be asked before a release, in
+#   the form "Did you... [question]?". The default questions are:
 #
-# === Options
+#   - `Bump the version?`
+#   - `Check everything in?`
+#   - `Review the manifest?`
+#   - `Update the README and docs?`
+#   - `Update the changelog?`
+#   - `Regenerate the gemspec?`
 #
-# - +checklist+: An array of reminder questions that should be asked before a release, in
-#   the form, "Did you... [question]?" You can see the defaults by running <tt>rake
-#   checklist</tt>. If the checklist is +nil+ or empty, the checklist will not shown
-#   during release. This is originally from hoe-doofus and called +doofus_checklist+.
+#   If the checklist is `nil` or empty, or trusted publishing is on, the checklist will
+#   not be shown.
 #
-# - +git_release_tag_prefix+: What do you want at the front of your release tags? The
-#   default is <tt>"v"</tt>.
+# - `git_release_tag_prefix`: What do you want at the front of your release tags? The
+#   default is `"v"`.
 #
-# - +git_remotes+: Which remotes do you want to push tags, etc. to? The default is
-#   <tt>%w[origin]</tt>
+# - `git_remotes`: Which remotes do you want to push tags, etc. to? The default is
+#   `%w[origin]`.
 #
-# - +git_tag_enabled+: Whether a git tag should be created on release. The default is
-#   +true+.
+# - `git_tag_enabled`: Whether a git tag should be created on release. The default is
+#   `true`.
 module Hoe::Halostatue
   # Indicates that this release is being run as part of a trusted release workflow.
-  # [default: +false+]
+  # [default: `false`]
   attr_accessor :trusted_release
 
   # An array of reminder questions that should be asked before a release, in the form,
-  # "Did you... [question]?" You can see the defaults by running <tt>rake checklist</tt>.
-  #
-  # If the checklist is +nil+ or empty, the checklist will not shown during release.
   attr_accessor :checklist
 
   # What do you want at the front of your release tags?
-  # [default: <tt>"v"</tt>]
+  # [default: `"v"`]
   attr_accessor :git_release_tag_prefix
 
   # Which remotes do you want to push tags, etc. to?
-  # [default: <tt>%w[origin]</tt>]
+  # [default: `%w[origin]`]
   attr_accessor :git_remotes
 
-  # Should git tags be created on release? [default: +true+]
+  # Should git tags be created on release? [default: `true`]
   attr_accessor :git_tag_enabled
 
   def initialize_halostatue # :nodoc:
@@ -95,10 +108,10 @@ module Hoe::Halostatue
     self.trusted_release = false
   end
 
-  LINKS = /\[(?<name>.+?)\](?:\(.+?\)|\[.+?\])/
+  LINKS = /\[(?<name>.+?)\](?:\(.+?\)|\[.+?\])/ # :nodoc:
 
   def define_halostatue_tasks # :nodoc:
-    desc "Show a reminder for steps I frequently forget"
+    desc "Show a reminder for steps frequently forgotten in a manual release"
     task :checklist do
       if checklist.nil? || checklist.empty?
         puts "Checklist is empty."
@@ -147,12 +160,11 @@ module Hoe::Halostatue
     desc "Update the manifest with Git's file list. Use Hoe's excludes."
     task "git:manifest" do
       with_config do |config, _|
-        files = __run_git("ls-files").split($/)
-        files.reject! { |f| f =~ config["exclude"] }
+        files = __run_git("ls-files")
+          .split($/)
+          .grep_v(config["exclude"])
 
-        File.open "Manifest.txt", "w" do |f|
-          f.puts files.sort.join("\n")
-        end
+        File.write "Manifest.txt", files.sort.join("\n") + "\n"
       end
     end
 
@@ -162,7 +174,7 @@ module Hoe::Halostatue
         tag = ENV["TAG"]
         ver = ENV["VERSION"] || version
         pre = ENV["PRERELEASE"] || ENV["PRE"]
-        ver += ".#{pre}" if pre
+        ver += ".#{pre}" if pre && !ver.ends_with?(pre)
         tag ||= "#{git_release_tag_prefix}#{ver}"
 
         git_tag_and_push tag
@@ -178,6 +190,8 @@ module Hoe::Halostatue
     task release_to: "git:tag"
   end
 
+  private
+
   def __git(command, *params)
     "git #{command.shellescape} #{params.compact.shelljoin}"
   end
@@ -193,26 +207,17 @@ module Hoe::Halostatue
   def git_tag_and_push tag
     msg = "Tagging #{tag}."
 
-    if git_svn?
-      sh __git("svn", "tag", tag, "-m", msg)
-    else
-      flags =
-        if __run_git("config", "--get", "user.signingkey").empty?
-          nil
-        else
-          "-s"
-        end
+    flags = "-s" unless __run_git("config", "--get", "user.signingkey").empty?
 
-      sh __git("tag", flags, "-f", tag, "-m", msg)
-      git_remotes.each { |remote| sh __git("push", "-f", remote, "tag", tag) }
-    end
+    sh __git("tag", flags, "-f", tag, "-m", msg)
+    git_remotes.each { |remote| sh __git("push", "-f", remote, "tag", tag) }
   end
 
   # This replaces Hoe#parse_urls with something that works better for Markdown.
   module ParseUrls # :nodoc:
     def parse_urls text
       keys = Hoe::URLS_TO_META_MAP.keys.join("|")
-      pattern = %r{^[-+*]\s+(#{keys})\s+::\s+[<]?(\w+://[^>\s]+)[>]?}m
+      pattern = %r{^[-+*]\s+(#{keys})\s+::\s+<?(\w+://[^>\s]+)>?}m
 
       text.scan(pattern).to_h
     end

data/licences/dco.txt

@@ -0,0 +1,34 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hoe-halostatue
 version: !ruby/object:Gem::Version
-  version: 2.1.1
+  version: 2.1.2
 platform: ruby
 authors:
 - Austin Ziegler
@@ -91,20 +91,20 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '4.0'
+        version: '5.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '7'
+        version: '8'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '4.0'
+        version: '5.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '7'
+        version: '8'
 description: |-
   Hoe::Halostatue is a [Hoe][hoe] meta-plugin that provides improved support for
   Markdown README files, provides features from other plugins, and enables
@@ -122,6 +122,7 @@ extra_rdoc_files:
 - Manifest.txt
 - README.md
 - SECURITY.md
+- licences/dco.txt
 files:
 - CHANGELOG.md
 - CODE_OF_CONDUCT.md
@@ -135,6 +136,7 @@ files:
 - lib/hoe/halostatue.rb
 - lib/hoe/halostatue/strict_warnings.rb
 - lib/hoe/halostatue/version.rb
+- licences/dco.txt
 homepage: https://github.com/halostatue/halostatue-data/
 licenses:
 - MIT