Switch the two jobs around and add a dependency of server package on sql-parser

Author: ondrejromancov

.github/workflows/publish.yaml

@@ -6,8 +6,8 @@ on:
       - v**
 
 jobs:
-  publish-server:
-    name: Publish Server
+  publish-sql-parser:
+    name: Publish SQL Parser
     runs-on: ubuntu-latest
     steps: 
       - uses: actions/checkout@v3
@@ -24,7 +24,7 @@ jobs:
         run: | 
           GIT_TAG=${{  github.ref_name }}
           VERSION="${GIT_TAG#v}"
-          yarn workspace sql-language-server version --new-version ${VERSION} --no-git-tag-version
+          yarn workspace sql-parser version --new-version ${VERSION} --no-git-tag-version
 
       - run: yarn install
       - run: yarn npm:prepublish
@@ -33,22 +33,24 @@ jobs:
       # in the build script instead of renaming it in the package.json
       # because other packages depend on it and we want to keep the name the same for tests to pass.
       - name: Rename the package
-        run: npm pkg set name=@deepnote/sql-language-server --workspace packages/server
-        
+        run: npm pkg set name=@deepnote/sql-parser --workspace packages/sql-parser
+
       - name: Configure github packages npm repository
         run: | 
            echo "//npm.pkg.github.com/:_authToken=${{ secrets.GITHUB_TOKEN }}" > ~/.npmrc
            echo "@deepnote:registry=https://npm.pkg.github.com" >> ~/.npmrc
+           # We use `npm publish` instead of `yarn publish` because yarn publish
 
       # We use `npm publish` instead of `yarn publish` because yarn publish
       # checks if the repository is clean and fails if it's not. This is complicated for us, given we rename 
       # the package dynamically and we don't want to commit the changes to the package.json.
-      - name: Publish the server package
-        run: npm publish --workspace packages/server
+      - name: Publish the sql-parser package
+        run: npm publish --workspace packages/sql-parser
 
-  publish-sql-parser:
-    name: Publish SQL Parser
+  publish-server:
+    name: Publish Server
     runs-on: ubuntu-latest
+    needs: publish-sql-parser
     steps: 
       - uses: actions/checkout@v3
 
@@ -64,7 +66,7 @@ jobs:
         run: | 
           GIT_TAG=${{  github.ref_name }}
           VERSION="${GIT_TAG#v}"
-          yarn workspace sql-parser version --new-version ${VERSION} --no-git-tag-version
+          yarn workspace sql-language-server version --new-version ${VERSION} --no-git-tag-version
 
       - run: yarn install
       - run: yarn npm:prepublish
@@ -73,16 +75,15 @@ jobs:
       # in the build script instead of renaming it in the package.json
       # because other packages depend on it and we want to keep the name the same for tests to pass.
       - name: Rename the package
-        run: npm pkg set name=@deepnote/sql-parser --workspace packages/sql-parser
-
+        run: npm pkg set name=@deepnote/sql-language-server --workspace packages/server
+        
       - name: Configure github packages npm repository
         run: | 
            echo "//npm.pkg.github.com/:_authToken=${{ secrets.GITHUB_TOKEN }}" > ~/.npmrc
            echo "@deepnote:registry=https://npm.pkg.github.com" >> ~/.npmrc
-           # We use `npm publish` instead of `yarn publish` because yarn publish
 
       # We use `npm publish` instead of `yarn publish` because yarn publish
       # checks if the repository is clean and fails if it's not. This is complicated for us, given we rename 
       # the package dynamically and we don't want to commit the changes to the package.json.
-      - name: Publish the sql-parser package
-        run: npm publish --workspace packages/sql-parser
+      - name: Publish the server package
+        run: npm publish --workspace packages/server