Skill Recorder v0.3.0
Warning
Windows users: Do not use the v0.3.0 Windows installation command. Its source installer can fail when nested dependency paths exceed legacy MAX_PATH, and cleanup can mask the underlying error. Install v0.3.1 instead. Existing successful v0.3.0 installations and the macOS/Ubuntu installers are unaffected.
Skill Recorder v0.3.0
This is a source-only release. No prebuilt application, installer, or
portable binary is attached. GitHub provides the tagged source archives, and
the commands below build the exact release commit locally.
Highlights
- The Windows source installer now saves a Skill Recorder (Source) shortcut
on your desktop, in addition to the existing Start Menu entry. It resolves
the real desktop folder, so OneDrive-redirected desktops work correctly. - The installer finishes with a confirmation that lists exactly where both
shortcuts were saved, so it is clear how to reopen the tool later. - Shortcut creation is no longer fatal. If Windows refuses to write a shortcut,
the installer reports a warning instead of discarding an installation that
already passed every integrity, license, and build check. - Set
SKILL_RECORDER_NO_DESKTOP_SHORTCUT=1to keep only the Start Menu entry.
The published one-line commands are unchanged. - No redundant downloads. Re-running the same commit already reused the
installed revision, and now says so plainly. An attempt that failed part-way
used to download everything again; the portable Node.js archive and the pinned
source archive are now kept in<install root>\cacheand reused on the next
attempt.
Cached files are re-verified by SHA-256 before use and discarded if they do
not match: the Node.js archive against the SHASUMS256.txt that nodejs.org
publishes, re-fetched on every run, and the source archive against a digest
recorded at download time, on top of the existing commit-directory and
required-path checks. Entries are deleted once the revision is installed, so the
cache only ever holds work from an interrupted attempt. Deleting it is always
safe.
Upgrade and compatibility notes
- Upgrading is optional. v0.2.1 installations keep working; re-run the command
below with this release's commit to pick up the desktop shortcut. - Existing shortcuts are refreshed in place, so they point at this revision.
- Windows uninstall now has one extra step.
INSTALL.mddocuments removing the
desktop.lnkalongside the Start Menu one. - No new dependencies and no third-party code were added. Shortcuts use the
built-in WindowsWScript.ShellCOM object and existing .NET APIs, and the
caching change only adds verification steps to the existing verify-then-build
chain. - macOS and Ubuntu behaviour is unchanged in this release.
Release identity
- Tag:
v0.3.0 - Commit:
fc5274fa5a5257dbf092602280bfd506eb7ba5ee
Installer script SHA-256 values:
ff3a6e03936f6c7d1aeddb32829be2fe7a9a2574e614d5145f65745f5b8c1530 install.ps1
a67893701328c14f74b8694d9ab7248b73fdf0076a8631ef9a87d15e9692e481 install.sh
Install from the exact release
Windows PowerShell:
$commit="fc5274fa5a5257dbf092602280bfd506eb7ba5ee"; $env:SKILL_RECORDER_COMMIT=$commit; irm "https://raw.githubusercontent.com/microsoft/skill-recorder/$commit/install.ps1" | iexmacOS or Ubuntu:
commit="fc5274fa5a5257dbf092602280bfd506eb7ba5ee"; curl -fsSL "https://raw.githubusercontent.com/microsoft/skill-recorder/$commit/install.sh" | SKILL_RECORDER_COMMIT="$commit" bashThe safer procedure is to download and inspect the script, verify its SHA-256
against the values above, and only then execute it. See the immutable
installation guide.
The source installers do not require administrator access or a global Node.js
or Copilot CLI installation. GitHub Copilot authentication, entitlement, and
network access are still required.
Licensing boundary
The MIT license covers Skill Recorder's own code. Third-party components remain
under their respective licenses and notices. The source installers retain the
applicable legal materials in the local installation. A locally assembled
application is for local execution only and must not be redistributed as a
release artifact.
Maintainers should follow the immutable
release runbook
before publishing later versions or any binary artifact.