Skip to content

flowreel 0.2.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Oct 21:08
· 17 commits to main since this release
v0.2.1
41abc48
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Install: npm install --save-dev @confidee/flowreel@0.2.1 (npm, published by the release workflow with a provenance attestation).

Documentation and release tooling only; the runtime's behaviour is
unchanged. The npm page now shows the logo, badges and the demo video's
thumbnail.

Added

  • The release workflow creates the GitHub Release after the npm publish:
    a third job (github-release, the only one that can write to the
    repository, and it never sees the npm token) titles it
    "flowreel " with an install line and the version's
    CHANGELOG.md section as its notes (scripts/release-notes.mjs, with
    unit tests). A release that already exists is left unchanged.
  • A 76-second narrated demo video at the top of the README, recorded with
    flowreel 0.2.0 from npm. The video, its thumbnail and the run's report
    are in assets/demo/; the leak tripwire allows the publisher's name in
    that demo's README and run report only.
  • The npm page (the runtime README) shows the demo's thumbnail, linked to
    the video on the project README (npm does not play videos); it appears
    on npm with the next release. Its logo is now the full mint logo (the
    symbol and the name, 320 px wide) instead of the small symbol alone.
  • Badges under the logo in the README and the npm page: npm version, CI,
    license, Node and Claude Code plugin.

Changed

  • CI can also be started by hand (Actions -> CI -> Run workflow).
  • README: install from npm (@confidee/flowreel is published); a clone
    is only for trying an unreleased change.
  • Docs: they now say the package is on npm (no "pre-release" or "until the
    runtime is on a registry"), and the example's setup offers the npm
    install first.
  • Docs: exit 130 and the INCOMPLETE verdict for an interrupted run are
    documented everywhere the exit codes are listed.
  • Docs: the tour scanner's TypeScript range is stated (5.x and 6.x;
    TypeScript 7 is not supported yet, issue #6), with a troubleshooting
    entry.
  • Docs: links in the plugin's templates and README work outside the
    repository; the changelog has version links.
  • Dependabot no longer proposes major versions of typescript (TypeScript
    7 has no JavaScript compiler API, which the tour scanner uses) or
    @types/node (the type definitions follow the supported Node versions,
    raised on purpose). Minor and patch updates still arrive.
Assets 2
Loading