Hello, what is the supported official way to obtain verifiable frontend build inputs for v0.70.0 when certificate-verified npm access fails?
On Windows with Node v22.23.2, a certificate-verified HTTPS HEAD to https://registry.npmjs.org/pnpm returns EPROTO with TLS alert 40 (handshake_failure). Certificate verification and network/security settings have not been changed.
The v0.70.0 release assets include portable/installer/CLI binaries and source archives, but no standalone apps/desktop-tauri/dist archive. I am assessing an unchanged frontend for a downstream Rust desktop build, pinned to commit f0b45ed422513eaf3e58ef0e321e1b02424547be and its unchanged pnpm lockfile.
If a matching frontend archive or offline dependency bundle is already available, an official URL, checksum and supported build procedure would answer this. Otherwise, please point to the recommended official acquisition/build procedure that preserves the lockfile and integrity verification. I am not seeking private caches, signing access, TLS disabling or an unofficial mirror. This approach has not been tested.
Thank you.
Hello, what is the supported official way to obtain verifiable frontend build inputs for v0.70.0 when certificate-verified npm access fails?
On Windows with Node v22.23.2, a certificate-verified HTTPS HEAD to
https://registry.npmjs.org/pnpmreturnsEPROTOwith TLS alert 40 (handshake_failure). Certificate verification and network/security settings have not been changed.The v0.70.0 release assets include portable/installer/CLI binaries and source archives, but no standalone
apps/desktop-tauri/distarchive. I am assessing an unchanged frontend for a downstream Rust desktop build, pinned to commitf0b45ed422513eaf3e58ef0e321e1b02424547beand its unchanged pnpm lockfile.If a matching frontend archive or offline dependency bundle is already available, an official URL, checksum and supported build procedure would answer this. Otherwise, please point to the recommended official acquisition/build procedure that preserves the lockfile and integrity verification. I am not seeking private caches, signing access, TLS disabling or an unofficial mirror. This approach has not been tested.
Thank you.