ci: fixed github pages deployment

[marc-romu]

No description provided.

[github-actions]

🏷️ This PR has been automatically assigned to milestone 1.4.1-alpha based on the version in Solution.props.

[Copilot]

Pull request overview

This PR updates the GitHub Pages generation workflow and release artifacts to fix where provider-hash manifest files are published for SmartHopper’s public hash verification and web UI.

Changes:

• Add a new provider hash manifest for 1.4.1-alpha.
• Update the composite Pages-generation action to emit versions.json under hashes/ and adjust latest.json handling.
• Document the GitHub Pages manifest-path fix in the changelog.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
.github/actions/generate-github-pages/action.yml	Adjusts where versions.json is written (and changes logic for creating/removing latest.json).
hashes/1.4.1-alpha.json	Adds the new version’s provider SHA-256 manifest and metadata.
CHANGELOG.md	Notes the intended Pages deployment fix for manifest locations.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The new logic skips generating hashes/latest.json when the newest available version is a prerelease. In this repo’s current state (hashes/ contains only 1.4.0-alpha.json and 1.4.1-alpha.json), that means latest.json will not be published at all, so clients falling back to .../hashes/latest.json (e.g., ProviderHashVerifier) will still hit 404. Consider always generating latest.json (using the latest stable when present, otherwise the latest prerelease), or publish a separate latest-stable.json if you want stable-only semantics.

Suggested change

	# Copy latest version to latest.json only if it's a stable release
	if ($latestVersion.IsStable) {
	$latestHashPath = Join-Path $hashesDir "latest.json"
	Copy-Item $latestVersion.File.FullName -Destination $latestHashPath -Force
	Write-Host " ✓ Created hashes/latest.json from stable version $($latestVersion.Version)"
	} else {
	Write-Host " ⚠ Skipped latest.json - latest version $($latestVersion.Version) is a prerelease, not stable"
	# Remove existing latest.json if it exists (to avoid stale latest pointing to old stable)
	$existingLatest = Join-Path $hashesDir "latest.json"
	if (Test-Path $existingLatest) {
	Remove-Item $existingLatest -Force
	Write-Host " ✓ Removed stale hashes/latest.json"
	}
	}
	# Always copy selected latest version (stable preferred, otherwise prerelease) to latest.json
	$latestHashPath = Join-Path $hashesDir "latest.json"
	Copy-Item $latestVersion.File.FullName -Destination $latestHashPath -Force
	if ($latestVersion.IsStable) {
	Write-Host " ✓ Created hashes/latest.json from stable version $($latestVersion.Version)"
	} else {
	Write-Host " ✓ Created hashes/latest.json from prerelease version $($latestVersion.Version)"
	}
	# Additionally, publish latest-stable.json if a stable version exists
	if ($stableVersions.Count -gt 0) {
	$latestStable = $stableVersions[0]
	$latestStablePath = Join-Path $hashesDir "latest-stable.json"
	Copy-Item $latestStable.File.FullName -Destination $latestStablePath -Force
	Write-Host " ✓ Created hashes/latest-stable.json from stable version $($latestStable.Version)"
	}

[Copilot]

This changelog entry claims GitHub Pages now places latest.json under hashes/, but the updated action currently skips generating hashes/latest.json when there are no stable versions. Since the repository’s hashes/ folder currently only contains prereleases (alpha), latest.json would still be missing and the described 404 fix wouldn’t hold. Please align the changelog with the actual behavior, or adjust the action to always publish hashes/latest.json (possibly pointing at the latest prerelease when no stable exists).