Railstart 0.5.0 - #34
Merged
Merged
Conversation
dpaluy
marked this pull request as ready for review
July 11, 2026 18:28
dpaluy
force-pushed
the
agent/ruby-4-railstart-hardening
branch
from
July 11, 2026 18:29
b240660 to
ffa3bfd
Compare
dpaluy
force-pushed
the
agent/ruby-4-railstart-hardening
branch
from
July 11, 2026 18:30
ffa3bfd to
40f6911
Compare
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.
Summary
nonechoice and API-only preset to emit--skip-cssrails newwith an argument vector instead of a shell-interpreted command stringrailstart initgenerate minimal overrides instead of freezing the full shipped schemaWhy
The API-only preset generated
--css=none, which Rails rejects. Existing unit coverage used a hand-built fixture and did not exercise the shipped YAML. The generator also passed user-influenced values through a shell command string, and configuration validation allowed malformed values to fail late.The previous CI workflow ran only the default test task, so it missed RuboCop failures, documentation dependency problems, packaging warnings, and invalid shipped preset commands.
Ruby compatibility
The gem continues to support Ruby 3.2 and newer. RuboCop continues to target Ruby 3.2 syntax.
Development and release use exact Ruby 4.0.5. CI retains the existing Ruby 3.4 and 4.0 entries and adds exact Ruby 4.0.5 coverage.
Dependency updates
This release incorporates the open gem update PRs:
The separate
actions/checkoutv5 to v7 major update remains out of scope.Closes #25
Closes #26
Closes #29
Closes #33
Impact
Existing user configuration remains layered by ID. New
railstart initoutput is deliberately minimal so later built-in choices and flags continue to flow through upgrades.The changelog, version constant, and lockfile are synchronized to 0.5.0.
Validation
bundle exec rake test: 67 runs, 197 assertions, 0 failures, 0 errors, 1 intentional opt-in skipbundle exec rubocop: 23 files inspected, no offensesRAILS_CONTRACT=1 bundle exec ruby -Itest test/rails_cli_contract_test.rb: 1 run, 4 assertions, 0 failuresbundle exec rake yard: successful with warnings treated as failuresruby -c exe/railstart: syntax OKbundle exec exe/railstart version: Railstart v0.5.0gem build railstart.gemspec: successfully builtrailstart-0.5.0.gemwithout file-permission warnings