Repository navigation
Default install-whitaker to whitaker-installer 0.2.10 #644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,7 +12,7 @@ inputs: | |
| action pins, and must be 0.2.9 or later: that is the first release with | ||
| --no-source-fallback, which the action always passes. | ||
| required: false | ||
| default: "0.2.9" | ||
| default: "0.2.10" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ⚪ Low · Guides name the old default When a consumer consults the user guide to determine the default installer version, the action now defaults to 0.2.10, but the current user guide still says 0.2.9 is the default, so consumers consulting it are given the wrong version. Update the user-facing documentation to match. Update the current user guide's default-version references to 0.2.10 while keeping the 0.2.9 minimum-version floor unchanged. Also at Prompt for AI agentsIn `.github/actions/install-whitaker/action.yml` at line 15:
**Guides name the old default**
When a consumer consults the user guide to determine the default installer version, the action now defaults to 0.2.10, but the current user guide still says 0.2.9 is the default, so consumers consulting it are given the wrong version. Update the user-facing documentation to match.
Update the current user guide's default-version references to 0.2.10 while keeping the 0.2.9 minimum-version floor unchanged.
Also at `.github/actions/install-whitaker/README.md:86`.
coderabbitai[bot] marked this conversation as resolved.
Resolved
|
||
| installer-sha256: | ||
| description: >- | ||
| SHA-256 digest of the whitaker-installer release archive for this | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -31,7 +31,7 @@ | |
| "x86_64-pc-windows-msvc", | ||
| "x86_64-unknown-linux-gnu", | ||
| ) | ||
| _PINNED_VERSIONS = ("0.2.9",) | ||
| _PINNED_VERSIONS = ("0.2.9", "0.2.10") | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟠 High · Incorrect archive digests pass When a 0.2.10 manifest digest is replaced with a different 64-character hexadecimal value, Assert the expected digest values for the newly pinned 0.2.10 assets, or independently verify the hashes of those assets in a test. Prompt for AI agentsIn `.github/actions/install-whitaker/tests/test_install_whitaker.py` at line 34:
**Incorrect archive digests pass**
When a 0.2.10 manifest digest is replaced with a different 64-character hexadecimal value, `TestPinnedDigestManifest.test_pins_every_supported_version_and_target` checks only asset names and 64-character hexadecimal syntax, so an incorrect 0.2.10 digest still passes; the action then rejects the real archive and installation fails.
Assert the expected digest values for the newly pinned 0.2.10 assets, or independently verify the hashes of those assets in a test. |
||
|
|
||
|
|
||
| def _step_env(name: str) -> dict[str, str]: | ||
|
|
@@ -70,7 +70,7 @@ def _step_script(name: str) -> str: | |
| "always passes." | ||
| ), | ||
| "required": False, | ||
| "default": "0.2.9", | ||
| "default": "0.2.10", | ||
| }, | ||
| "installer-sha256": { | ||
| "description": ( | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,7 +12,7 @@ permissions: | |
| contents: read | ||
|
|
||
| env: | ||
| WHITAKER_TEST_INSTALLER_VERSION: 0.2.9 | ||
| WHITAKER_TEST_INSTALLER_VERSION: 0.2.10 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟠 High · Wrong installer version passes When the action mistakenly installs a different supported version, such as 0.2.9, the install workflow requests 0.2.10, but its verification checks only that an installer file is executable; Verify the installed binary's reported version or otherwise assert that the archive selected was the requested 0.2.10 asset. Prompt for AI agentsIn `.github/workflows/test-install-whitaker.yml` at line 15:
**Wrong installer version passes**
When the action mistakenly installs a different supported version, such as 0.2.9, the install workflow requests 0.2.10, but its verification checks only that an installer file is executable; `install-whitaker` therefore passes if it installs 0.2.9 instead, so the test does not establish that the real 0.2.10 archive works.
Verify the installed binary's reported version or otherwise assert that the archive selected was the requested 0.2.10 asset. |
||
|
|
||
| jobs: | ||
| install-whitaker: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Medium · CI keeps the old installer
When the Linux CI job restores a cached Whitaker checkout that causes 0.2.9’s
git pullto abort, the Linux CI workflow passesWHITAKER_INSTALLER_VERSION=0.2.9explicitly, overriding this default; its cached checkout is therefore still updated by the old installer’sgit pull, and CI continues to fail on stale cached checkouts.Update the CI version override to 0.2.10 or remove it so the workflow uses the new default.
Prompt for AI agents