chore: release v4.0.3 #155
Open
Conversation
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
There was a problem hiding this comment.
Pull request overview
This is an automated release PR generated by release-please to publish version 5.0.0 of the ProcessExecuter gem. This is a major version release containing numerous breaking changes, new features, and bug fixes that have accumulated since v4.0.2.
- Version bumped from 4.0.2 to 5.0.0 with extensive breaking changes to the API
- Added comprehensive CHANGELOG entry documenting all features, bug fixes, and breaking changes
- Updated release manifest to track the new version
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| lib/process_executer/version.rb | Updates the VERSION constant from '4.0.2' to '5.0.0' |
| CHANGELOG.md | Adds complete v5.0.0 release notes including breaking changes, features, bug fixes, and other changes |
| .release-please-manifest.json | Updates the version tracking from "4.0.2" to "5.0.0" |
CHANGELOG.md
Outdated
| * ProcessExecuter.spawn_and_wait_with_options | ||
| * ProcessExecuter::SpawnAndWaitOptions | ||
| * In places where users of this gem rescued ::ArgumentError, they will have to change the rescued class to ProcessExecuter::ArgumentError. | ||
| * to maintain the same behavior, client code will have to change how they call `ProcessExecuter.run` if they do not specify `out:` and |
There was a problem hiding this comment.
The breaking change description appears to be incomplete. The sentence ends with "if they do not specify out: and" without finishing the thought. This should be completed to clearly communicate what users need to do.
Suggested change
| * to maintain the same behavior, client code will have to change how they call `ProcessExecuter.run` if they do not specify `out:` and | |
| * to maintain the same behavior, client code will have to change how they call `ProcessExecuter.run` if they do not specify `out:` and previously relied on the default capturing of stdout and stderr; they must now either pass an explicit `out:` destination or switch to `run_with_capture`. |
jcouball
force-pushed
the
release-please--branches--main--components--process_executer
branch
from
e54c433 to
a78ad3c
Compare
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.
🤖 I have created a release beep boop
4.0.3 (2026-01-04)
Other Changes
This PR was generated with Release Please. See documentation.