Skip to content

chore: restore next npm tag for prerelease versions #558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
B4nan merged 2 commits into from
Feb 17, 2026
Merged

chore: restore next npm tag for prerelease versions #558

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4febf2c
Initial plan
Copilot Feb 10, 2026
ece9d92
chore: change prerelease npm tag from beta to next
Copilot Feb 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/publish-to-npm.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ on:
default: latest
options:
- latest
- beta
- next

permissions:
id-token: write # Required for OIDC
Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/test-and-release.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,5 +130,5 @@ jobs:
inputs: >
{
"ref": "${{ github.sha }}",
"tag": "beta"
"tag": "next"
}
8 changes: 4 additions & 4 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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
Expand Down