Add workflow for releasing gem

[tsuzuki-takaaki]

What

• Add GitHub Actions workflow for releasing gem to RubyGems.org
  • Use https://github.com/rubygems/release-gem

Why

• We always execute the release command locally

Refs

• Add release-gem.yml and bump up version to v1.1.0 graphql-kaminari_connection#36
• Already setup RubyGems Trusted Publishing
  • https://github.com/increments/qiita-dev/issues/7383#issuecomment-2975145721
• Already setup release environment
  • https://github.com/increments/qiita-dev/issues/7383#issuecomment-2975362104

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[Copilot]

Pull Request Overview

Adds a new GitHub Actions workflow to automate gem releases to RubyGems.org.

• Introduces a manual workflow_dispatch trigger for releases
• Checks out code, sets up Ruby 3.4.4 with bundler cache, and runs rubygems/release-gem
• Configures necessary permissions and environment

Comments suppressed due to low confidence (2)

.github/workflows/release.yml:17

• Add with: fetch-depth: 0 to the actions/checkout step to ensure the full Git history (including tags) is fetched, which is required for release-gem to detect and manage version tags correctly.

- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2

.github/workflows/release.yml:17

• [nitpick] Consider pinning to a stable version tag (e.g., actions/checkout@v4) instead of a full commit SHA for better readability and simpler updates.

- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2

[kimkim0814]

nits 以外は良さそうです

LGTM!