@orderly.network/npm-release 0.0.2 → 0.0.3-alpha.0

package/README.md

@@ -19,10 +19,7 @@ pnpm add -D @orderly.network/npm-release
 ```json
 {
   "scripts": {
-    "release": "orderly-npm-release",
-    "release:patch": "RELEASE_VERSION_TYPE=patch orderly-npm-release",
-    "release:minor": "RELEASE_VERSION_TYPE=minor orderly-npm-release",
-    "release:major": "RELEASE_VERSION_TYPE=major orderly-npm-release"
+    "release": "orderly-npm-release"
   }
 }
 ```
@@ -37,12 +34,6 @@ pnpm add -D @orderly.network/npm-release
 | `GIT_USERNAME`         | Git username (used with token for authenticated remote URL)                           |
 | `GIT_NAME`             | Git `user.name` for commits                                                           |
 | `GIT_EMAIL`            | Git `user.email` for commits                                                          |
-| `GIT_COMMIT_MESSAGE`   | Optional custom commit message                                                        |
-| `RELEASE_VERSION_TYPE` | Bump type: `major`, `minor`, or `patch`                                               |
-| `CUSTOM_PRE_TAG`       | Pre-release identifier (e.g. `alpha`, `beta`); enables `--preRelease` and `--npm.tag` |
+| `RELEASE_VERSION_TYPE` | Bump type: `patch`, `minor`, or `major`                                               |
+| `PRERELEASE_TAG`       | Pre-release identifier (e.g. `alpha`, `beta`); enables `--preRelease` and `--npm.tag` |
 | `SLACK_WEBHOOK_URL`    | Webhook URL for success/failure Slack notifications                                   |
-
-## Prerequisites
-
-- Your project must have a `package.json` with a valid `version`.
-- For publishing to npm, configure `.release-it.json` in your project (or rely on defaults). This package ships a default [.release-it.json](.release-it.json) you can copy or merge.

package/index.mjs

@@ -12,16 +12,15 @@ const npm = {
 };
 
 const git = {
-  token: process.env.GIT_TOKEN,
-  username: process.env.GIT_USERNAME,
   name: process.env.GIT_NAME,
   email: process.env.GIT_EMAIL,
-  commitMessage: process.env.GIT_COMMIT_MESSAGE,
+  username: process.env.GIT_USERNAME,
+  token: process.env.GIT_TOKEN,
 };
 
-const customPreTag = process.env.CUSTOM_PRE_TAG;
+const preReleaseTag = process.env.PRERELEASE_TAG;
 
-// Custom release version type (major, minor, patch)
+// Custom release version type (patch, minor, major)
 const releaseVersionType = process.env.RELEASE_VERSION_TYPE;
 
 /** Inlined config (formerly .release-it.json) */
@@ -197,7 +196,7 @@ async function authNPM() {
 }
 
 /**
- * When current version is already a pre-release (e.g. 1.0.0-alpha.0) and CUSTOM_PRE_TAG
+ * When current version is already a pre-release (e.g. 1.0.0-alpha.0) and PRERELEASE_TAG
  * matches the same preId (e.g. "alpha"), use increment "prerelease" so release-it bumps
  * to 1.0.0-alpha.1. Otherwise use RELEASE_VERSION_TYPE (patch/minor/major).
  * Returns options for release-it programmatic API (merged with RELEASE_IT_CONFIG).
@@ -205,10 +204,10 @@ async function authNPM() {
 async function getReleaseItOptions() {
   let increment = releaseVersionType;
 
-  if (customPreTag) {
+  if (preReleaseTag) {
     const currentVersion = readPackageVersion();
     const { isPrerelease, preId } = parseVersion(currentVersion);
-    const normalizedPreTag = sanitizePreId(customPreTag);
+    const normalizedPreTag = sanitizePreId(preReleaseTag);
     // Continue pre-release: alpha.0 -> alpha.1 (same preId)
     if (isPrerelease && preId === normalizedPreTag) {
       increment = "prerelease";
@@ -220,9 +219,9 @@ async function getReleaseItOptions() {
     increment,
   };
 
-  if (customPreTag) {
-    options.preRelease = customPreTag;
-    options.npm.tag = customPreTag;
+  if (preReleaseTag) {
+    options.preRelease = preReleaseTag;
+    options.npm.tag = preReleaseTag;
   }
 
   return options;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orderly.network/npm-release",
-  "version": "0.0.2",
+  "version": "0.0.3-alpha.0",
   "main": "index.mjs",
   "module": "index.mjs",
   "license": "MIT",