edgeone 1.0.16-beta.2 → 1.0.17

package/README.md

@@ -152,7 +152,7 @@ edgeone pages deploy <directoryOrZip> -t <token>
 #### Parameters
 
 - `<directoryOrZip>`: Path of folder or ZIP package to deploy (required)
-- `-t, --token`: API Token for CI/CD pipelines (required for non-interactive environments)
+- `-t, --token`: API Token for CI/CD pipelines (required)
 - `-e, --env`: Environment to deploy to, choices: 'production' or 'preview' (default: 'production')
 
 #### CI Pipeline Examples
@@ -167,14 +167,15 @@ edgeone pages deploy ./build.zip -e preview -t $EDGEONE_API_TOKEN
 
 #### Obtaining an API Token
 
-For more information, please refer to https://edgeone.ai/document/177158578324279296
+How to create an API Token
 
-To use the deploy command in CI/CD pipelines, you need to generate an API token:
+1. Access the Pages console and switch to the "API Token" Tab.
+2. Click "Create API Token".
+3. Enter "Token description" to help you remember the purpose of the API Token.
+4. Select "expiration time" to ensure your information security.
+5. Click Submit.
 
-1. Log in to the EdgeOne Console
-2. Navigate to the Pages project settings
-3. Generate an API token with deployment permissions
-4. Add this token as a secure environment variable in your CI/CD system
+For more information, please refer to https://edgeone.ai/document/177158578324279296
 
 <br/>
 

package/edgeone-dist/cli.js

@@ -180275,7 +180275,7 @@ var yargs_default = Yargs;
 // package.json
 var package_default = {
   name: "edgeone",
-  version: "1.0.16-beta.2",
+  version: "1.0.17",
   description: "Command-line interface for TencentCloud Pages Functions",
   bin: {
     edgeone: "./edgeone-bin/edgeone.js"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edgeone",
-  "version": "1.0.16-beta.2",
+  "version": "1.0.17",
   "description": "Command-line interface for TencentCloud Pages Functions",
   "bin": {
     "edgeone": "./edgeone-bin/edgeone.js"