fix: configure release-please correctly to unblock release pipeline #63
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
DaMandal0rian
approved these changes
Nov 20, 2025
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
Fixes the broken release pipeline by aligning the configuration with
release-please-actiondefaults and removing the Python version dependency.Changes
.release-please-config.json->release-please-config.json.pythontosimple.pythontype requires aversionfield inpyproject.tomlorsetup.py, which we do not use (we are a Docker-based deployment). Thesimpletype relies solely on the manifest file, which correctly matches our workflow.Impact
This will trigger the pending release (v0.4.2) that should have been created after recent fixes were merged.