fix: configure release-please workflow to use config files #53
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
The GitHub Actions workflow was explicitly passing release-type and package-name parameters, which caused release-please to ignore .release-please-config.json. This prevented the extra-files configuration from being processed, so Docker image versions in docker-compose.yml and k8s/deployment.yaml were not being automatically updated during releases. Changes: - Remove explicit parameters from release-please action to enable config file discovery - Update k8s/deployment.yaml from v0.4.0 to v0.4.1 with x-release-please-version marker - This allows release-please to automatically update both deployment files in future releases Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
RembrandtK
approved these changes
Nov 10, 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 release-please configuration issue misconfiguration in PR #49 that lead to automated release-please PR #52 which didnt bump the version number in the docker-compose.yml or kubernetes files. The GitHub Actions workflow was explicitly passing
release-typeandpackage-nameparameters, which caused release-please to completely ignore.release-please-config.json. This prevented theextra-filesconfiguration from working, so Docker image versions were never automatically updated.