Skip to content

Commit 7296df3

Browse files
committed
update contrib and use npm key
1 parent 5a194e0 commit 7296df3

File tree

2 files changed

+10
-7
lines changed

2 files changed

+10
-7
lines changed

.github/workflows/experimental-release.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,8 +52,8 @@ jobs:
5252
run: npm run compile
5353

5454
- name: Publish experimental packages
55-
# env:
56-
# NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
55+
env:
56+
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
5757
run: |
5858
git diff
5959

CONTRIBUTING.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -234,9 +234,12 @@ Create a new branch from **main**, then find the hash of the commit you want to
234234
Create a patch-level changeset for the revert and open a PR with it.
235235
Merge the PR and cut a release according to the [Release flow](#release-flow).
236236

237-
### Experimental release
237+
### Experimental release flow
238238

239-
To release an experimental version to the NPM registry, create a new branch from **main**, then add the `experimental` label to the PR.
240-
This creates a new PR with the `experimental` branch as the source.
241-
Merging this PR triggers an experimental package release to the NPM registry.
242-
You can install it with `npm install @redocly/cli@experimental`.
239+
To release an experimental version to the **NPM** registry, follow these steps:
240+
241+
1. Create a new PR to **main**.
242+
2. Add the `experimental` label to the PR. This creates a new PR with to the `experimental` branch (which is a copy of the `main` branch).
243+
3. Merging the second PR triggers release to the **NPM** registry under the `experimental` tag.
244+
245+
The released version can be installed with `npm install @redocly/cli@experimental`.

0 commit comments

Comments
 (0)