Repository navigation
release: 0.1.0 - #33
Merged
Merged
Conversation
Bump FastRspec::VERSION to 0.1.0 and move the Unreleased changelog entries into a dated 0.1.0 section (gem packaging fix, Ruby 3.2 native extension compile fix, docs reframed as target contracts). Dz-Task-Id: tsk_9bb8d4ad292bdce1c1a5ab39f56a10a0
Contributor
Author
✅ Reviewed — nothing blocking0 actionable comment(s) · grounded on your code 🤖 developerz.ai — automated review, running on your model and your box. |
Contributor
Author
There was a problem hiding this comment.
Review summary — 2 file(s), 0 finding(s).
Bumps FastRspec::VERSION from 0.0.1 to 0.1.0 and moves the Unreleased changelog entries into a dated 0.1.0 section. Low risk: the version string and the changelog match the description, and CI, including the package build and smoke run, passed.
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bump FastRspec::VERSION to 0.1.0 and move the Unreleased changelog
entries into a dated 0.1.0 section (gem packaging fix, Ruby 3.2 native
extension compile fix, docs reframed as target contracts).
Acceptance
Changes
apps/fast-rspec/lib/fast_rspec/version.rb(edit) — Bump FastRspec::VERSION from '0.0.1' to '0.1.0' (line 4). Nothing else in the file changes; the gemspec reads this constant at build time (fast_rspec.gemspec:7).CHANGELOG.md(edit) — Cut the 0.1.0 section. Move the existing '## [Unreleased]' bullet (project skeleton description) into a new '## [0.1.0] - 2026-11-12' section and leave '## [Unreleased]' empty above it. Inside the 0.1.0 section add a '### Changed' subsection with exactly one line per shipping commit in the window: (1) b8184fe — drop README.md and CHANGELOG.md from the packaged gem files (they remain repo-root docs); (2) d5ad9f3 — fix Ruby 3.2 compilation of the native C extension by including <stdbool.h> before <ruby.h>; (3) b132352 — reframe README.md, llms.txt and the gemspec summary/description as design‑‑‑Verification
./bin/checkpassed (exit 0) in 37s.What the editors ran to see the change working, and what they saw:
bin/rake smoke(release): EXIT=0; 'fast_rspec 0.1.0 built to pkg/fast_rspec-0.1.0.gem.' and 'smoke ok: fast_rspec 0.1.0 (native)' — the bumped VERSION constant flows through the gemspec into the built gem and the gem requires cleanly in a temporary GEM_HOME without Rails.🤖 Opened by developerz.ai, an automated agent, not a human, on developerz-ai/fast_rspec.
Raised automatically by a developerz.ai maintainer lane.