Repository navigation
Conversation
…readme Closes #1454 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…uild Only a 404 means the Actor has no default build. Any other error now fails the command instead of silently printing the `latest` schema with exit 0. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
2 participants
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.
Note
TL;DR —
actors info --inputand--readmenow read the Actor's default build, not thelatesttag. Actors without alatesttag no longer print "No input schema found" with exit 0, and Actors where the two builds differ no longer show the wrong schema. This also fixes the red E2E nightly. Small change in one command, with a fallback tolatest.Closes #1454
Changes
src/commands/actors/info.ts: for--inputand--readme, resolve the build withclient.actor(id).defaultBuild(). Fall back totaggedBuilds.latestif that call fails. This follows the approach agreed on the issue, and it also handlesdefaultRunOptions.buildset to a build number.test/local/commands/actors-info.test.ts: 3 tests with a mocked client: nolatesttag, default build preferred overlatest, fallback tolatest. The first two fail without the fix.Evidence
apify/rag-web-browsernow has onlybeta-3andversion-1tags.defaultRunOptions.buildisversion-1.actors/info.test.ts > shows input schema with --input flagfails on the last 3 master nightlies (10-03 to 10-05) withSyntaxError: Unexpected token 'E', because the CLI printed the error text instead of JSON: failing job 10-05.defaultBuild()returned the right input schema forapify/rag-web-browser(15 properties),apify/web-scraper(39) andapify/hello-world(1), without a token.Not verified
TEST_USER_TOKEN). The next E2E nightly will show it.🤖 Generated with Claude Code