merge changes

Author: dreamwasp

.github/actions/yarn/action.yml

@@ -8,6 +8,7 @@ runs:
       uses: actions/setup-node@v4
       with:
         node-version-file: .nvmrc
+        registry-url: 'https://registry.npmjs.org'
     - uses: actions/cache@v4
       with:
         path: |

.github/workflows/publish.yml

@@ -29,29 +29,39 @@ jobs:
           fetch-depth: 0
           token: ${{ secrets.ACTIONS_GITHUB_TOKEN }}
 
+      - name: Get branch name
+        id: branch-name
+        uses: tj-actions/branch-names@v8
+
       - name: Set git user
         run: |
           git config --global user.email "[email protected]"
           git config --global user.name "codecademydev"
           git config --global push.default current
+          echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > .npmrc
 
       - uses: ./.github/actions/yarn
 
       - run: yarn turbo run build --concurrency=3
 
-      - name: Publish
+      - name: Publish Alpha
+        # Only publish alpha on non-main branches
+        if: steps.branch-name.outputs.is_default != 'true'
         env:
           HUSKY_ENABLED: true
           GH_TOKEN: ${{ secrets.ACTIONS_GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npx auto shipit
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          npx lerna publish --yes --canary --dist-tag=alpha.${GITHUB_SHA:0:6} --preid=alpha.${GITHUB_SHA:0:6}
 
-  publish-check:
-    runs-on: ubuntu-22.04
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/yarn
-      - run: npx auto pr-check --url "https://github.com/${{github.repository}}/actions/runs/${{github.run_id}}?pr=${{github.event.pull_request.number}}"
+      - name: Publish
+        # Only publish the non-alpha version on main
+        if: steps.branch-name.outputs.is_default == 'true'
         env:
-          GH_TOKEN: ${{ secrets.ACTIONS_GITHUB_TOKEN || github.token }}
+          HUSKY_ENABLED: true
+          GH_TOKEN: ${{ secrets.ACTIONS_GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          npx lerna publish --yes --exact --conventional-commits --changelog-preset conventionalcommits --include-merged-tags --create-release=github

README.md

@@ -64,35 +64,6 @@ The config for Turborepo is located at [/turbo.json](/turbo.json).
 
 To use Turborepo without extra configuration, if your package needs to be compiled, it should have a task called `build` that compiles it's files and puts them into a directory called `dist` inside the package directory. If you need a more complicated setup, you can read the docs and customize the configuration in `turbo.json`.
 
-**Release Labels**
-
-These labels will mark your PR as ready for release. They will trigger a release of the package(s) you changed once your PR is merged.
-
-- **release/major**: Increments the major version number of the package(s) you changed
-- **release/minor**: Increments the minor version number of the package(s) you changed
-- **release/patch**: Increments the patch version number of the package(s) you changed
-- **release/performance**: Increments the patch version number of the package(s) you changed
-
-These labels will not create a release by default, but will if combined with one of the above labels:
-
-- **release/dependencies**: Changes to dependencies
-- **release/internal**: Changes to internal code
-- **release/tests**: Changes to tests
-
-The skip label will prevent a release from being created. You can merge multiple PRs with this label, and then merge a PR without it to create a release from all of them at once.
-
-- **release/skip**: Skips the release process for the package(s) you changed
-
-**Scope**
-
-A scope is optional and consists of a noun describing a section of the codebase surrounded by parenthesis, e.g., feat(Button):
-
-**Breaking Changes**
-
-Using the **release/major** label will bump the major version number of the package(s) you changed, which indicates that your changes are not backwards compatible with previous versions of the package(s).
-
-This will indicate to package consumers that they need to refactor their usage of the module to upgrade.
-
 #### Breaking Changes Release Process
 
 Because client-modules is a separate repository from its consumers, it can be tricky to coordinate technically breaking changes.

auto.config.js

@@ -48,11 +48,6 @@
     "lerna": "3.22.1"
   },
   "devDependencies": {
-    "auto": "^11.1.6",
-    "@auto-it/all-contributors": "^11.0.4",
-    "@auto-it/first-time-contributor": "^11.0.4",
-    "@auto-it/npm": "^11.0.4",
-    "@auto-it/released": "^11.0.4",
     "@babel/cli": "7.13.10",
     "@babel/core": "7.19.6",
     "@babel/preset-typescript": "^7.13.0",

package.json

@@ -23,8 +23,8 @@
     "eslint": "^8.11.0"
   },
   "dependencies": {
-    "@typescript-eslint/eslint-plugin": "^8.31.1",
-    "@typescript-eslint/parser": "^8.31.1",
+    "@typescript-eslint/eslint-plugin": "^8.31.0",
+    "@typescript-eslint/parser": "^8.31.0",
     "eslint-config-prettier": "^10.1.2",
     "eslint-mdx": "^3.4.1",
     "eslint-plugin-import": "^2.31.0",