Fix release-please workflow configuration #36
Conversation
This change restores .release-please-manifest.json and release-please-config.json to properly support the 'extra-files' configuration (updating version.txt) which is not supported as a direct input in the release-please-action@v4 workflow YAML. It also updates the workflow file to remove the invalid inputs.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
|
Review changes with Changed Files
|
This change reverts the .github/workflows/release-please.yml to the state requested by the user, which explicitly uses `config-file` and `manifest-file` inputs. It also restores the required .release-please-manifest.json and release-please-config.json files to support the `extra-files` configuration (updating version.txt) that was causing issues when passed as a direct workflow input.
1 participant
Fixed the release-please workflow by reverting to a manifest-based configuration. The
extra-filesinput caused the workflow to fail as it is not supported in thewithblock of the action. Restored.release-please-manifest.jsonandrelease-please-config.jsonto handle versioning and file updates correctly.PR created automatically by Jules for task 11253249376066659490 started by @azman0101