Upload release assets

I need to upload the Linux and Windows build artifacts for v2.1.0. Attach the two binaries and the checksum file to the release page for analytics, mark each asset with its checksum in the release description, and tell Ops and QA once the upload completes so they can validate downloads before the Friday deploy window.

Before I upload release assets, verify file sizes and checksums, surface any executables that contain debug symbols or excessive size, and confirm we have valid licenses for bundled libraries. Create an upload checklist that includes naming conventions and SHA256 entries so support can reproduce artifact verification easily.

I attempted to attach the built Windows binary to the release and the web UI rejected it with a file size limit error. I don't know whether to use the repository's release assets or an external host. Explain the likely size limit, outline the options (split, compress, external storage) with exact commands, and give a clear message I can send to Ops explaining the chosen approach and any extra validation steps.

Uploading assets keeps sucking time because files exceed size limits or downloads fail after publishing. Where am I losing reliability? Recommend a single repeatable strategy for hosting and naming release assets, the verification steps to run after upload, and a short team convention to avoid last-minute hosting changes before release day.