apify-cli 0.13.1-beta.0 → 0.13.1-beta.2

package/npm-shrinkwrap.json

@@ -61,7 +61,7 @@
                 "sinon": "^9.2.4"
             },
             "engines": {
-                "node": ">=12.0.0"
+                "node": ">=16.0.0"
             }
         },
         "node_modules/@apify/actor-templates": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "apify-cli",
-  "version": "0.13.1-beta.0",
+  "version": "0.13.1-beta.2",
   "description": "Apify command-line interface helps you create, develop, build and run Apify actors, and manage the Apify cloud platform.",
   "main": "index.js",
   "scripts": {
@@ -49,7 +49,7 @@
   },
   "homepage": "https://github.com/apify/apify-cli#readme",
   "engines": {
-    "node": ">=12.0.0"
+    "node": ">=16.0.0"
   },
   "dependencies": {
     "@apify/actor-templates": "^0.1.3",

package/src/commands/push.js

@@ -18,6 +18,13 @@ const DEFAULT_RUN_OPTIONS = {
     memoryMbytes: 4096,
     timeoutSecs: 3600,
 };
+const DEFAULT_ACTOR_VERSION_NUMBER = '0.0';
+
+// It would be better to use `version-0.0` or similar,
+// or even have no default tag, but the platform complains when
+// actor does not have a build with a `latest` tag, so until
+// that changes, we have to add it.
+const DEFAULT_BUILD_TAG = 'latest';
 
 class PushCommand extends ApifyCommand {
     async run() {
@@ -29,8 +36,15 @@ class PushCommand extends ApifyCommand {
         let actorId;
         let actor;
         // User can override actor version and build tag, attributes in localConfig will remain same.
-        const version = flags.version || flags.versionNumber || localConfig.version || '0.0';
-        const buildTag = flags.buildTag || localConfig.buildTag;
+        const version = flags.version || flags.versionNumber || localConfig.version || DEFAULT_ACTOR_VERSION_NUMBER;
+        let buildTag = flags.buildTag || localConfig.buildTag;
+        // We can't add the default build tag to everything. If a user creates a new
+        // version, e.g. for testing, but forgets to add a tag, it would use the default
+        // tag and their production runs might be affected ❌
+        // TODO: revisit this when we have better build tagging system on platform.
+        if (!buildTag && version === DEFAULT_ACTOR_VERSION_NUMBER) {
+            buildTag = DEFAULT_BUILD_TAG;
+        }
         const waitForFinishMillis = Number.isNaN(flags.waitForFinish)
             ? undefined
             : parseInt(flags.waitForFinish, 10) * 1000;