Improve build resilience for self-hosted APIs (continue-on-error)

[thotganesh]

Hi Bryan,

First of all, thanks for this great project!

I'm using it on a self-hosted VM (Proxmox/Docker) behind a Cloudflare Tunnel. I noticed that the GitHub Actions build often fails prematurely if the status webhook returns a minor error (like 422 or 400 due to proxy filtering).

To fix this, I modified the workflows in my fork by adding continue-on-error: true to every fjogeleit/http-request-action step. This ensures the build process completes even if a status notification fails.

I also fixed an issue with the GENURL secret to ensure proper communication with the local API.

If you are interested, I can submit a Pull Request to integrate these resilience improvements into the main repository!

Best regards,

[bryangerlach]

Please submit a PR and I will review it. I am currently thinking of a better way to implement some things because there are a lot of failures since my server is overloaded at the moment.

[thotganesh]

Done! I've submitted the PR as requested: #218

This should make the build process much more resilient to the current server overloads. Thanks again for the help!

[thotganesh]

Update: The issue with the x86_64-unknown-linux-gnu target has been fixed. By updating the build environment and fixing the file paths, the generation process is now fully operational. Everything is ready on my end.