Skip to content

chore: version packages - #573

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Build Info

npx @taskless/cli-nightly@0.13.4-20261022195405x50b7ee6

Built from: 50b7ee6
Committed at: 2026-10-22 19:54:05

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

  • 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.
  • 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.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 4b9f575 to 145ac64 Compare October 22, 2026 19:51
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 145ac64 to 3fb54ad Compare October 22, 2026 19:54

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants