Merged
Conversation
…rmat Build status: Success
…ty Build status: Success
…ld status: Success
…les and pp require
… use porcelain mode for proper change detection - Add git user config in commit_to_remote test helper - Update file content matcher to use regex for flexible matching - Add cucumber.yml for proper test configuration
…ec to support Ruby 2.7+ (drop Ruby 2.6) - Update CI to test Ruby 2.7, 3.0, 3.2, 3.3 (remove 2.6) - Improve README with better structure and clarity - Add 'Why Prodder?' section - Update requirements: Ruby 2.7+, PostgreSQL 15+ - Remove Rails from requirements (not a dependency) - Better organized workflow explanation - Improved installation and usage sections - Add badges for Ruby and PostgreSQL versions - Update PostgreSQL requirement to 15+ throughout docs
…he blog.git directory is gitignored but needed for Cucumber tests. Added step to extract it from blog.git.tgz archive before running tests.
…as failing because pg_dump version (16) didn't match PostgreSQL server version (17.7). Install postgresql-client-17 from the official PostgreSQL APT repository to fix the mismatch.
…ere failing because git wasn't configured with user.name and user.email, which are required for git commits. Added step to configure git globally in CI environment.
…itter environment variables in Cucumber Before hook so they're available for all test scenarios that create commits. This is the proper way to configure git for Aruba-based tests.
…other PostgreSQL client tools are in PATH during test execution to fix the lint test that checks for missing executables.
…xport to prepend PostgreSQL bin directory to PATH instead of trying to reference env.PATH in GitHub Actions env block, which was replacing the entire PATH and breaking git access.
…_dump generates a random \restrict token on every dump, causing all dump files to appear changed even when nothing actually changed. This broke tests that expected no commits when dumping unchanged schemas. Solution: Add --restrict-key=prodder flag to pg_dump commands to use a fixed key instead of random one, making dump output deterministic. This fixes all Cucumber test failures related to unexpected file changes.
74b36e4 to
be018d9
Compare
rnubel
approved these changes
Dec 10, 2025
kaisensan
approved these changes
Dec 10, 2025
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.
Overview
This comprehensive modernization upgrade brings Prodder up to date with current Ruby and PostgreSQL standards. The project now supports Ruby 2.7–3.3 and PostgreSQL 15–17, ensuring compatibility with modern Rails applications while maintaining backward compatibility where reasonable.
Key Changes
1. Ruby Version Support
2. PostgreSQL Modernization
3. Dependency Updates
4. Code Modernization
5. CI/CD Improvements
6. Documentation
Testing
Version Bump
Gem version bumped to 1.9.0 to reflect the significant modernization and version support changes.
Breaking Changes
Backward Compatibility