Repository navigation
Refresh the public package baselines to v0.2.2 - #166
Merged
Merged
Conversation
After v0.2.2 became the latest release, the current-public package checks
refused to run ("Public latest advanced; generate authentic exports before
refreshing the Windows fixture"), failing on every pull request.
windows-package-v022 holds two profile exports made by the unmodified
public v0.2.2 core (95058a7), built with the v0.2.1 harness relabelled for
the new tag. All 326 extracted source files match the tag's blobs, all 122
registry dependencies match its lockfile, and both manifests equal the
v0.2.1 ones apart from the profile name. development-package-v022.json pins
the signed v0.2.2 AppImage and Debian package; every downloaded artifact
matched GitHub's digest and passed its updater signature. The scripts,
workflow triggers and tests now point at the new baseline.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What broke
Once v0.2.2 became the latest release, the current-public package checks refused to run on every pull request:
They test the newest public installers against profile exports made by that same release, and the retained exports came from v0.2.1.
What changed
scripts/fixtures/windows-package-v022/: two new exports (no-hud,single-hud) made by the unmodified public v0.2.2 core at95058a75, using the v0.2.1 harness with only its revision and labels changed. All 326 extracted source files match the tag's blobs and all 122 registry dependencies match itsCargo.lock. Both exported manifests equal the v0.2.1 ones apart from the profile name; the eight payloads are byte-for-byte the same.scripts/fixtures/development-package-v022.json: pins the signed v0.2.2 AppImage and Debian package. Every downloaded artifact matched GitHub's recorded digest, and all three installers passedverifyPublicPackageagainst the product's updater key. The release'srelease-commit.jsonnames the same commit (run 36946290396).windows-package-v021stays: it is the source of the release-upgrade fixture until the next release refreshes it.Checks
node --testfor the development package fixture and guard, the Windows package contract, package smoke, Linux native smoke, docs-only and release guards: 112 pass. The 7 Windows PowerShell 7 tests can't run on this machine (nopwsh); they fail identically on unchangedmainhere and run in CI.biome check .