miyabi 0.4.0 → 0.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: acad0974c78fe7cac1841d823ea439e671a69eb3dad915ef8adcfcfdd0f4fdda
-  data.tar.gz: 4bfc100695a36d2d22fc68295fa8cf0441d2e7bba02e2b300b06949e079ce87a
+  metadata.gz: bb04c2510122b519fffedbe7da7a7bbc231fe2691dc25b72b6892ecbb3cccdd4
+  data.tar.gz: 7c7ccea8e988db4b4e8e634b559d3143ced7b3722bc4c912c5ea98234fdb0839
 SHA512:
-  metadata.gz: a19ce621920fa07fb6905f96891aeb26cb05987c8e5e6467042258ee94463fb9e6254b68fe7245d629a1ab7f929c1a711e446fbbf875574302e081fae0339e5f
-  data.tar.gz: b82e68c6a79e5fb0360abf73b1989bd95e012a6e6adac69411fa1672cac9709227b2e0a268e3c7319dc5406bb14da7bcafc7c47a7ded18658fa9a6df33c78e71
+  metadata.gz: d75a4b99bba5e2e6a0dd267a94dc3a36dd0e0fac3ec16afcd43cb35f61341c9628e35448acba8bc099d96bce32a6ef7355cc623a57cce80c30c9ef8da5c19240
+  data.tar.gz: c521af659f19b5a73b84308f65f9ce15b38b29093c986d8f395dc59157bad7ed8926752850c7f67b279038fdb83962ac6aa8a1e36e7e2691eab79acbf2aee6d0

data/.github/workflows/release.yaml

@@ -0,0 +1,31 @@
+# https://guides.rubygems.org/trusted-publishing/releasing-gems/
+name: Release
+on:
+  push:
+    tags:
+      - '*'
+  workflow_dispatch:
+jobs:
+  push:
+    name: Push gem to RubyGems.org
+    runs-on: ubuntu-latest
+
+    permissions:
+      id-token: write # IMPORTANT: this permission is mandatory for trusted publishing
+      contents: write # IMPORTANT: this permission is required for `rake release` to push the release tag
+
+    environment: release
+
+    steps:
+      # Set up
+      - uses: actions/checkout@v6
+        with:
+          persist-credentials: false
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          bundler-cache: true
+          ruby-version: ruby
+
+      # Release
+      - uses: rubygems/release-gem@v1

data/CHANGELOG.md

@@ -9,6 +9,10 @@ The format is based on [Keep a Changelog][cl], and this project adheres to [Sema
 
 ## [Unreleased]
 
+## 0.4.1
+
+Maintenance release.  Mainly for enabling trusted publishing.
+
 ## 0.4.0
 
 Make `to_kanhira` method optional.  If you still need this, install Nokogiri gem and:

data/README.md

@@ -54,21 +54,14 @@ If you use the GNU Guix, `guix shell` to enter the development environment, then
 ## Contributing
 
 Bug reports and pull requests are welcome on
-[GitHub](https://github.com/gemmaro/miyabi).  This project is intended to be a
-safe, welcoming space for collaboration, and contributors are expected to
-adhere to the [Contributor Covenant](http://contributor-covenant.org) code of
-conduct.
+[GitHub](https://github.com/gemmaro/miyabi).
 
 ## License
 
 The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
 
-## Code of Conduct
+## Links and Related Works
 
-Everyone interacting in the Miyabi project’s codebases, issue trackers, chat
-rooms and mailing lists is expected to follow the [code of
-conduct](https://github.com/gemmaro/miyabi/blob/master/CODE_OF_CONDUCT.md).
+This work has been initially created by isy at [isy/miyabi](https://github.com/isy/miyabi).
 
-## Related Works
-
-[jaconv](https://github.com/ikegami-yukino/jaconv) (Python library)
+There are other similar libraries such as [jaconv](https://github.com/ikegami-yukino/jaconv) (Python library).

data/lib/miyabi/version.rb

@@ -1,3 +1,3 @@
 module Miyabi
-  VERSION = '0.4.0'
+  VERSION = '0.4.1'
 end

data/manifest.scm

@@ -2,4 +2,4 @@
              (gnu packages ruby-xyz)
              (gnu packages ruby-check)
              (guix profiles))
-(packages->manifest (list ruby-nokogiri ruby-rspec ruby-3.1 ruby-rubocop))
+(packages->manifest (list ruby-nokogiri ruby-rspec ruby-3.3 ruby-rubocop))

data/miyabi.gemspec

@@ -22,4 +22,5 @@ Gem::Specification.new do |spec|
   spec.required_ruby_version = '>= 3.0'
 
   spec.add_development_dependency 'rspec', '~> 3.12'
+  spec.add_development_dependency 'rake'
 end

metadata

@@ -1,15 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: miyabi
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
 platform: ruby
 authors:
 - Hironori Akaishi
 - gemmaro
-autorequire:
 bindir: bin
 cert_chain: []
-date: 2025-07-21 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -25,6 +24,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '3.12'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 description: Format Japanese characters
 email:
 - ah.gm3622@gmail.com
@@ -34,12 +47,12 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".envrc"
+- ".github/workflows/release.yaml"
 - ".gitignore"
 - ".rspec"
 - ".rubocop.yml"
 - ".rubocop_todo.yml"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -60,7 +73,6 @@ licenses:
 - MIT
 metadata:
   rubygems_mfa_required: 'true'
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -75,8 +87,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.27
-signing_key:
+rubygems_version: 4.0.6
 specification_version: 4
 summary: kana,hira,kanji formatter
 test_files: []

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## 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.
-
-## 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
-
-Examples of unacceptable behavior by participants include:
-
-* 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
-  professional setting
-
-## Our 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.
-
-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.
-
-## 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.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at ah.gm3622@gmail.com. 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.
-
-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.
-
-## 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]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/