[github-actions]

Build Info

npx @taskless/cli-nightly@0.13.4-20261024003540xfa2ac04

Built from: fa2ac04
Committed at: 2026-10-24 00:35:40

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@taskless/cli@0.13.4

Compare with v0.13.3

Patch Changes

• fa2ac04: taskless check prints only error-severity findings when CI is true or 1, and ends with a count of the warnings, infos, and hints it left out. Pass --include-warnings to print them. --json output and the exit code are unchanged.

• cf968ff: taskless detect now finds a linter the way its ecosystem usually installs or runs it, not only from a dedicated config file, so a repository that lints on a tool's defaults no longer reads as having no linter.

  • Dependencies are read from every ecosystem's manifest: pyproject.toml dev dependencies (PEP 735 [dependency-groups], which uv add --dev writes, [tool.uv] dev-dependencies, [tool.pdm.dev-dependencies], Hatch environments, and Poetry groups, which were previously read by group name), every pip requirements file such as requirements-dev.txt or requirements/*.txt, Gemfile gems, composer.json require-dev, go.mod tool directives, and Package.swift packages.
  • Config inside a manifest: [lints.clippy] in Cargo.toml, a [flake8] section in setup.cfg or tox.ini, and the prettier and stylelint keys in package.json.
  • A root CI or hook config that runs the linter, such as a workflow running cargo clippy or a pre-commit hook from astral-sh/ruff-pre-commit. Being a Rust repository is not on its own evidence of clippy.
  • New linters: standard, pint, and php-cs-fixer. ESLint, Prettier, and stylelint gain their TypeScript and other missing config filenames.

• 172f963: Rules for a linter the repository already runs now follow a fixed order. The agent first looks for a rule the linter already ships, checking each tool's catch-all rules by name (no-restricted-syntax, banned-api, noRestrictedImports, and others). It writes a new custom rule in that linter only when the repository already has five or more of its own to model it on. Otherwise the request becomes a Taskless rule. route (topic v8) no longer asks the user to choose between a linter rule and a Taskless rule, and it describes each linter detect found in the repository. During onboarding (topic v11), the agent only enables rules the repository's installed packages already ship.

  detect --json reports customRules for ESLint, Biome, pylint, flake8, and Ruff: how many rules the repository wrote itself for that linter, and where they are. A count that cannot be read without running a JavaScript config is reported as "unknown".

  taskless agent create-legacy-rule --tool=<name> serves a recipe for one linter, named as detect reports it: ruff, eslint (including typescript-eslint), biome, pylint, or flake8. Each recipe names the tool's catch-all rules, says how to confirm a rule exists in the installed version (ruff rule, biome explain, pylint --help-msg), and covers the traps that make a rule silently not fire, such as Ruff preview rules and ESLint 10's removal of .eslintrc. The ESLint recipe also lists eight well-known plugins, each with a docs link. Other tool names fall back to the generic recipe. ast-grep, vale, prettier, and black are refused with a pointer to the right recipe. route now names the --tool command for each linter it describes.

• 5d6da09: A nightly init installs beside the release and no longer offers to move @taskless/cli pins in scripts, CI, or hooks onto @taskless/cli-nightly. It also keeps the release's recorded version when the manifest predates install.launchers, so .taskless/bin/cli.mjs still has a version to run. A release init now retires the nightly: it removes .taskless/bin/cli-nightly.mjs and its lockfile, drops the nightly's recorded version and permission rules, and names any @taskless/cli-nightly pin left in scripts, CI, or hooks. Any package.json dependency on the CLI is now raised for removal in favour of the project launcher, and pinnedCli entries carry a reason.