diff --git a/.github/workflows/publish-to-npm.yaml b/.github/workflows/publish-to-npm.yaml
index b1eee5e8c1..167c85f5bd 100644
--- a/.github/workflows/publish-to-npm.yaml
+++ b/.github/workflows/publish-to-npm.yaml
@@ -14,7 +14,7 @@ on:
                 default: latest
                 options:
                     - latest
-                    - beta
+                    - next
 
 permissions:
     id-token: write # Required for OIDC
@@ -49,8 +49,8 @@ jobs:
             - name: Build module
               run: npm run build
 
-            - name: Check version consistency and bump pre-release version (beta only)
-              if: ${{ inputs.tag == 'beta' }}
+            - name: Check version consistency and bump pre-release version (next only)
+              if: ${{ inputs.tag == 'next' }}
               run: node ./.github/scripts/before-beta-release.js
 
             - name: Publish to NPM
diff --git a/.github/workflows/test-and-release.yaml b/.github/workflows/test-and-release.yaml
index 787b2b0029..2f9ce3cbf5 100644
--- a/.github/workflows/test-and-release.yaml
+++ b/.github/workflows/test-and-release.yaml
@@ -130,5 +130,5 @@ jobs:
                   inputs: >
                       {
                           "ref": "${{ github.sha }}",
-                          "tag": "beta"
+                          "tag": "next"
                       }
diff --git a/RELEASE.md b/RELEASE.md
index b436f46643..7393c46a0a 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -7,11 +7,11 @@ After creating a release there, Actions will automatically produce a latest vers
 ## TLDR;
 
 - To **NOT** release anything on a push to `master`, add `[skip ci]` to your commit message.
-- To release `beta`, just push to `master`. If it breaks with a `Version already exists error` increment version
+- To release `next`, just push to `master`. If it breaks with a `Version already exists error` increment version
   in `package.json` and push again.
 - To release `latest`, go to releases on GitHub, draft and publish a release. If you don't know how, read below.
 
-## Prerelease (beta) versions
+## Prerelease (next) versions
 
 On each push to the `master` branch, a new prerelease version is automatically built and published
 by GitHub Actions. To skip the process, add `[skip ci]` to your commit message.
@@ -23,8 +23,8 @@ by GitHub Actions. To skip the process, add `[skip ci]` to your commit message.
 3. If all is well, a new prerelease version is published to NPM (`${VERSION}-beta.${COUNTER}`),
    where `VERSION` is the version in package.json and `COUNTER` is a zero based index of existing prereleases.
    Example: `0.15.1-beta.3`.
-4. The package is tagged with the `beta` NPM tag and a Git tag is associated with the triggering commit.
-5. A build of Apify docker images is triggered that updates the `beta` packages to use the newly published package.
+4. The package is tagged with the `next` NPM tag and a Git tag is associated with the triggering commit.
+5. A build of Apify docker images is triggered that updates the `next` packages to use the newly published package.
 6. All done and ready to use.
 
 ### Updating a release version