fix: add @godaddy scope

.github/workflows/pr.yaml

@@ -8,7 +8,7 @@ on:
 jobs:
   ci:
     runs-on:
-      - self-hosted
+      - ubuntu-24.04-arm
 
     steps:
       - name: Checkout Repo
@@ -17,7 +17,6 @@ jobs:
       - name: Use Node.js
         uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
         with:
-          cache: npm
           node-version-file: .nvmrc
 
       - name: Install Dependencies

MIGRATION.md

@@ -4,4 +4,5 @@
 
 The following breaking changes were made in v2:
 - Everything was migrated from AWS SDK v2 to AWS SDK v3. This means that you must now pass in V3-generation client instances for liveness checks.
-- The library is now ESM-only. If you are using CommonJS, you will need to use `import()` to load the library or convert the code using this library to ESM.
+- The library is now ESM-only. If you are using CommonJS, you will need to use `import()` to load the library or convert the code using this library to ESM.
+- The package has been renamed to `@godaddy/aws-liveness` to follow the GoDaddy package naming convention. You will need to update your import statements accordingly.

README.md

@@ -13,7 +13,7 @@ npm i --save aws-liveness
 ## Usage
 
 ```javascript
-import AWSLiveness from 'aws-liveness';
+import AWSLiveness from '@godaddy/aws-liveness';
 import { DynamoDBClient } from '@aws-sdk/client-dynamodb';
 
 const awsLiveness = new AWSLiveness();
@@ -53,7 +53,7 @@ By default, `AWSLiveness` supports running the following liveness commands for t
  You can also create additional checks to customize liveness.
 
 ```js
-import AWSLiveness from 'aws-liveness';
+import AWSLiveness from '@godaddy/aws-liveness';
 import { DynamoDBClient, DescribeTableCommand } from '@aws-sdk/client-dynamodb';
 
 class MyCustomService {

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "aws-liveness",
+  "name": "@godaddy/aws-liveness",
   "version": "2.0.0",
   "description": "AWS Liveness tools",
   "type": "module",