kinetic_sdk 5.0.27 → 5.0.28

data/gems/mime-types-data-3.2025.0107/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant 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.
+
+## 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
+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 [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.
+
+### 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>.
+
+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]: https://www.contributor-covenant.org
+[Mozilla CoC]: https://github.com/mozilla/diversity

data/gems/{mime-types-data-3.2024.0305/Contributing.md → mime-types-data-3.2025.0107/CONTRIBUTING.md}

@@ -1,4 +1,4 @@
-## Contributing
+# Contributing
 
 Contributions to mime-types-data is encouraged in any form: a bug report, new
 MIME type definitions, or additional code to help manage the MIME types. As with
@@ -10,8 +10,8 @@ acceptance of your code contributions:
 - Use a thoughtfully-named topic branch that contains your change. Rebase your
   commits into logical chunks as necessary.
 - Use [quality commit messages][qcm].
-- Do not change the version number; when your patch is accepted and a release
-  is made, the version will be updated at that point.
+- 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 new or updated documentation.
 
@@ -21,7 +21,7 @@ implementation that wishes to use the data as a MIME types registry, so I am
 particularly interested in tools that will create a mime-types-data package for
 other languages.
 
-### Adding or Modifying MIME Types
+## Adding or Modifying MIME Types
 
 The Ruby mime-types gem loads its data from files encoded in the `data`
 directory in this gem by loading `mime-types-data` and reading
@@ -60,7 +60,7 @@ If you are making a change for a private fork, use `rake convert:yaml:json` to
 convert the YAML to JSON, or `rake convert:yaml:columnar` to convert it to the
 new columnar format.
 
-#### Updating Types from the IANA or Apache Lists
+### Updating Types from the IANA or Apache Lists
 
 If you are maintaining a private fork and wish to update your copy of the MIME
 types registry used by this gem, you can do this with the rake tasks:
@@ -70,71 +70,47 @@ $ rake mime:iana
 $ rake mime:apache
 ```
 
-##### A Note on Provisional Types
+#### A Note on Provisional Types
 
-The file `types/provisional-standard-types.yaml` contains the provisionally
-registered types from IANA. Per IANA,
+Provisionally registered types from IANA are contained in the `types/*.yaml`
+files. Per IANA,
 
 > This registry, unlike some other provisional IANA registries, is only for
 > temporary use. Entries in this registry are either finalized and moved to the
 > main media types registry or are abandoned and deleted. Entries in this
 > registry are suitable for use for development and test purposes only.
 
-The provisional types file is rewritten when updated, so pull requests to
-manually promote or customize provisional types (such as with extensions). It is
-recommended that any updates required to the data be performed in your
-application if you require provisional types.
+Provisional types are rewritten when updated, so pull requests to manually
+customize provisional types (such as with extensions) are considered lower
+priority. It is recommended that any updates required to the data be performed
+in your application if you require provisional types.
 
-### Development Dependencies
+## Development Dependencies
 
-mime-types-data uses Ryan Davis’s {Hoe}[https://github.com/seattlerb/hoe] to
-manage the release process, and it adds a number of rake tasks. You will mostly
-be interested in:
+## Test Dependencies
 
-```sh
-$ rake
-```
-
-which runs the tests the same way that:
-
-```sh
-$ rake test
-$ rake travis
-```
-
-will do.
-
-To assist with the installation of the development dependencies for
-mime-types-data, I have provided the simplest possible Gemfile pointing to the
-(generated) `mime-types-data.gemspec` file. This will permit you to do:
-
-```sh
-$ bundle install
-```
-
-to get the development dependencies. If you aleady have `hoe` installed, you
-can accomplish the same thing with:
+mime-types-data 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 tests the same way that `rake test` does.
 
-```sh
-$ rake newb
-```
-
-This task will install any missing dependencies, run the tests/specs, and
+To assist with the installation of the development dependencies for mime-types,
+I have provided the simplest possible Gemfile pointing to the (generated)
+`mime-types-data.gemspec` file. This permits `bundle install` for dependencies.
+If you already have `hoe` installed, you can accomplish the same thing with
+`rake newb`. This task will install any missing dependencies, run the tests, and
 generate the RDoc.
 
-You can run tests with code coverage analysis by running:
-
-```sh
-$ rake test:coverage
-```
+You can run tests with code coverage analysis by running `rake test:coverage`.
 
 ### Workflow
 
 Here's the most direct way to get your work merged into the project:
 
 - Fork the project.
-- Clone down your fork (`git clone git://github.com/<username>/mime-types-data.git`).
-- Create a topic branch to contain your change (`git checkout -b my\_awesome\_feature`).
+- Clone down your fork
+  (`git clone git://github.com/<username>/mime-types-data.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.
@@ -142,103 +118,33 @@ Here's the most direct way to get your work merged into the project:
 - Create a pull request against mime-types/mime-types-data and describe what
   your change does and the why you think it should be merged.
 
-### The Release Process
+## The Release Process
 
-The release process needs automation; as it includes generating code and
-committing to the repository, it is not clear how this will happen safely.
+The release process is much more automated than it used to be, as regular
+updates are performed with GitHub actions on Tuesdays. Before release, however,
+a final step of checking for IANA updates should be performed.
 
 1. Review any outstanding issues or pull requests to see if anything needs to be
-   addressed. This is necessary because there is currently no automated source
-   for extensions for the thousands of MIME entries. (Suggestions and/or pull
+   addressed. This is necessary because there is no automated source for
+   extensions for the thousands of MIME entries. (Suggestions and/or pull
    requests for same would be deeply appreciated.)
 2. `bundle install`
 3. `bundle exec rake mime:apache`
 4. `bundle exec rake mime:iana`
 5. Review the changes to make sure that the changes are sane. The IANA data
    source changes from time to time, resulting in big changes or even a broken
-   step 4. (The most recent change was the addition of the font/\* top-level
+   step 4. (The most recent change was the addition of the `font/*` top-level
    category.)
 6. `bundle exec rake convert`
 7. `bundle exec rake update:version`
-8. Write up the changes in History.md. If any PRs have been merged, these should
-   be noted specifically.
+8. Write up the changes in `CHANGELOG.md`. If any PRs have been merged, these
+   should be noted specifically and contributions should be added in
+   `Contributing.md`.
 9. Commit the changes and push to GitHub.
 10. `bundle exec rake release VERSION=newversion`
 
-### Automating the Release
-
-If anyone wishes to provide suggestions on automation, this would be a two-phase
-process:
-
-1. A system would need to periodically create PRs to the GitHub repository with
-   the output of the following commands (steps 2, 3, and 4):
-
-   ```sh
-   bundle install
-   bundle exec rake mime:apache
-   bundle exec rake mime:iana
-   git add .
-   git commit -m "[Automated] MIME Type update for $(date)"
-   # Somehow make the PR from here.
-   ```
-
-2. Once this PR is approved and merged, the next steps would be conversion,
-   version update, automatic update of History.md, and release (steps 6–10).
-
-This is based on an issue [#18][].
-
-### Contributors
-
-- Austin Ziegler created mime-types.
-
-Thanks to everyone else who has contributed to mime-types:
-
-- Aaron Patterson
-- Aggelos Avgerinos
-- Alessio Parma
-- Alex Balhatchet
-- Andre Pankratz
-- Andrey Eremin
-- Andy Brody
-- Arnaud Meuret
-- Bradley Meck
-- Brandon Galbraith
-- Chris Gat
-- Chris Salzberg
-- David Genord
-- Eric Marden
-- Garret Alfert
-- Godfrey Chan
-- Greg Brockman
-- Hans de Graaff
-- Henrik Hodne
-- Jeremy Evans
-- John Gardner
-- Jon Sneyers
-- Jonas Petersen
-- Juanito Fatas
-- Keerthi Siva
-- Ken Ip
-- Łukasz Śliwa
-- Lucia
-- Martin d'Allens
-- Mauricio Linhares
-- Mohammed Gad
-- Myk Klemme
-- nycvotes-dev
-- Postmodern
-- Richard Hirner
-- Richard Hurt
-- Richard Schneeman
-- Robert Buchberger
-- Samuel Williams
-- Sergio Baptista
-- Tao Guo
-- Thomas Leese
-- Tibor Szolár
-- Todd Carrico
-- Yoran Brondsema
+This is based on an issue [#18][#18].
 
 [qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
 [rmt]: https://github.com/mime-types/ruby-mime-types/
-[#18]: https://github.com/mime-types/mime-types-data/issues/18
+[hoe]: https://github.com/seattlerb/hoe

data/gems/mime-types-data-3.2025.0107/CONTRIBUTORS.md

@@ -0,0 +1,52 @@
+# Contributors
+
+- Austin Ziegler created mime-types.
+
+Thanks to everyone else who has contributed to mime-types:
+
+- Aaron Patterson
+- Aggelos Avgerinos
+- Alessio Parma
+- Alex Balhatchet
+- Andre Pankratz
+- Andrey Eremin
+- Andy Brody
+- Arnaud Meuret
+- Bradley Meck
+- Brandon Galbraith
+- Chris Gat
+- Chris Salzberg
+- David Genord
+- Eric Marden
+- Garret Alfert
+- Godfrey Chan
+- Greg Brockman
+- Hans de Graaff
+- Henrik Hodne
+- Jeremy Evans
+- John Gardner
+- Jon Sneyers
+- Jonas Petersen
+- Juanito Fatas
+- Keerthi Siva
+- Ken Ip
+- Łukasz Śliwa
+- Lucia
+- Martin d'Allens
+- Mauricio Linhares
+- Mohammed Gad
+- Myk Klemme
+- nycvotes-dev
+- Postmodern
+- Richard Hirner
+- Richard Hurt
+- Richard Schneeman
+- Robert Buchberger
+- Samuel Williams
+- Sergio Baptista
+- Shane Eskritt
+- Tao Guo
+- Thomas Leese
+- Tibor Szolár
+- Todd Carrico
+- Yoran Brondsema

data/gems/{mime-types-data-3.2024.0305/Licence.md → mime-types-data-3.2025.0107/LICENCE.md}

@@ -1,6 +1,6 @@
 ## Licence
 
-- Copyright 2003–2021 Austin Ziegler and other contributors.
+- Copyright 2003–2025 Austin Ziegler and other contributors.
 
 The software in this repository is made available under the MIT license.
 

data/gems/{mime-types-data-3.2024.0305 → mime-types-data-3.2025.0107}/Manifest.txt

@@ -1,10 +1,12 @@
-Code-of-Conduct.md
-Contributing.md
-History.md
-Licence.md
+CHANGELOG.md
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+CONTRIBUTORS.md
+LICENCE.md
 Manifest.txt
 README.md
 Rakefile
+SECURITY.md
 data/content_type_mime.db
 data/ext_mime.db
 data/mime-types.json
@@ -18,16 +20,3 @@ data/mime.use_instead.column
 data/mime.xrefs.column
 lib/mime-types-data.rb
 lib/mime/types/data.rb
-types/application.yaml
-types/audio.yaml
-types/chemical.yaml
-types/conference.yaml
-types/drawing.yaml
-types/font.yaml
-types/image.yaml
-types/message.yaml
-types/model.yaml
-types/multipart.yaml
-types/text.yaml
-types/video.yaml
-types/world.yaml

data/gems/{mime-types-data-3.2024.0305 → mime-types-data-3.2025.0107}/README.md

@@ -1,8 +1,8 @@
 # mime-types-data
 
 - home :: https://github.com/mime-types/mime-types-data/
-- code :: https://github.com/mime-types/mime-types-data/
 - issues :: https://github.com/mime-types/mime-types-data/issues
+- code :: https://github.com/mime-types/mime-types-data/
 
 ## Description
 
@@ -13,11 +13,11 @@ extensions to look up the likely MIME type definitions.
 
 ### About MIME Media Types
 
-MIME media types are used in MIME-compliant communications, as in e-mail or
-HTTP traffic, to indicate the type of content which is transmitted. The
-registry provided in mime-types-data contains detailed information about MIME
-entities. There are many types defined by RFCs and vendors, so the list is long
-but invariably; don't hesitate to offer additional type definitions for
+MIME media types are used in MIME-compliant communications, as in e-mail or HTTP
+traffic, to indicate the type of content which is transmitted. The registry
+provided in mime-types-data contains detailed information about MIME entities.
+There are many types defined by RFCs and vendors, so the list is long but
+invariably; don't hesitate to offer additional type definitions for
 consideration. MIME type definitions found in mime-types are from RFCs, W3C
 recommendations, the [IANA Media Types registry][registry], and user
 contributions. It conforms to RFCs 2045 and 2231.
@@ -26,20 +26,20 @@ contributions. It conforms to RFCs 2045 and 2231.
 
 This registry contains the MIME media types in four formats:
 
-- A YAML format matching the Ruby mime-types library objects (MIME::Type).
-  This is the primary user-editable format for developers. It is _not_
-  shipped with the gem due to size considerations.
+- A YAML format matching the Ruby mime-types library objects (MIME::Type). This
+  is the primary user-editable format for developers. It is _not_ shipped with
+  the gem due to size considerations.
 - A JSON format converted from the YAML format. Prior to Ruby mime-types 3.0,
   this was the main consumption format and is still recommended for any
-  implementation that does not wish to implement the columnar format, which
-  has a significant implementation effort cost.
-- An encoded text format splitting the data for each MIME type across
-  multiple files. This columnar data format reduces the minimal data load
-  substantially, resulting in a performance improvement at the cost of more
-  complex code for loading the data on-demand. This is the default format for
-  Ruby mime-types 3.0.
-- An encoded text format for use with [`mini_mime`][] (as of 3.2021.1108). This
-  can be enabled with:
+  implementation that does not wish to implement the columnar format, which has
+  a significant implementation effort cost.
+- An encoded text format splitting the data for each MIME type across multiple
+  files. This columnar data format reduces the minimal data load substantially,
+  resulting in a performance improvement at the cost of more complex code for
+  loading the data on-demand. This is the default format for Ruby mime-types
+  3.0.
+- An encoded text format for use with [`mini_mime`][minimime]. This can be
+  enabled with:
 
   ```ruby
   MiniMime::Configuration.ext_db_path =
@@ -50,24 +50,24 @@ This registry contains the MIME media types in four formats:
 
 ## mime-types-data Modified Semantic Versioning
 
-mime-types-data uses a heavily modified [Semantic Versioning][] scheme to
-indicate that the data formats compatibility based on a `SCHEMA` version and
-the date of the data update: `SCHEMA.YEAR.MONTHDAY`.
+mime-types-data uses a heavily modified [Semantic Versioning][semver] scheme to
+indicate that the data formats compatibility based on a `SCHEMA` version and the
+date of the data update: `SCHEMA.YEAR.MONTHDAY`.
 
 1. If an incompatible data format change is made to any of the supported
-   formts, `SCHEMA` will be incremented. The current `SCHEMA` is 3, supporting
+   formats, `SCHEMA` will be incremented. The current `SCHEMA` is 3, supporting
    the YAML, JSON, and columnar formats required for Ruby mime-types 3.0.
 
-2. When the data is updated, the `YEAR.MONTHDAY` combination will be updated.
-   An update on the last day of October 2015 would be written as `2015.1031`,
+2. When the data is updated, the `YEAR.MONTHDAY` combination will be updated. An
+   update on the last day of October 2015 would be written as `2015.1031`,
    resulting in the full version of `3.2015.1031`.
 
 3. If multiple versions of the data need to be released on the same day due to
-   error, there will be an additional `REVISION` field incremented on the end
-   of the version. Thus, if three revisions need to be published on October
-   31st, 2015, the last release would be `3.2015.1031.2` (remember that the
-   first release has an implied `0`.)
+   error, there will be an additional `REVISION` field incremented on the end of
+   the version. Thus, if three revisions need to be published on October 31st,
+   2015, the last release would be `3.2015.1031.2` (remember that the first
+   release has an implied `0`.)
 
 [registry]: https://www.iana.org/assignments/media-types/media-types.xhtml
-[semantic versioning]: http://semver.org/
-[`mini_mime`]: https://github.com/discourse/mini_mime
+[semver]: http://semver.org/
+[minimime]: https://github.com/discourse/mini_mime

data/gems/mime-types-data-3.2025.0107/Rakefile

@@ -0,0 +1,88 @@
+# frozen_string_literal: true
+
+require "rubygems"
+require "hoe"
+require "rake/clean"
+
+$LOAD_PATH.unshift("lib")
+$LOAD_PATH.unshift("support")
+
+Hoe.plugin :halostatue
+
+Hoe.plugins.delete :debug
+Hoe.plugins.delete :newb
+Hoe.plugins.delete :publish
+Hoe.plugins.delete :signing
+
+Hoe.spec "mime-types-data" do
+  developer("Austin Ziegler", "halostatue@gmail.com")
+
+  require_ruby_version ">= 2.0"
+
+  license "MIT"
+
+  spec_extras[:metadata] = ->(val) {
+    val.merge!({"rubygems_mfa_required" => "true"})
+  }
+
+  extra_dev_deps << ["hoe", "~> 4.0"]
+  extra_dev_deps << ["hoe-halostatue", "~> 1.0"]
+  extra_dev_deps << ["mime-types", ">= 3.4.0", "< 4"]
+  extra_dev_deps << ["nokogiri", "~> 1.6"]
+  extra_dev_deps << ["rake", ">= 10.0", "< 14"]
+  extra_dev_deps << ["standard", "~> 1.0"]
+end
+
+namespace :mime do
+  desc "Download the current MIME type registrations from IANA."
+  task :iana, [:destination] do |_, args|
+    require "iana_registry"
+    IANARegistry.download(to: args.destination)
+  end
+
+  desc "Download the current MIME type configuration from Apache."
+  task :apache, [:destination] do |_, args|
+    require "apache_mime_types"
+    ApacheMIMETypes.download(to: args.destination)
+  end
+end
+
+namespace :release do
+  desc "Prepare a new release"
+  task :prepare do
+    require "prepare_release"
+
+    PrepareRelease.new
+      .download_and_convert
+      .write_updated_version
+      .write_updated_history
+      .rake_git_manifest
+      .rake_gemspec
+  end
+
+  desc "Prepare a new release for use with GitHub Actions"
+  task :gha do
+    require "prepare_release"
+
+    PrepareRelease.new
+      .download_and_convert
+      .write_updated_version
+      .write_updated_history
+      .rake_git_manifest
+      .rake_gemspec
+      .as_gha_vars
+  end
+end
+
+desc "Default conversion from YAML to JSON and Columnar"
+task :convert do
+  require "prepare_release"
+
+  PrepareRelease.new.convert_types
+end
+
+Rake::Task["gem"].prerequisites.unshift("convert")
+Rake::Task["gem"].prerequisites.unshift("git:manifest")
+Rake::Task["gem"].prerequisites.unshift("gemspec")
+
+# vim: syntax=ruby

data/gems/mime-types-data-3.2025.0107/SECURITY.md

@@ -0,0 +1,7 @@
+# mime-types-data Security
+
+## Security contact information
+
+To report a security vulnerability, please use the
+[Tidelift security contact](https://tidelift.com/security). Tidelift will
+coordinate the fix and disclosure.