Skip to content

v1.5.0

Choose a tag to compare

@github-actions github-actions released this 20 Oct 16:06
· 23 commits to develop since this release
a496477

Added

  • Trackers: agents read and send issue files on every tracker. New
    tracker_list_attachments, tracker_download_attachments and
    tracker_attach_files tools fetch an issue's files into the workspace
    (/workspace/tracker/<issue key>/), keep a copy on the issue's task — marked
    with the issue's key on the card — and put files onto issues. A tracker
    trigger can Copy issue files to the task when a run starts. Files visible
    to only some people in the tracker are never copied.
  • Trackers: GitLab issues are a tracker. Pick a GitLab connection's projects
    under Issue boards; a board's label lists, between Open and Closed, are
    the columns, and moving an issue swaps those labels.
  • Integrations: Sign in with GitLab connects as a GitLab service
    account instead of a person's token. A group Owner signs in once; Flow creates
    the account in the group, keeps only its token for repositories, merge
    requests and issues, and rotates it before a required expiry. Signing in to
    the same group again reuses that account; removing the connection revokes its
    token, and a group Owner deletes the account in GitLab. Operators set
    GITLAB_OAUTH_CLIENT_ID and GITLAB_OAUTH_CLIENT_SECRET to offer it.
  • Trackers: on GitHub Projects, files sent to an issue are stored in the
    issue's repository under hidden refs/aixle/attachments/ refs, so images show
    inline in private repositories; Link files instead on the Trackers page
    keeps them on the Aixle task.
  • Admin: a superadmin can invite a company's people from the admin, without
    signing in as its admin. The company form, new or edit, takes a list of
    addresses and a role. Any company's page has "Invite members", which takes a
    pasted list and shows who is invited and who has joined. Each person gets the
    invitation a company admin sends from Members, from "An administrator".

Changed

  • Triggers & gates: the trigger form's on/off switch is labeled Trigger
    enabled
    and says that what arrives while a trigger is off is not run when
    it is turned back on.
  • Admin: a new company's initial admin is invited instead of being given a
    password by the operator. The form asks only for their address; they get the
    standard invitation email, set their own password and join as admin. Until
    they accept they show as Pending under "Invite members", where a Re-send button
    sends the invitation again. A platform administrator's address is refused, and
    an email that cannot be sent leaves the company in place and says so.
  • Tasks: a task's Properties — column, type, priority, assignee, epic, tags —
    sit right under its title, above the description, so a long description no
    longer pushes them out of view.
  • Sessions & Runs: agent CLIs raised to Claude Code 2.1.303, Codex 0.163.0,
    Cursor CLI 2026.10.18-ea085cb, Grok 1.0.62, Kiro CLI 2.32.0 and Antigravity
    CLI 1.4.2. Gemini CLI stays at 0.60.0: every newer release still stops
    --yolo at a prompt when the agent edits a build file.
  • Sessions & Runs: Antigravity CLI telemetry follows the setting on the
    user's Google account (/config in the CLI, or the "Terms of Service & Data
    Use" step) instead of being switched off by the image, which releases after
    1.1.27 no longer allow.
  • Integrations: the Aixle Flow app for YouTrack (1.0.2) sets itself up through
    YouTrack's own API; only the service user's tokens still go through Hub. The
    service user is now created with a random password that is never stored or
    shown, and the app uses only the aixle-flow user it created: any other
    account with that login stops the setup.

Fixed

  • Workflows: the Base Resources tab scrolls, so resources below the fold
    can be reached.
  • Sessions & Runs: an interactive Antigravity CLI session opens at the
    prompt instead of the CLI's first-run colour scheme, terms and folder-trust
    screens.
  • Sessions & Runs: an Antigravity CLI session no longer replaces its pinned
    CLI with the vendor's newest release a second after it starts.

Images

Published as ghcr.io/aixlehq/flow-<name>:1.5.0: flow-web, flow-otlp-ingest, flow-agent-base-core, flow-claude-code, flow-cursor-cli, flow-codex, flow-gemini-cli, flow-antigravity-cli, flow-grok, flow-kiro-cli. Web 1.5.0 launches the agent images of the same version.

What's Changed

  • fix(youtrack-app): set up through YouTrack's API, Hub only for tokens by @artempartos in #514
  • refactor(usage): drop the legacy tokens column by @artempartos in #515
  • feat(admin): invite a company's members from the admin by @artempartos in #516
  • feat(board): show task properties above the description by @artempartos in #517
  • feat(admin): invite a new company's initial admin instead of a password by @artempartos in #518
  • chore(agents): raise agent CLI pins, Antigravity to 1.4.2 without its first-run screens by @artempartos in #519
  • feat(trackers): issue files on every tracker; GitLab as a tracker over a service account by @artempartos in #513
  • fix(builder): make the Base Resources tab scroll by @dvislov in #520
  • chore(release): 1.5.0 by @artempartos in #521

Full Changelog: v1.4.0...v1.5.0