chore: add pnpm workspace configuration to manage packages (#1130)

* chore: add pnpm workspace configuration to manage packages

* fix(ci): update test command to use pnpm instead of npm

* chore: update governance and contributing guidelines, remove package-lock.json

Author: rxmarbles

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,15 @@
+---
+name: 📃 Documentation Bug
+about: You want to report something that is wrong or missing from the documentation.
+labels: "Type: Docs"
+---
+
+## 📃 Summary
+<!--
+  A clear and concise description of what is missing
+-->
+
+## Expected documentation
+<!--
+  A clear and concise description of what you'd like to read
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -13,7 +13,7 @@ Explain the **motivation** for making this change. What existing problem does th
 
 <!--
 Help reviewers and the release process by included a changeset entry.
-Use `npm run changeset` and follow the prompts to create a changeset.
+Use `pnpm run changeset` and follow the prompts to create a changeset.
 -->
 
 - [ ] Changeset added ([docs](https://github.com/godaddy/javascript#submit-a-changeset))

.github/dependabot.yml

@@ -4,40 +4,40 @@ updates:
     package-ecosystem: github-actions
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
   - directory: /
     package-ecosystem: npm
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
   - directory: /packages/eslint-config-godaddy
     package-ecosystem: npm
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
   - directory: /packages/eslint-config-godaddy-flow
     package-ecosystem: npm
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
   - directory: /packages/eslint-config-godaddy-react
     package-ecosystem: npm
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
   - directory: /packages/eslint-config-godaddy-react-flow
     package-ecosystem: npm
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
   - directory: /packages/eslint-config-godaddy-react-typescript
     package-ecosystem: npm
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
   - directory: /packages/eslint-config-godaddy-typescript
     package-ecosystem: npm
     rebase-strategy: auto
     schedule:
-      interval: daily
+      interval: weekly
 

.github/workflows/cicd.yml

@@ -14,11 +14,15 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v5
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
           node-version-file: '.nvmrc'
+          cache: 'pnpm'
       - name: Install dependencies
-        run: npm ci
+        run: pnpm install
       - name: Test
-        run: npm test
+        run: pnpm test

.github/workflows/release.yaml

@@ -19,16 +19,18 @@ jobs:
         uses: actions/setup-node@v5
         with:
           node-version-file: '.nvmrc'
+          cache: 'pnpm'
 
       - name: Install Dependencies
-        run: npm ci
+        run: pnpm install --prefer-offline
 
       - name: Create Release Pull Request or Publish to npm
         id: changesets
         uses: changesets/action@v1
         with:
+          version: pnpm run version
           # This expects you to have a script called release which does a build for your packages and calls changeset publish
-          publish: npm run release
+          publish: pnpm run release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_SECRET }}

.github/workflows/stale.yml

@@ -9,7 +9,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Close Stale Issues
-      uses: actions/stale@v8.0.0
+      uses: actions/stale@v9
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
         stale-pr-message: |

.nvmrc

@@ -1 +1 @@
-22
+24

CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age,
+body size, disability, ethnicity, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event. Representation of a
+project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the GoDaddy OSPO (Open Source Policy Office) at
+oss@godaddy.com. All complaints will be reviewed and investigated and will
+result in a response that is deemed necessary and appropriate to the
+circumstances. The project team is obligated to maintain confidentiality with
+regard to the reporter of an incident. Further details of specific enforcement
+policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq
+
+[homepage]: https://www.contributor-covenant.org