chore: version packages - #407
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
September 27, 2026 20:10
709d839 to
ca17cdb
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.
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.11.4
Compare with v0.11.3
Patch Changes
sgandvalerules run without one.taskless auth loginis unchanged, and commands that need an account still say so.taskless checknow exits 1 when the Taskless service withholds a runtime rule because the organization's plan does not include runtime rules, instead of printing a notice and exiting 0. The output names the withheld rules and links to the upgrade page, and--jsoncarries anentitlementobject. If a CI job starts failing with this, the rules did not stop matching: they stopped running, and the fix is the plan, not the code. Unauthenticated and--anonymousruns, andsgandvalerules, are unchanged.Build Info
npx @taskless/cli-nightly@0.11.4-20260927201224x86799efBuilt from: 86799ef
Built at: 2026-09-27 20:12:24