Description
The prepare-release.yml workflow passes FILE_PATHS as space-separated values to vig-os/commit-action@v0.2.0, but the action splits on commas. The entire space-separated string is treated as a single non-existent path, silently skipped, and both commit steps succeed with "No files to commit" instead of creating the expected commits.
The prepare-release workflow is designed to:
- Freeze the CHANGELOG on
dev (Unreleased → [X.Y.Z] - TBD + fresh empty Unreleased), commit to dev
- Create the release branch from
dev (post-freeze)
- Strip the empty Unreleased section from the release branch, commit to
release/X.Y.Z
All commits use commit-action to bypass branch protection rulesets via GitHub App token.
Because both commit steps silently no-op, the release branch is created from the unfrozen dev SHA, and neither branch receives the expected changelog modifications.
Steps to Reproduce
- Trigger the "Prepare Release" workflow with version
0.3.2
- Both "Commit prepared CHANGELOG to dev via API" and "Commit stripped CHANGELOG to release branch via API" log "No files to commit"
- Workflow reports success despite no commits being created
Evidence: Run #23899040367, job Prepare Release Branch
Expected Behavior
commit-action should commit both CHANGELOG.md and assets/workspace/.devcontainer/CHANGELOG.md to the target branches with the frozen/stripped content.
Actual Behavior
commit-action receives FILE_PATHS="CHANGELOG.md assets/workspace/.devcontainer/CHANGELOG.md", splits on ,, gets a single path "CHANGELOG.md assets/workspace/.devcontainer/CHANGELOG.md" which doesn't exist, silently skips it, and returns "No files to commit" with exit code 0.
Environment
- GitHub Actions,
ubuntu-22.04 runner
vig-os/commit-action@1bc004353d08d9332a0cb54920b148256220c8e0 (v0.2.0)
- Workflow:
.github/workflows/prepare-release.yml
Possible Solution
Change both FILE_PATHS values in prepare-release.yml from space-separated to comma-separated:
# Before
FILE_PATHS: CHANGELOG.md assets/workspace/.devcontainer/CHANGELOG.md
# After
FILE_PATHS: CHANGELOG.md,assets/workspace/.devcontainer/CHANGELOG.md
Changelog Category
Fixed
Acceptance Criteria
Description
The
prepare-release.ymlworkflow passesFILE_PATHSas space-separated values tovig-os/commit-action@v0.2.0, but the action splits on commas. The entire space-separated string is treated as a single non-existent path, silently skipped, and both commit steps succeed with "No files to commit" instead of creating the expected commits.The prepare-release workflow is designed to:
dev(Unreleased →[X.Y.Z] - TBD+ fresh empty Unreleased), commit todevdev(post-freeze)release/X.Y.ZAll commits use
commit-actionto bypass branch protection rulesets via GitHub App token.Because both commit steps silently no-op, the release branch is created from the unfrozen
devSHA, and neither branch receives the expected changelog modifications.Steps to Reproduce
0.3.2Evidence: Run #23899040367, job Prepare Release Branch
Expected Behavior
commit-actionshould commit bothCHANGELOG.mdandassets/workspace/.devcontainer/CHANGELOG.mdto the target branches with the frozen/stripped content.Actual Behavior
commit-actionreceivesFILE_PATHS="CHANGELOG.md assets/workspace/.devcontainer/CHANGELOG.md", splits on,, gets a single path"CHANGELOG.md assets/workspace/.devcontainer/CHANGELOG.md"which doesn't exist, silently skips it, and returns "No files to commit" with exit code 0.Environment
ubuntu-22.04runnervig-os/commit-action@1bc004353d08d9332a0cb54920b148256220c8e0(v0.2.0).github/workflows/prepare-release.ymlPossible Solution
Change both
FILE_PATHSvalues inprepare-release.ymlfrom space-separated to comma-separated:Changelog Category
Fixed
Acceptance Criteria
.cursor/rules/tdd.mdc)