Skip to content

chore: version packages - #594

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 30, 2026 •

Copy link
Copy Markdown
Contributor

Build Info

npx @taskless/cli-nightly@0.13.5-20261030180659x0b41364

Built from: 0b41364
Committed at: 2026-10-30 18:06:59

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

Compare with v0.13.4

Patch Changes

  • 0b41364: The no-eval-call entry in @taskless/cli/reference.json now flags a call to eval with any number of arguments, as its prompt asks, and carries a fail case for eval() and for eval(a, b). Previously the reference rule matched exactly one argument, so a rule generated correctly from the prompt, with fixtures on each side of the arity boundary as create-sg-rule recommends, was graded against a reference that did not fire on them. The prompt now names the arities it expects. The corpus version is unchanged: the shape is the same, only the content of one entry moved.
  • 0b2ed45: The prefer-use-over-utilize entry in @taskless/cli/reference.json now flags utilized and utilization, as its prompt asks, and carries a fail case for each. Previously the reference rule missed both, so a rule generated correctly from the prompt was graded against a reference that did not fire on those cases. The prompt now names the forms it expects. The corpus version is unchanged: the shape is the same, only the content of one entry moved.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5a7a8e6 to a9e0d99 Compare October 30, 2026 18:07

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