jDeploy 5.5.3 Release Notes

Fixed an issue where release notes weren’t displayed correctly when publishing the first release in a repository.

Problem: On the first release in a repository, all artifacts were uploaded correctly to GitHub, but the release notes weren’t displayed. This was likely related to failures in fetching the package-info file during initial setup.

Solution: The release process now properly handles first-time releases, ensuring release notes are correctly attached and displayed even when the package-info file is being created for the first time.

Reference: Issue #332

Fixed a critical issue that broke Windows installer builds in GitHub Actions workflows.

Problem: When using jDeploy 5.4.3 in GitHub Actions, Windows builds failed with the error:

This affected projects that had been working correctly with jDeploy 5.2.1.

Solution: Fixed the path handling in the GitHub Actions workflow to correctly resolve script paths on Windows runners, ensuring cross-platform compatibility.

Reference: Issue #320

Fixed a regression where builds failed if a project didn’t provide a custom icon.

Problem: The zip file generator would fail with an error when the application didn’t have a custom icon.png file:

Solution: jDeploy now correctly falls back to the default icon (./cli/src/main/resources/ca/weblite/jdeploy/icon.png) when no custom icon is provided, eliminating this class of build failure.

Reference: Issue #329

Enhanced validation and error messages when creating new projects with GitHub repositories in the jDeploy Desktop GUI.

Problem: When creating a new project, the GitHub project name needed to be in the form {owner}/{repo}, but the form didn’t provide clear hints. Entering a full GitHub URL or just {repo} resulted in unhelpful error messages (IO errors and string out of bounds errors).

Solution: * Added clear hints on the form indicating the required format * Improved validation to catch incorrect formats before submission * Enhanced error messages to guide users toward the correct format

Reference: Issue #55

Fixed handling of minLauncherInitialAppVersion in branch releases.

Problem: Branch releases weren’t properly handling the launcher update feature properties, which could cause unexpected behavior.

Solution: Branch releases now completely ignore minLauncherInitialAppVersion and related launcher update properties. This provides clear, predictable behavior for branch releases. The launcher update feature may be revisited for branch releases in a future version.

jDeploy 5.5.3 is backward compatible with 5.5.0 and later versions. No changes are required for existing applications.

Projects that experienced issues with: * First-time releases * Windows builds in GitHub Actions * Missing custom icons * GitHub project creation

…​will benefit immediately from these bug fixes without any configuration changes.