27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
# ForgeFlow 0.4.1 release notes
|
|
|
|
## Windows Bash path fix
|
|
|
|
ForgeFlow 0.4.1 fixes the source quality gate on Windows when the project is stored at a path such as `C:\Projects\ForgeFlow`.
|
|
|
|
The previous verifier passed an absolute Windows path directly to `bash -n`. Bash interpreted the backslashes as escape characters, producing a collapsed path such as `C:ProjectsForgeFlow...` and a false validation failure.
|
|
|
|
The verifier now starts Bash with the ForgeFlow project root as its working directory and passes the deployment example as a relative POSIX path:
|
|
|
|
```text
|
|
examples/server/forgeflow-deploy
|
|
```
|
|
|
|
This keeps the project root separate from the script argument and works across Windows Git Bash, Linux and macOS.
|
|
|
|
## Regression coverage
|
|
|
|
New automated coverage verifies that:
|
|
|
|
- a Windows project root remains in `cwd`;
|
|
- no drive letter or backslash is passed as the Bash script argument;
|
|
- absolute and escaping script paths are rejected;
|
|
- Bash validation succeeds from a project root containing spaces.
|
|
|
|
No Gitea token, repository mapping, SSH credential, deployment profile or diagnostic history is changed by this update.
|