feat: improve release process

Signed-off-by: Jan Pokorný <JenomPokorny@gmail.com>

Author: JanPokorny

.github/actions/setup/action.yml

@@ -4,17 +4,28 @@ description: 'Set up mise tools (Python, Node.js, ...) and install project depen
 runs:
   using: "composite"
   steps:
-    - uses: actions/cache@v4
+    - name: Cache uv .venv
+      uses: actions/cache@v4
       with:
-        path: .venv
-        key: uv-venv-v1-${{ runner.os }}-${{ hashFiles('uv.lock') }}
-        restore-keys: uv-venv-v1-${{ runner.os }}-
+        path: ${{ github.workspace }}/**/.venv
+        key: uv-venv-v2-${{ runner.os }}-${{ hashFiles('**/uv.lock') }}
+        restore-keys: uv-venv-v2-${{ runner.os }}-
 
-    - uses: actions/cache@v4
+    - name: Cache pnpm store
+      uses: actions/cache@v4
       with:
         path: ~/.local/share/pnpm/store
         key: pnpm-store-v1-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
         restore-keys: pnpm-store-v1-${{ runner.os }}-
+      
+    - name: Cache Next.js cache
+      uses: actions/cache@v4
+      with:
+        path: ${{ github.workspace }}/**/.next/cache
+        key: nextjs-cache-v1-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}-${{ hashFiles('**/*.js', '**/*.jsx', '**/*.ts', '**/*.tsx') }}
+        restore-keys: |
+          nextjs-cache-v1-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}-
+          nextjs-cache-v1-${{ runner.os }}-
     
     - name: Set environment variables
       shell: bash

CONTRIBUTING.md

@@ -250,9 +250,9 @@ mise x -- telepresence connect
 # Receive traffic to a pod by replacing it in the cluster
 mise x -- telepresence replace <pod-name>
 
-# More information about how replace/intercept/ingress works can be found in the [Telepresence documentation](https://telepresence.io/docs/howtos/engage).
+# More information about how replace/intercept/ingress works: https://telepresence.io/docs/howtos/engage
+
 # Once done, quit Telepresence using:
-```sh
 mise x -- telepresence quit
 ```
 
@@ -328,7 +328,7 @@ This would
 
 ### Step 2: QA & Polish the release on release branch
 
-You can then iteratively polish the release in `main` branch and cherry-pick the commits to `release`. When you are ready to create a new release candidate, run `mise run release:bump` to bump up the release candidate version.
+You can then iteratively polish the release in `main` branch and cherry-pick the commits to `release`. When you are ready to create a new release candidate, run `mise run release:publish-rc` to bump up the release candidate version.
 
 Creating new RC would trigger GH action to deploy pre-release version of the package for testing.
 
@@ -337,14 +337,13 @@ Creating new RC would trigger GH action to deploy pre-release version of the pac
 Once you've verified the RC version works, publish the final release from the `release` branch:
 
 ```shell
-git checkout release
-mise run release:publish
+mise run release:publish-rc
 ```
 
 This task will simply create a final tag for `release` version and push, which triggers GH action to deploy to pypi and npm.
 
 ## Documentation
 
-All changes that modify existing features or introduce new functionality must include documentation updates as part of the pull request. Documentation files should be added or updated in the `docs` folder.
+All changes that modify existing features or introduce new functionality must include documentation updates as part of the pull request. Documentation files should be added or updated in the `docs/development` folder.
 
 A GitHub workflow automatically checks that documentation requirements are met. If your change does not require documentation updates (e.g., bug fixes that don't change behavior, internal refactoring, or test-only changes), you must explicitly note this in your PR description.