apify-cli 1.10.1-beta.21 → 1.10.1-beta.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/actor.js
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
|
-
import{i as e,r as t,t as n}from"./_register-
|
|
2
|
+
import{i as e,r as t,t as n}from"./_register-C2FfMi7H.js";t(`Actor`);for(let e of n)e.registerCommand(`actor`);await e(`actor`);export{};
|
|
3
3
|
//# sourceMappingURL=actor.js.map
|
package/dist/apify.js
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
|
-
import{i as e,n as t,r as n}from"./_register-
|
|
2
|
+
import{i as e,n as t,r as n}from"./_register-C2FfMi7H.js";n(`Apify`);for(let e of t)e.registerCommand(`apify`);await e(`apify`);export{};
|
|
3
3
|
//# sourceMappingURL=apify.js.map
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "apify-cli",
|
|
3
|
-
"version": "1.10.1-beta.
|
|
3
|
+
"version": "1.10.1-beta.23",
|
|
4
4
|
"description": "Apify command-line interface (CLI) helps you manage the Apify cloud platform and develop, build, and deploy Apify Actors.",
|
|
5
5
|
"exports": "./dist/index.js",
|
|
6
6
|
"type": "module",
|
package/skills/apify/SKILL.md
CHANGED
|
@@ -22,9 +22,11 @@ If a command's help shows an "interactive note", it lists exactly which flags ma
|
|
|
22
22
|
|
|
23
23
|
See https://apify.com/auth.md for how to authenticate. Do not assume `APIFY_TOKEN` is already set in the environment and use it implicitly — confirm with the user first.
|
|
24
24
|
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
-
|
|
25
|
+
`APIFY_TOKEN` wins over a stored login, for every command. When it is set, `apify login` refuses to run unless `--token` passes the same token — unset `APIFY_TOKEN` first, or skip the login.
|
|
26
|
+
|
|
27
|
+
- Persist a session explicitly: `apify login --token <token>`. Exits non-zero on a rejected token, so `apify login --token <t> && apify push` is safe to chain.
|
|
28
|
+
- Verify auth: `apify info` (prints the username, user ID, and which source the token came from; non-zero exit / error if not authenticated).
|
|
29
|
+
- Print the token in use: `apify auth token` (the `APIFY_TOKEN` one when set, otherwise the stored login's).
|
|
28
30
|
|
|
29
31
|
## Structured output
|
|
30
32
|
|