Skip to content

chore: release v4.1.0 - #197

Merged
jcouball merged 1 commit into
mainfrom
release-please--branches--main--components--process_executer
Aug 31, 2026
Merged

jcouball merged 1 commit into
mainfrom
release-please--branches--main--components--process_executer

Conversation

@jcouball

@jcouball jcouball commented Aug 30, 2026

Copy link
Copy Markdown
Member

🤖 I have created a release beep boop

4.1.0 (2026-08-31)

Other Changes

  • Characterize validation ordering when unknown and invalid options are given together (#192) (15d6e06)
  • Collapse encoding validators and clarify capture-redirection assembly (#194) (bab8610)
  • Contribute subclass redirections via an internal_redirections hook (#190) (8ecbda5)
  • Derive the process-group isolation decision from a single source (#191) (5d8ac7d)
  • Describe every source of MonitoredPipe#exception (#193) (333b7bd)
  • Extract shared validate! from Options::Base#initialize and #merge! (#192) (422956a)
  • Track opened pipes as per-call instance state instead of an out-parameter (#190) (f279f1e)

This PR was generated with Release Please. See documentation.

Copilot AI lite review requested due to automatic review settings August 30, 2026 23:59

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The changelog update introduces a duplicate 4.1.0 section with an incorrect compare link (v4.1.0...v4.1.0), which should be corrected before release.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR is a Release Please–generated release chore for v4.1.0, intended to update the project changelog to reflect the release contents.

Changes:

  • Adds a new 4.1.0 entry to CHANGELOG.md describing issue #190–related internal refactors.
File summaries
File Description
CHANGELOG.md Adds a new v4.1.0 changelog section (currently duplicating an existing v4.1.0 entry and using a self-compare link).
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread CHANGELOG.md Outdated
Comment on lines +8 to +15
## [4.1.0](https://github.com/main-branch/process_executer/compare/v4.1.0...v4.1.0) (2026-08-30)


### Other Changes

* Contribute subclass redirections via an internal_redirections hook ([#190](https://github.com/main-branch/process_executer/issues/190)) ([8ecbda5](https://github.com/main-branch/process_executer/commit/8ecbda54874de933ab07a64d91e0a07e17f7ece0))
* Track opened pipes as per-call instance state instead of an out-parameter ([#190](https://github.com/main-branch/process_executer/issues/190)) ([f279f1e](https://github.com/main-branch/process_executer/commit/f279f1e0672b91b966ee73cbadf00749522e488d))

@jcouball
jcouball force-pushed the release-please--branches--main--components--process_executer branch 3 times, most recently from 94e9bdb to 31e6d6c Compare August 31, 2026 20:33
@jcouball
jcouball force-pushed the release-please--branches--main--components--process_executer branch from 31e6d6c to 515801f Compare August 31, 2026 22:45
@jcouball
jcouball merged commit f6bc1e6 into main Aug 31, 2026
2 checks passed
@jcouball
jcouball deleted the release-please--branches--main--components--process_executer branch August 31, 2026 22:52
jcouball added a commit that referenced this pull request Aug 31, 2026
…onfig

The override was added in #195 to force the hardening release to 4.1.0
instead of 4.0.5, but release-as is a standing instruction, not a
one-shot: left in place after #163 released 4.1.0, it made release-please
propose v4.1.0 again for every subsequent release PR (#197), which
collided with the existing v4.1.0 tag when merged.

With the override removed, release-please computes the next version from
conventional commits again. A future forced version should use a
Release-As footer on an empty commit instead, which applies to a single
release and leaves nothing behind.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants