You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
echo "::warning file=package.json,line=1::Version v$package_version already exists - no release will be created. If you want to create a new release, please update the version in package.json and push again."
26
-
echo "skipped=true" >> $GITHUB_OUTPUT
33
+
if [[ -n "$gh_exists" || -n "$npm_exists" ]]; then
Copy file name to clipboardExpand all lines: README.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,6 +145,25 @@ Run the CLI in development mode:
145
145
./bin/dev
146
146
```
147
147
148
+
## Publishing
149
+
150
+
Automatic publishing is handled by the `version, tag and github release` workflow. A new npm version is published whenever a version bump is merged into the `main` branch. The workflow can also be triggered manually from the **Actions** tab.
151
+
152
+
To enable publishing, set the following repository secrets:
153
+
154
+
-`NPM_TOKEN` – authentication token for npm.
155
+
-`GH_EMAIL` and `GH_USERNAME` – used by the README update step.
156
+
157
+
Once the secrets are configured, pushing a new version or running the workflow manually will build the project, create a GitHub release and publish the package to npm.
158
+
159
+
### Linting workflows
160
+
161
+
Before committing changes to workflows, you can lint them locally:
0 commit comments