chore: Refresh metadata files

.gitignore

@@ -1,15 +1,12 @@
-*.swp
-*~
+*.gem
+.byebug_history
 .rake_tasks~
 .source_index
-.vagrant
 Gemfile.lock
-Vagrantfile
-coverage
-doc
-html
-pkg
-publish
+coverage/
+doc/
+html/
+pkg/
+publish/
 test/cache.tst
 tmp/
-.byebug_history

.hoerc

@@ -6,14 +6,14 @@ exclude: !ruby/regexp '/
   )$
   |
   \.(?:
-      bundle|
-      git|
-      github|
-      hg|
-      idea|
-      svn|
-      vagrant
-    )\/
+    bundle |
+    git |
+    github |
+    hg |
+    idea |
+    svn |
+    vagrant
+  )\/
   |
   [Aa]ppraisals
   |
@@ -28,23 +28,21 @@ exclude: !ruby/regexp '/
     standard.* |
     travis |
     unused
-    )\.yml$
+  )\.yml$
   |
   (?i:TAGS)$
   |
   \.(?:
-      DS_Store |
-      autotest |
-      byebug_history |
-      gemtest |
-      gitattributes |
-      gitignore |
-      hoerc |
-      minitest.rb |
-      simplecov-prelude.rb
+    DS_Store |
+    autotest |
+    byebug_history |
+    gemtest |
+    gitattributes |
+    gitignore |
+    hoerc |
+    minitest.rb |
+    simplecov-prelude.rb
   )$
   |
   \.gemspec$
-  |
-  Vagrantfile$
   /x'

Code-of-Conduct.md

@@ -2,73 +2,127 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-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.
 
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
 
-Examples of unacceptable behavior by participants include:
+## Our Standards
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+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
 
-## Our Responsibilities
+## Enforcement Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+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.
 
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors 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.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+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 by contacting the project team at [INSERT EMAIL ADDRESS]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+reported to the community leaders responsible for enforcement at [INSERT CONTACT
+METHOD]. 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.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+### 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 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+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>.
+
+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>.
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[homepage]: https://www.contributor-covenant.org
+[Mozilla CoC]: https://github.com/mozilla/diversity

Gemfile

@@ -1,22 +1,6 @@
-# frozen_string_literal: true
-
-# NOTE: This file is not the canonical source of dependencies. Edit the
-# Rakefile, instead.
+# NOTE: This file is not the canonical source of dependencies. Edit the Rakefile, instead.
 
 source "https://rubygems.org/"
 
-mime_version =
-  if RUBY_VERSION < "1.9"
-    gem "rdoc", "< 4.0"
-    gem "rake", "~> 10.0"
-    "1.25"
-  elsif RUBY_VERSION < "2.0"
-    gem "rdoc", "< 6.0"
-    "2.0"
-  elsif RUBY_VERSION >= "2.0"
-    "3.0"
-  end
-
-gem "mime-types", "~> #{mime_version}"
-
+# TODO: Remove this for minitar 1 since archive-tar-minitar is going away
 gemspec :name => "minitar"

History.md

@@ -1,6 +1,6 @@
 # History
 
-## 0.12 / 2024-08-DD
+## 0.12 / 2024-08-06
 
 - Properly handle very long GNU filenames, resolving [#46][].
 - Handle very long GNU filenames that are 512 or more bytes, resolving [#45][].

Licence.md

@@ -3,8 +3,8 @@
 minitar is free software that may be redistributed and/or modified under the
 terms of Ruby’s licence or the Simplified BSD licence.
 
-* Copyright 2004–2017 Austin Ziegler.
-* Portions copyright 2004 Mauricio Julio Fernández Pradier.
+- Copyright 2004–2024 Austin Ziegler.
+- Portions copyright 2004 Mauricio Julio Fernández Pradier.
 
 ### Simplified BSD Licence
 

README.rdoc

@@ -3,7 +3,7 @@
 home :: https://github.com/halostatue/minitar/
 code :: https://github.com/halostatue/minitar/
 bugs :: https://github.com/halostatue/minitar/issues
-rdoc :: http://rdoc.info/gems/minitar/
+rdoc :: https://rdoc.info/gems/minitar/
 cli  :: https://github.com/halostatue/minitar-cli
 
 == Description

Rakefile

@@ -22,32 +22,6 @@ Hoe.spec "minitar" do
 
   require_ruby_version ">= 1.8"
 
-  # This is a hack because of an issue with Hoe 3.26, but I'm not sure which
-  # hoe version introduced this issue or if it's a JRuby issue. This issue is
-  # demonstrable in lib/hoe.rb at line 676, which is (reformatted for space):
-  #
-  # ```ruby
-  # readme =
-  #   input
-  #     .lines
-  #     .chunk { |l| l[/^(?:=+|#+)/] || "" } # # chunk is different somehow
-  #     .map(&:last) # <-- HERE: "#" does not respond to #last
-  #     .each_slice(2)
-  #     .map { |k, v|
-  #       kp = k.join
-  #       kp = kp.strip.chomp(":").split.last.downcase if k.size == 1
-  #       [kp, v.join.strip]
-  #     }
-  #     .to_h
-  # ```
-  #
-  # We don't *ship* with JRuby, but use it in CI only, so this is here at least
-  # temporarily.
-  if RUBY_PLATFORM.match?(/java/)
-    self.summary = self.description = "Description for testing"
-    self.homepage = "https://github.com/KineticCafe/app-identity/tree/main/ruby/"
-  end
-
   self.licenses = ["Ruby", "BSD-2-Clause"]
 
   self.post_install_message = <<-EOS

support/hoe/deprecated_gem.rb

@@ -1,6 +1,8 @@
 # A Hoe plug-in to provide a second, linked gemspec, for a gem that has been
 # deprecated in favour of a modern name. (The name is an artifact of Hoe's
 # plugin loading.)
+#
+# TODO: Remove for 1.0 since archive-tar-minitar is going away
 module Hoe::Deprecated_Gem # standard:disable Naming/ClassAndModuleCamelCase
   def linked_spec(spec)
     permitted_classes = %w[