Replace RDoc gem dependency with YARD in aethyr.gemspec #93

New issue

Open

opened 2026-03-15 04:13:09 +00:00 by freemo · 0 comments

freemo commented

2026-03-15 04:13:09 +00:00

Owner

Metadata

Commit Message: chore(deps): replace rdoc with yard gem
Branch: feature/m1-yard-migration

Background and Context

The gemspec currently declares rdoc ~> 4.2 as a development dependency. This must
be replaced with the yard gem to match the specification.

Expected Behavior

aethyr.gemspec lists yard instead of rdoc as a development dependency
bundle install resolves successfully

Acceptance Criteria

rdoc removed from gemspec dependencies
yard added as development dependency
bundle install succeeds

Subtasks

Update gemspec to replace rdoc with yard
Run bundle install to verify resolution
Verify no remaining rdoc requires in gemspec

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the
Commit Message in Metadata exactly.
The commit is pushed to the remote on the branch matching the Branch in Metadata.
The commit is submitted as a pull request to master, reviewed, and merged.

## Metadata - **Commit Message**: `chore(deps): replace rdoc with yard gem` - **Branch**: `feature/m1-yard-migration` ## Background and Context The gemspec currently declares `rdoc ~> 4.2` as a development dependency. This must be replaced with the `yard` gem to match the specification. ## Expected Behavior - `aethyr.gemspec` lists `yard` instead of `rdoc` as a development dependency - `bundle install` resolves successfully ## Acceptance Criteria - `rdoc` removed from gemspec dependencies - `yard` added as development dependency - `bundle install` succeeds ## Subtasks - [ ] Update gemspec to replace rdoc with yard - [ ] Run `bundle install` to verify resolution - [ ] Verify no remaining rdoc requires in gemspec ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged**.