@salesforce/plugin-templates 55.5.9 → 55.5.10

package/messages/apexTrigger.md

@@ -4,7 +4,7 @@ Generate an Apex trigger.
 
 # description
 
-Generates the Apex trigger \*.trigger file and associated metadata file. These files must be contained in a parent directory called "triggers" in your package directory. Either run this command from an existing directory of this name, or use the --output-dir flag to generate one or point to an existing one.
+Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent directory called "triggers" in your package directory. Either run this command from an existing directory of this name, or use the --output-dir flag to generate one or point to an existing one.
 
 If you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with the Salesforce object you want to generate a trigger for. If you don't specify --event, "before insert" is used.
 

package/oclif.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "55.5.9",
+  "version": "55.5.10",
   "commands": {
     "project:generate": {
       "id": "project:generate",
@@ -387,7 +387,7 @@
     "apex:generate:trigger": {
       "id": "apex:generate:trigger",
       "summary": "Generate an Apex trigger.",
-      "description": "Generates the Apex trigger \\*.trigger file and associated metadata file. These files must be contained in a parent directory called \"triggers\" in your package directory. Either run this command from an existing directory of this name, or use the --output-dir flag to generate one or point to an existing one.\n\nIf you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with the Salesforce object you want to generate a trigger for. If you don't specify --event, \"before insert\" is used.",
+      "description": "Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent directory called \"triggers\" in your package directory. Either run this command from an existing directory of this name, or use the --output-dir flag to generate one or point to an existing one.\n\nIf you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with the Salesforce object you want to generate a trigger for. If you don't specify --event, \"before insert\" is used.",
       "strict": true,
       "pluginName": "@salesforce/plugin-templates",
       "pluginAlias": "@salesforce/plugin-templates",

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@salesforce/plugin-templates",
     "description": "Commands to create metadata from a default or custom template",
-    "version": "55.5.9",
+    "version": "55.5.10",
     "main": "lib/index.js",
     "author": "Salesforce",
     "bugs": "https://github.com/salesforcecli/plugin-templates/issues",
@@ -268,7 +268,7 @@
         }
     },
     "sfdx": {
-        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.9.crt",
-        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.9.sig"
+        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.10.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.10.sig"
     }
 }