Skip to content

1.38.2 — an extension on this decade's engine

Latest

Choose a tag to compare

@github-actions github-actions released this 30 Aug 11:38
· 1 commit to main since this release

Fixed

  • The Raycast extension was running an engine seven releases old. It
    declared ^1.31.0, and the score arrived in the engine at 1.34.0 — so the
    extension carried score UI the engine it depended on could never populate.
    Because the extension shares its library folder with the app and the command
    line, that showed up as an inconsistency rather than an absence: in Recent
    Reports
    a run crawled by the app had a score and a run crawled by the
    extension did not, in the same list.

    Now ^1.38.1, which also brings the site-wide cause collapse and the plural
    fixes. The lockfile had been held still while the Store submission was in
    review; that submission is a pull request in another repository and is not
    affected by this.

  • The Windows update dialog did not say to close the app first. It said
    running the new installer over this one was the whole update, which is true
    only once this one is closed: the installer offers to remove the old version
    before writing the new one, and an uninstaller cannot delete files that are
    open. It stops with "Unable to uninstall!".

    Reported by somebody updating 1.38.0, who had pressed Download in that
    very dialog and so still had the app running when the installer ran. The
    dialog had walked them into it.

  • The winget job failed a release it had no business failing.
    winget-releaser only ever updates a package: with nothing yet in
    microsoft/winget-pkgs it exits 1 with "Package Nurkamol.SeoAudit does not
    exist", which turned an otherwise-finished 1.38.1 red for a step that
    structurally could not succeed. It now asks that repository whether the
    package is there and warns instead — precisely, rather than with
    continue-on-error, so a real failure still fails once the package exists.

    The first version has to be submitted by hand, once. desktop/README.md has
    the komac command; a test checks that the section the warning names actually
    exists, because a pointer to a missing heading reads as an answer and ends
    the search.


Installing on macOS

brew tap nurkamol/seo-audit https://github.com/nurkamol/seo-audit
brew trust nurkamol/seo-audit
brew install --cask seo-audit

Homebrew verifies the download against the checksum below and clears the
quarantine flag for you, so the app opens the first time.

Downloading the zip instead? macOS may say "SEO Audit is damaged and
can't be opened."
It is not damaged. The app is ad-hoc signed rather than
notarised — notarising needs a paid Apple Developer account this project
does not have — and macOS refuses quarantined apps without a notarisation
ticket. Check what you downloaded first:

shasum -a 256 seo-audit-1.38.2-macos.zip
# 38e1565799a90243f94e61aef573f38b18c604c0ed4b855d5ffd0e9339bed009

Then, once it matches, clear the flag — no sudo needed:

xattr -dr com.apple.quarantine "/Applications/SEO Audit.app"

That is what right-click → Open does in the Finder, without the dialog.
Apple Silicon, macOS Tahoe or newer.

Windows and Linux

The setup.exe, .deb and .AppImage below are attached by a separate
job and may appear a few minutes after this release does.

The Windows installer is unsigned, so SmartScreen shows "Windows protected
your PC"
More info → Run anyway. Same reason as macOS: a code-signing
certificate is a paid, per-year thing this project does not have. The
.AppImage needs chmod +x before it will run.

Check any of them first. A SHA256SUMS.txt covering every file here is
attached alongside them, and the same checksums are listed at the end of
these notes:

shasum -a 256 --ignore-missing -c SHA256SUMS.txt

Checksums

Verify a download before you wave a warning away. With SHA256SUMS.txt
saved beside the file, in the same folder:

shasum -a 256 --ignore-missing -c SHA256SUMS.txt
7b02a22642af74cbfee6684323b75f1956461c5dbb534ccbedefdec76e13c2ac  SEO.Audit_1.38.2_amd64.AppImage
fdf68e5a65c8211f73bf73967d08613c21dba896855fd902980eff4719fe59e6  SEO.Audit_1.38.2_amd64.deb
106fc06001f780377d6e124646eec993cb0fb91a2aee9dfea757a60594283974  SEO.Audit_1.38.2_x64-setup.exe
38e1565799a90243f94e61aef573f38b18c604c0ed4b855d5ffd0e9339bed009  seo-audit-1.38.2-macos.zip

The macOS line appears twice in these notes on purpose: once above, computed
when the app was built, and once here, computed from what is actually attached.
They should agree.