@cmflow/cli 2.3.1 → 3.0.0

package/README.md

@@ -331,16 +331,12 @@ Note: Jira versions are expected to follow `<COMPONENT>-<version>` or similar. F
 ### Detailed behavior
 1. Fetch all Jira versions for the project (`projectId`).
 2. Keep those whose version (after stripping `component-`, `version-`, and `v` prefixes) is semver <= the provided `--tag`.
-3. For each selected version, fetch related issues and prepare a delivery note by type:
-   - `Story` → `feat`
-   - `Sous-tâche` → `tech`
-   - `Tâche` → `chore`
-   - `Bug` → `fix`
-4. Print the delivery note to stdout (example below).
-5. If `--update` is provided:
+3. Print the delivery note to stdout (example below).
+4. If `--update` is provided:
    - Mark the relevant version(s) as `released=true` with `releaseDate=YYYY-MM-DD` (today's date).
-   - Move each related issue to the Jira state `id=18`, `name="Livré en production"` (transition errors are logged but won't stop the whole process).
-6. If the Directus config is complete, trigger the workflow by passing the list of `version` values for the processed releases.
+5. If the Directus config is complete, trigger the workflow by passing the list of `version` values for the processed releases.
+
+> Important: moving issue isn't supported from the cmflow. You have to create a jira automation script to move the issue on your board.
 
 ### Example
 
@@ -365,23 +361,6 @@ Raw CLI example:
 cm jira-releases --project-id CMAB --component API --tag v0.3241.3 --update
 ```
 
-### Example of generated note
-The console output includes a share-ready message (note: the tool prints the message in French by default):
-
-```text
-Hello,
-We will deploy to production version <TAG> of the <COMPONENT>
-Here is what this delivery includes:
-
-- v<version>:
- - feat(CMAB-123): Story title
- - fix(CMAB-456): XYZ fix
-
-The API team
-```
-
-The exact structure may vary depending on how many versions are included and which issues are associated.
-
 ### Best practices
 - Use a valid semver `--tag` (the `v`/`version-` prefixes are accepted).
 - Ensure your Jira versions follow a consistent schema that includes the component (`<COMPONENT>-<version>`) to allow matching.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cmflow/cli",
-  "version": "2.3.1",
+  "version": "3.0.0",
   "description": "An awesome Git Flow",
   "author": "camfou",
   "license": "MIT",

package/src/commands/jira-releases.js

@@ -3,28 +3,10 @@ import figures from "figures";
 import moment from "moment";
 
 import { triggerDirectusFlow } from "../common/back/directus/directus-flow.js";
-import { jiraGetReleasesAndIssues } from "../common/back/jira/jira-get-releases-and-issues.js";
-import { jiraIssueMoveTo } from "../common/back/jira/jira-issue-move-to.js";
+import { getSortedReleases } from "../common/back/jira/get-sorted-releases.js";
 import { updateJiraRelease } from "../common/back/jira/jira-releases.js";
 import { getConfig } from "../common/index.js";
 
-const TYPES = {
-  Story: "feat",
-  "Sous-tâche": "tech",
-  Tâche: "chore",
-  Bug: "fix"
-};
-
-function getSummary(issue) {
-  return issue.fields.summary
-    .replace("CLONE -", "")
-    .replace("[FEAT]", "")
-    .replace(/\[(.*)]:/, "$1 -")
-    .replace("[BUG]", "")
-    .replace("[FIX]", "")
-    .trim();
-}
-
 export class JiraReleases {
   mapContext(commander, context) {
     return {
@@ -46,7 +28,7 @@ export class JiraReleases {
       {
         title: `List all releases under ${context.tag} for ${context.component} component and ${context.projectId} project`,
         task: async () => {
-          context.releases = await jiraGetReleasesAndIssues(context.projectId, context.component, context.tag);
+          context.releases = await getSortedReleases(context.projectId, context.component, context.tag);
         }
       },
       {
@@ -58,17 +40,6 @@ export class JiraReleases {
             release.releaseDate = moment().format("YYYY-MM-DD");
 
             await updateJiraRelease(release);
-
-            await Promise.all(
-              release.issues.map((issue) => {
-                return jiraIssueMoveTo(issue, {
-                  id: "18",
-                  name: "Livré en production"
-                }).catch((er) => {
-                  console.error(chalk.red(figures.cross), `Error moving issue ${issue.key} to production: ${er.message}`);
-                });
-              })
-            );
           }
         }
       },
@@ -86,32 +57,4 @@ export class JiraReleases {
       }
     ];
   }
-
-  success(context) {
-    console.log(chalk.green(figures.tick), "Release notes generated successfully");
-    console.log("\n");
-
-    const note = `Bonjour,
-Nous allons livrer en production la version ${context.tag} de l'${context.component}
-Au menu de cette livraison :
-
-${context.releases
-  .filter(Boolean)
-  .reverse()
-  .map((release) => {
-    const issues =
-      release.issues?.map((issue) => {
-        return ` - ${TYPES[issue.fields.issuetype.name] || issue.fields.issuetype.name}(${issue.key}): ${getSummary(issue)}`;
-      }) || [];
-
-    return issues.length ? (context.releases.length > 1 ? "- v" + release.version + ":\n" : "") + issues.join(",\n") : false;
-  })
-  .filter((line) => line !== false)
-  .join("\n\n")}
-
-L'Equipe API
-    `;
-
-    console.log(note);
-  }
 }

package/src/common/back/jira/{jira-get-releases-and-issues.js → get-sorted-releases.js}

@@ -1,6 +1,6 @@
 import semver from "semver";
 
-import { getJiraReleases, getJiraVersionRelatedIssues } from "./jira-releases.js";
+import { getJiraReleases } from "./jira-releases.js";
 
 /**
  * Returns all releases under the tag version for the given project and component.
@@ -8,7 +8,7 @@ import { getJiraReleases, getJiraVersionRelatedIssues } from "./jira-releases.js
  * @param component {string}
  * @param tagVersion {string}
  */
-export async function jiraGetReleasesAndIssues(projectId, component, tagVersion) {
+export async function getSortedReleases(projectId, component, tagVersion) {
   const releases = await getJiraReleases(projectId);
 
   const promises = releases
@@ -25,11 +25,6 @@ export async function jiraGetReleasesAndIssues(projectId, component, tagVersion)
     })
     .sort((ra, rb) => {
       return semver.rcompare(ra.version, rb.version);
-    })
-    .map(async (release) => {
-      const { issues } = await getJiraVersionRelatedIssues(projectId, release.name);
-      release.issues = issues;
-      return release;
     });
 
   const [current, ...others] = await Promise.all(promises);

package/src/common/back/jira/jira-issue-move-to.js

@@ -1,38 +0,0 @@
-import { jiraRequest } from "./jira-request.js";
-
-/**
- * Moves a JIRA issue to the correct state using the specified transition.
- * @param issue
- * @param toTransition
- * @return {Promise<void>}
- */
-export async function jiraIssueMoveTo(issue, toTransition) {
-  /**
-   * {
-   *       transitions: {
-   *         id: string;
-   *         name: string;
-   *         to: { id: string; name: string };
-   *       }[];
-   *     }
-   */
-  const { transitions } = await jiraRequest(`/rest/api/3/issue/${issue.key}/transitions`);
-  const transition = transitions.find((transition) => {
-    return transition.id === toTransition.id;
-  });
-
-  if (transition) {
-    await jiraRequest(`/rest/api/3/issue/${issue.key}/transitions`, {
-      method: "post",
-      headers: {
-        "Content-Type": "application/json",
-        Accept: "application/json"
-      },
-      body: {
-        transition: {
-          id: transition.id
-        }
-      }
-    });
-  }
-}