v1.17.2

.eslintrc

@@ -5,6 +5,7 @@
     "react/destructuring-assignment": 0,
     "react/no-access-state-in-setstate": 0,
     "react/jsx-props-no-spreading": 0,
+    "react/jsx-no-useless-fragment": 1,
     "no-useless-escape": 0
   }
 }

.github/CODEOWNERS

@@ -1 +1 @@
-* @carbon-design-system/developers-auxiliary
+* @carbon-design-system/developers-system-reviewers @eng618

.github/CONTRIBUTING.md

@@ -9,39 +9,51 @@ Want to contribute to this repository? Please read below first:
 
 ## Issues and bugs
 
-If you find a bug in the source code or a mistake in the documentation, you can help us by
-submitting an issue to this repo. Even better you can submit a Pull Request with a fix.
+If you find a bug in the source code or a mistake in the documentation, you can
+help us by submitting an issue to this repo. Even better you can submit a Pull
+Request with a fix.
 
 **Please see the submission guidelines below**.
 
 ## Feature requests
 
-You can request a new feature by submitting an issue to this repo. Proposed features (with suitable design documentation and reasoning) can be crafted and submitted to this repo as a Pull Request.
+You can request a new feature by submitting an issue to this repo. Proposed
+features (with suitable design documentation and reasoning) can be crafted and
+submitted to this repo as a Pull Request.
 
 **Please see the Submission Guidelines below**.
 
 ## Doc fixes
 
-If you want to help improve the docs, it’s a good idea to let others know what you’re working on to minimize duplication of effort. Comment on an issue to let others know what you’re working on, or create a new issue if your work doesn’t fit within the scope of any of the existing doc fix projects.
+If you want to help improve the docs, it’s a good idea to let others know what
+you’re working on to minimize duplication of effort. Comment on an issue to let
+others know what you’re working on, or create a new issue if your work doesn’t
+fit within the scope of any of the existing doc fix projects.
 
 **Please see the submission guidelines below**.
 
 ## Submission guidelines
 
 ### Setup
 
-1. Fork the project by navigating to the main [repository](https://github.com/carbon-design-system/gatsby-theme-carbon) and clicking the **Fork** button on the top-right corner.
+1. Fork the project by navigating to the main
+   [repository](https://github.com/carbon-design-system/gatsby-theme-carbon) and
+   clicking the **Fork** button on the top-right corner.
 
-2. Navigate to your forked repository and copy the **SSH url**. Clone your fork by running the following in your terminal:
+2. Navigate to your forked repository and copy the **SSH url**. Clone your fork
+   by running the following in your terminal:
 
    ```
    $ git clone [email protected]:{ YOUR_USERNAME }/gatsby-theme-carbon.git
    $ cd gatsby-theme-carbon
    ```
 
-   See [GitHub docs](https://help.github.com/articles/fork-a-repo/) for more details on forking a repository.
+   See [GitHub docs](https://help.github.com/articles/fork-a-repo/) for more
+   details on forking a repository.
 
-3. Once cloned, you will see `origin` as your default remote, pointing to your personal forked repository. Add a remote named `upstream` pointing to the main `gatsby-theme-carbon`:
+3. Once cloned, you will see `origin` as your default remote, pointing to your
+   personal forked repository. Add a remote named `upstream` pointing to the
+   main `gatsby-theme-carbon`:
 
    ```
    $ git remote add upstream [email protected]:carbon-design-system/gatsby-theme-carbon.git
@@ -59,52 +71,74 @@ If you want to help improve the docs, it’s a good idea to let others know what
 
 ### Submitting an issue
 
-Before you submit your issue, search the repository. Maybe your question was already answered.
+Before you submit your issue, search the repository. Maybe your question was
+already answered.
 
-If your issue appears to be a bug, and hasn’t been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues.
+If your issue appears to be a bug, and hasn’t been reported, open a new issue.
+Help us to maximize the effort we can spend fixing issues and adding new
+features, by not reporting duplicate issues.
 
 ### Submitting a pull request
 
-1. Search this repository for an open or closed pull request that relates to your submission. You don’t want to duplicate effort.
+1. Search this repository for an open or closed pull request that relates to
+   your submission. You don’t want to duplicate effort.
 
-2. Pull the latest master branch from `upstream`:
+2. Pull the latest main branch from `upstream`:
 
    ```
-   $ git pull upstream master
+   $ git pull upstream main
    ```
 
-3. Always work and submit pull requests from a branch. _Do not submit pull requests from the `master` branch of your fork_.
+3. Always work and submit pull requests from a branch. _Do not submit pull
+   requests from the `main` branch of your fork_.
 
    ```
-   $ git checkout -b { YOUR_BRANCH_NAME } master
+   $ git checkout -b { YOUR_BRANCH_NAME } main
    ```
 
-4. Create your patch or feature following our [development guidelines](/README.md#development). Make sure to also follow our [coding standards](#coding-standards).
+4. Create your patch or feature following our
+   [development guidelines](/README.md#development). Make sure to also follow
+   our [coding standards](#coding-standards).
 
-5. Test your branch and add new test cases where appropriate per the [testing guidelines](#testing).
+5. Test your branch and add new test cases where appropriate per the
+   [testing guidelines](#testing).
 
 6. Commit your changes using a descriptive commit message.
 
    ```
    $ git commit -a -m "chore: Update header with newest designs, resolves #123"
    ```
 
-   **Note:** the optional commit `-a` command line option will automatically `add` and `rm` edited files. See [Close a commit via commit message](https://help.github.com/articles/closing-issues-via-commit-messages/) and [writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages) for more details on commit messages.
+   **Note:** the optional commit `-a` command line option will automatically
+   `add` and `rm` edited files. See
+   [Close a commit via commit message](https://help.github.com/articles/closing-issues-via-commit-messages/)
+   and
+   [writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages)
+   for more details on commit messages.
 
-7. Once ready for feedback from other contributors and maintainers, **push your commits to your fork** (be sure to run `yarn ci-check` before pushing, to make sure your code passes linting and unit tests):
+7. Once ready for feedback from other contributors and maintainers, **push your
+   commits to your fork** :
 
    ```
    $ git push origin { YOUR_BRANCH_NAME }
    ```
 
-8. In GitHub, navigate to [carbon-design-system/gatsby-theme-carbon](https://github.com/carbon-design-system/gatsby-theme-carbon) and click the button that reads "Compare & pull request".
+8. In GitHub, navigate to
+   [carbon-design-system/gatsby-theme-carbon](https://github.com/carbon-design-system/gatsby-theme-carbon)
+   and click the button that reads "Compare & pull request".
 
 9. Write a title and description, the click "Create pull request".
 
-   See [how to write the perfect pull request](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) for more details on writing good PRs.
+   See
+   [how to write the perfect pull request](https://github.com/blog/1943-how-to-write-the-perfect-pull-request)
+   for more details on writing good PRs.
 
-10. Stay up to date with the activity in your pull request. Maintainers will be reviewing your work and making comments, asking questions and suggesting changes to be made before they merge your code. When you need to make a change, add, commit and push to your branch normally.
+10. Stay up to date with the activity in your pull request. Maintainers will be
+    reviewing your work and making comments, asking questions and suggesting
+    changes to be made before they merge your code. When you need to make a
+    change, add, commit and push to your branch normally.
 
-    Once all revisions to your pull request are complete, a maintainer will squash and merge your commits for you.
+    Once all revisions to your pull request are complete, a maintainer will
+    squash and merge your commits for you.
 
 **That’s it! Thank you for your contribution!**

.github/dependabot.yml

@@ -0,0 +1,33 @@
+version: 2
+updates:
+  # Update Carbon packages
+  - package-ecosystem: "npm"
+    directory: "/packages/gatsby-theme-carbon"
+    schedule:
+      interval: "daily"
+      time: "13:00"
+      timezone: "America/New_York"
+    labels:
+      - ""
+    allow:
+      - dependency-name: "@carbon*"
+    reviewers:
+      - "eng618"
+  # Update all deps monthly
+  - package-ecosystem: npm
+    directory: "/"
+    schedule:
+      interval: "monthly"
+      time: "13:00"
+      timezone: "America/New_York"
+    reviewers:
+      - "eng618"
+  # Update github actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"
+      time: "13:00"
+      timezone: "America/New_York"
+    reviewers:
+      - "eng618"

.github/workflows/manual-release.yml

@@ -0,0 +1,29 @@
+name: Release
+on: workflow_dispatch
+
+jobs:
+  release:
+    if:
+      contains('["alisonjoseph","vpicone", "sstrubberg", "jnm2377", "eng618"]',
+      github.actor)
+    runs-on: ubuntu-latest
+    steps:
+      # fetch-depth: 0 ensures we get commit messages for changelog/versioning
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+          registry-url: https://registry.npmjs.org
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+
+      - name: Run release command
+        run: yarn release:ci
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}