feat: v0.4.0 - License change, bug fixes, and CI improvements #33
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "v0.4.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Major Changes:
Bug Fixes:
Development Improvements:
Pull Request Overview
This PR introduces version 0.4.0 with a significant license change from MIT to AGPL-3.0, along with critical bug fixes and CI/CD improvements. The changes enhance cross-platform compatibility and strengthen the project's copyleft licensing.
Reviewed Changes
Copilot reviewed 5 out of 473 changed files in this pull request and generated 3 comments.
Show a summary per file
The div function checks for zero division but returns 0 when b == 0. This could mask calculation errors in templates. Consider returning an error or a special value that indicates division by zero occurred.
The error from os.Stat is ignored when the file doesn't exist. Consider logging when template files are missing to aid debugging, especially since this function is designed to handle ARM64-specific template loading issues.
The ParseFiles result is ignored and only errors are logged. If parsing fails for some files but succeeds for others, the function continues silently. Consider tracking successful vs failed template parsing to ensure critical templates are loaded.
Pull Request Overview
This PR implements version 0.4.0 with a major license change from MIT to AGPL-3.0, along with bug fixes for ARM64 compatibility, SMTP validation, and currency display issues. It also introduces CI/CD improvements with separate workflows for testing PRs and publishing Docker images.
Reviewed Changes
Copilot reviewed 5 out of 473 changed files in this pull request and generated 2 comments.
Show a summary per file
@ -101,0 +144,4 @@"templates/smtp-message.html","templates/form-errors.html","templates/error.html",}Returning NaN for division by zero in a template function could cause unexpected behavior in HTML rendering. Consider returning 0 or an error value that's more predictable in template contexts.
The magic number '/2' for determining when too many templates have failed should be defined as a named constant for better maintainability and clarity.