Updates node version to v24

README.md

@@ -1,32 +1,39 @@
 # CLI for Microsoft 365 Runscript
+
 GitHub action to run a script using the CLI for Microsoft 365
 
 ![CLI for Microsoft 365 Runscript](./images/pnp-cli-microsoft365-blue.svg)
 
 This GitHub Action (created using typescript) uses [CLI for Microsoft 365](https://pnp.github.io/cli-microsoft365/), to run a line of script supplied to it or run code in a script file supplied to it.
 
 ## Usage
+
 ### Pre-requisites
+
 Create a workflow `.yml` file in `.github/workflows` directory of your repo. An [example workflow](#example-workflow---cli-for-microsoft-365-runscript) is available below. For more information, reference the GitHub Help Documentation for [Creating a workflow file](https://help.github.com/en/articles/configuring-a-workflow#creating-a-workflow-file).
 
 ## Dependencies on other GitHub Actions
 
 - [CLI for Microsoft 365 Login](https://github.com/pnp/action-cli-login) – **Required** . This action is dependant on `action-cli-login`. So in the workflow we need to run  `action-cli-login` before using this action.
 
-#### Optional requirement
+### Optional requirement
+
 Since `action-cli-login` requires user name and password which are sensitive pieces of information, it would be ideal to store them securely. We can achieve this in a GitHub repo by using [secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets). So, click on `settings` tab in your repo and add 2 new secrets:
+
 - `adminUsername` - store the admin user name in this (e.g. user@contoso.onmicrosoft.com)
 - `adminPassword` - store the password of that user in this.
 These secrets are encrypted and can only be used by GitHub actions.
 
 ### Inputs
+
 - `CLI_MICROSOFT365_SCRIPT_PATH` : Relative path of the script in your repo.
 - `CLI_MICROSOFT365_SCRIPT` : The script to run
 - `IS_POWERSHELL` : `true|false` Used only with CLI_MICROSOFT365_SCRIPT. If true the assumption is the script passed in CLI_MICROSOFT365_SCRIPT will be a PowerShell script, otherwise the assumption is bash script. Default is false
 
 One of `CLI_MICROSOFT365_SCRIPT_PATH` / `CLI_MICROSOFT365_SCRIPT` is mandatory, in case both are defined `CLI_MICROSOFT365_SCRIPT_PATH` gets preference.
 
 ### Example workflow - CLI for Microsoft 365 Runscript
+
 On every `push` build the code, then deploy and then send an email using CLI for Microsoft 365 Runscript action.
 
 ```yaml
@@ -40,36 +47,41 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [18.x]
+        node-version: [24]
 
     steps:
 
     # CLI for Microsoft 365 login action
     - name: Login to tenant
-      uses: pnp/action-cli-login@v3
+      uses: pnp/action-cli-login@v4
       with:
         ADMIN_USERNAME:  ${{ secrets.adminUsername }}
         ADMIN_PASSWORD:  ${{ secrets.adminPassword }}
 
     # CLI for Microsoft 365 runscript action option 1 (single line of script as input)
     - name: Send email
-      uses: pnp/action-cli-runscript@v3
+      uses: pnp/action-cli-runscript@v4
       with:
-        CLI_MICROSOFT365_SCRIPT: m365 spo mail send --webUrl https://contoso.sharepoint.com/sites/teamsite --to 'user@contoso.onmicrosoft.com' --subject 'Deployment done' --body '<h2>CLI for Microsoft 365</h2> <p>The deployment is complete.</p> <br/> Email sent via CLI for Microsoft 365 GitHub Action.'
+        CLI_MICROSOFT365_SCRIPT: m365 outlook mail send --to 'john.doe@contoso.onmicrosoft.com' --subject 'Deployment done' --bodyContents '<h2>CLI for Microsoft 365</h2> <p>The deployment is complete.</p> <br/> Email sent via CLI for Microsoft 365 GitHub Action.' --bodyContentType HTML
 
     # CLI for Microsoft 365 runscript action option 2 (script file as input)
     - name: Create lists
-      uses: pnp/action-cli-runscript@v3
+      uses: pnp/action-cli-runscript@v4
       with:
         CLI_MICROSOFT365_SCRIPT_PATH: ./script/lists.ps1 
         #lists.ps1 will have all the required CLI for Microsoft 365 commands
 ```
 
 #### Self-hosted runners
-If self-hosted runners are used for running the workflow, then please make sure that they have `PowerShell` or `bash` installed on them. 
+
+If self-hosted runners are used for running the workflow, then please make sure that they have `PowerShell` or `bash` installed on them.
 
 ## Release notes
 
+### v4.0.0
+
+- Bumped to Node version 24
+
 ### v3.0.0
 
 - Bumped to Node version 20
@@ -79,4 +91,5 @@ If self-hosted runners are used for running the workflow, then please make sure
 - Renames action to 'CLI for Microsoft 365 Runscript'
 
 ### v1.0.0
-- Added initial 'CLI for Microsoft 365 runscript' GitHub action solving #2
+
+- Added initial 'CLI for Microsoft 365 runscript' GitHub action solving #2

action.yml

@@ -4,11 +4,11 @@ inputs:
   CLI_MICROSOFT365_SCRIPT_PATH:  
     description: 'Relative path of the script in your repo.'
   CLI_MICROSOFT365_SCRIPT:
-    description: 'CLI for Microsoft 365 Script'
+    description: 'CLI for Microsoft 365 Script.'
   IS_POWERSHELL:
-    description: 'Used only with CLI_MICROSOFT365_SCRIPT. If true the assumption is the script passed in CLI_MICROSOFT365_SCRIPT will be a PowerShell script, otherwise the assumption is bash script. Default is false'
+    description: 'Used only with CLI_MICROSOFT365_SCRIPT. If true the assumption is the script passed in CLI_MICROSOFT365_SCRIPT will be a PowerShell script, otherwise the assumption is bash script. Default is false.'
 runs:
-  using: "node20"
+  using: "node24"
   main: "dist/index.js"
 branding:
   icon: 'terminal'  

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnp/action-cli-runscript",
-  "version": "3.0.0",
+  "version": "4.0.0",
   "description": "A GitHub Action that runs a CLI for Microsoft 365 script",
   "main": "dist/index.js",
   "scripts": {
@@ -108,7 +108,7 @@
     "@actions/io": "^1.1.1"
   },
   "devDependencies": {
-    "@types/node": "^16.11.6",
+    "@types/node": "^24.10.4",
     "@vercel/ncc": "^0.31.1",
     "typescript": "^4.4.4"
   }