Skip to content

Releases

v0.20.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 14:06
75aec8f

What's Changed

  • feat: complete Bitbucket Git authentication and companion updates for v0.20.0 by @AngelMsger in #44

Full Changelog: v0.19.0...v0.20.0

v0.19.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 11:24
8a7b139

What's Changed

  • feat: add scoped release evidence and version history by @AngelMsger in #43

Full Changelog: v0.18.1...v0.19.0

v0.18.1

Choose a tag to compare

@github-actions github-actions released this 12 Nov 09:55
6137a4b

What's Changed

  • fix: clarify release check failures for 0.18.1 by @AngelMsger in #42

Full Changelog: v0.18.0...v0.18.1

v0.18.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 07:27
0054427

What's Changed

  • feat: #40 bind readiness and recovery to the selected context by @AngelMsger in #41

Full Changelog: v0.17.0...v0.18.0

v0.17.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 14:39
31d2283

What's Changed

  • feat: add personal mentors and leaders for 0.17.0 by @AngelMsger in #39

Full Changelog: v0.16.1...v0.17.0

v0.16.1

Choose a tag to compare

@github-actions github-actions released this 10 Nov 06:53
b5eb2b3

What's Changed

Full Changelog: v0.16.0...v0.16.1

v0.16.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 05:58
bedb822

What's Changed

Full Changelog: v0.15.0...v0.16.0

v0.15.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 12:57
6351907

What's Changed

  • fix: keep local files a sync fast-forward would replace by @AngelMsger in #32
  • fix: publish only from a tag that is exactly v by @AngelMsger in #33
  • feat: add WeCom channel support and prepare 0.15.0 by @AngelMsger in #34

Full Changelog: v0.14.0...v0.15.0

v0.14.0

Choose a tag to compare

@github-actions github-actions released this 28 Oct 14:51
b3aa28f

What's Changed

  • feat: refresh Skills when tools or fx update, and update only installed tools by @AngelMsger in #30
  • fix: prefer root VERSION and prepare 0.14.0 by @AngelMsger in #31

Full Changelog: v0.13.0...v0.14.0

v0.13.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 14:41
8e32747

0.13.0 (2026-10-27)

Added

  • Set up companion tools without a manifest. fx init with no directory and no source
    lists the tools in fx's catalog and asks which to set up, by number or name, with
    Enter taking all of them; fx init --tools <name,...> or --tools all names them
    for agents and scripts, and --dry-run previews. fx installs the tools that are
    missing, has each one install its Skill for your coding agents, adds its own
    fx-workspace Skill, and checks whether each one is signed in. On a terminal it
    offers to start the setup of a tool that is not signed in (<tool> config init,
    gh auth login), which asks for the service and your credentials; otherwise, and
    with --yes, the report hands that command to you. No workspace is registered, and
    a manifest still decides the tools and presets the services they point at. The JSON
    report has tools, tool_install and skills, and preparation.scope.workspace
    is null.
  • Let a tool's auth in the catalog or a manifest name the JSON field its status must
    report (json) and the tool's own interactive setup (login). The bundled catalog
    names both for the family CLIs and login for gh, and fx tool show reports them.

Changed

  • Tell a companion's reuse check in a background hook run how long the run can give
    it, through the companion's own --timeout, and leave the check unasked when that is
    under the ten seconds by which a companion bounds the lookups a reuse adds. The check
    used to be ended when the run's time for it ran out. The reuse step's verify in
    fx login --list and the init preview gains deadline, with the flag and the least
    time the check needs (minimumMs).
  • Record LOGIN_UNCHECKED in place of LOGIN_REQUIRED when every login check of a
    background hook run that did not pass was not asked or gave no answer, which
    fx doctor reports as incomplete coverage, as when the run ran out of time for it.

Fixed

  • Count a Jenkins or OpenObserve environment as signed in only when
    jenkins-cli auth status or openobserve-cli auth status reports
    authenticated: true. Both exit zero when nobody is signed in, so on a machine
    without credentials the sign-in step counted as done and fx init and fx sync
    did not ask for it.
  • Leave the declared authentication method out of the OpenObserve and Prometheus
    commands fx where prints and probes, as checks have done since 0.9.1. A probe of
    an OpenObserve context that uses basic authentication was sent with
    --auth-scheme session and refused; the commands now name only the server's URL
    and organization besides the context.

What's Changed

  • fix: give background reuse checks their deadline and drop the sign-in method from coordinates by @AngelMsger in #27
  • feat: set up companion tools with fx init when there is no manifest by @AngelMsger in #28
  • chore: prepare release 0.13.0 by @AngelMsger in #29

Full Changelog: v0.12.0...v0.13.0