Update spelling and workflow versions

.github/workflows/release.yml

@@ -22,6 +22,7 @@ on:
 
 jobs:
   release:
-    if: "startsWith(github.event.head_commit.message, 'Release: v')"
+    if: |-
+      ${{ startsWith(github.event.head_commit.message, 'Release: v') }}
     name: 'Release'
     uses: 'google-github-actions/.github/.github/workflows/release.yml@v0'

.github/workflows/troubleshooting.yml

@@ -27,7 +27,7 @@ jobs:
     runs-on: 'ubuntu-latest'
 
     steps:
-      - uses: 'actions/github-script@v6'
+      - uses: 'actions/github-script@v7'
         with:
           script: |-
             const msg =

README.md

@@ -618,7 +618,7 @@ as a secret.
 > [!CAUTION]
 >
 > Google Cloud Service Account Key JSON files must be secured
-> and treated like a password. Anyone with acess to the JSON key can
+> and treated like a password. Anyone with access to the JSON key can
 > authenticate to Google Cloud as the underlying Service Account. By default,
 > these credentials never expire, which is why the former authentication options
 > are much preferred.

action.yml

@@ -143,7 +143,7 @@ inputs:
     description: |-
       Number of times to retry a failed authentication attempt. This is useful
       for automated pipelines that may execute before IAM permissions are fully
-      propogated.
+      propagated.
     deprecationMessage: |-
       This field is no longer used and will be removed in a future release.
     required: false

docs/TROUBLESHOOTING.md

@@ -9,7 +9,7 @@
     > [!CAUTION]
     >
     > Enabling debug logging increases the chances of a secret
-    > being accidentially logged. While GitHub Actions will scrub secrets,
+    > being accidentally logged. While GitHub Actions will scrub secrets,
     > please take extra caution when sharing these debug logs in publicly
     > accessible places like GitHub issues.
     >
@@ -81,7 +81,7 @@
         token", it means admission into the Workload Identity Pool failed. Check
         your [**Attribute Conditions**][attribute-conditions].
 
-    -   If the error message inclues "Failed to generate OAuth 2.0 Access
+    -   If the error message includes "Failed to generate OAuth 2.0 Access
         Token", it means Service Account Impersonation failed. Check your
         [**Service Account Impersonation**][sa-impersonation] settings and
         ensure the principalSet is correct.

src/post.ts

@@ -34,7 +34,7 @@ export async function run(logger: Logger) {
 
     // Look up the credentials path, if one exists. Note that we only check the
     // environment variable set by our action, since we don't want to
-    // accidentially clean up if someone set GOOGLE_APPLICATION_CREDENTIALS or
+    // accidentally clean up if someone set GOOGLE_APPLICATION_CREDENTIALS or
     // another environment variable manually.
     const credentialsPath = process.env['GOOGLE_GHA_CREDS_PATH'];
     if (!credentialsPath) {