Repository navigation
chore: version packages - #573
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 19:51
4b9f575 to
145ac64
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 19:54
145ac64 to
3fb54ad
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build Info
npx @taskless/cli-nightly@0.13.4-20261022195405x50b7ee6Built 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 detectnow 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.pyproject.tomldev dependencies (PEP 735[dependency-groups], whichuv add --devwrites,[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 asrequirements-dev.txtorrequirements/*.txt,Gemfilegems,composer.jsonrequire-dev,go.modtooldirectives, andPackage.swiftpackages.[lints.clippy]inCargo.toml, a[flake8]section insetup.cfgortox.ini, and theprettierandstylelintkeys inpackage.json.cargo clippyor a pre-commit hook fromastral-sh/ruff-pre-commit. Being a Rust repository is not on its own evidence of clippy.standard,pint, andphp-cs-fixer. ESLint, Prettier, and stylelint gain their TypeScript and other missing config filenames.5d6da09: A nightly
initinstalls beside the release and no longer offers to move@taskless/clipins in scripts, CI, or hooks onto@taskless/cli-nightly. It also keeps the release's recorded version when the manifest predatesinstall.launchers, so.taskless/bin/cli.mjsstill has a version to run. A releaseinitnow retires the nightly: it removes.taskless/bin/cli-nightly.mjsand its lockfile, drops the nightly's recorded version and permission rules, and names any@taskless/cli-nightlypin left in scripts, CI, or hooks. Anypackage.jsondependency on the CLI is now raised for removal in favour of the project launcher, andpinnedClientries carry areason.