chore(release): Upgrade version

Author: javierbrea

.github/CONTRIBUTING.md

@@ -43,11 +43,14 @@ $ docker compose build
 $ docker compose run action
 ```
 
+> [!CAUTION]
+> The Docker image won't work in some systems due to the usage of Chromium, as in MacOS with M1 processors. In this case, you can [run the Node.js code instead](#test-the-nodejs-code-locally).
+
 You can provide a `.env` file to set environment variables used by the GitHub Actions Toolkit. For more information, see the example file, [`.env.example`](./.env.example), and the
 [GitHub Actions Documentation](https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables).
 
 > [!IMPORTANT]
-> The action will search for configuration file and dependencies in the `/github/workspace` directory. The root workspace directory is mounted as a volume in the container in that folder. You can set another directory to be checked by setting the `INPUT_CWD` environment variable to the desired directory (e.g. `INPUT_CWD=test-action`).
+> The root workspace directory is mounted as a volume in the container in the `/github/workspace` folder. You can set another workspace subdirectory for testing the synchronization locally by setting the `INPUT_CWD` environment variable to the desired directory (e.g. `INPUT_CWD=test-action`).
 
 ### Test the Node.js code locally
 

CHANGELOG.md

@@ -11,6 +11,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 #### Deprecated
 #### Removed
 
+## [2.0.0] - 2025-03-18
+
+### Changed
+
+* feat(BREAKING CHANGE): Throw an error in case the `cwd` input is absolute, because the action only has access to the repository files
+* chore: Use Docker action instead of Node.js action in order to install Chromium and Puppeteer
+* chore: Use Pnpm instead of NPM
+* chore: Move `dependencies` to `devDependencies`, because in runtime the action uses only the bundled code, and it installs the mermaid dependencies by itself in the Docker image. This is because the `@tid-xcut` libraries are in a private repository, and the action cannot install them in the Docker image. Some fixes are applied to the bundled code to make it work in the Docker image.
+
+### Fixed
+
+* fix: Generate mermaid diagrams in the Confluence page
+
+### Added
+
+* docs: Add automation notice to Confluence pages containing the action docs
+* test: Add mermaid diagram to readme.md file, and test that it has been synced to Confluence in E2E tests
+
+
 ## [1.2.0] - 2025-03-13
 
 ### Changed

README.md

@@ -63,7 +63,7 @@ docs/
 
 ```yaml
 - name: Sync markdown files to Confluence
-  uses: Telefonica/markdown-confluence-sync-action@v1
+  uses: Telefonica/markdown-confluence-sync-action@v2
   with:
     mode: tree
     docs-dir: './docs'
@@ -89,7 +89,7 @@ For example:
 
 ```yaml
 - name: Sync markdown files to Confluence
-  uses: Telefonica/markdown-confluence-sync-action@v1
+  uses: Telefonica/markdown-confluence-sync-action@v2
   with:
     mode: id
     docs-dir: '.'
@@ -132,7 +132,7 @@ confluence_page_id: 123456789
 
 ```yaml
 - name: Sync markdown files to Confluence
-  uses: Telefonica/markdown-confluence-sync-action@v1
+  uses: Telefonica/markdown-confluence-sync-action@v2
   with:
     mode: flat
     docs-dir: './docs'
@@ -187,7 +187,7 @@ The action accepts a configuration file in the root of the repository, and it ca
 | `confluence-notice-template` | Template string to use for the notice message | No | |
 | `confluence-dry-run` | Dry run mode: Do not update Confluence pages. Only log pages to sync | No | `false `|
 | `log-level` | Log level: `silent`, `silly`, `debug`, `verbose`, `info`, `warn`, `error` | No | `info` |
-| `cwd` | Current working directory. Path from where resolve `docs-dir`, `files-pattern`, and search for the configuration file | No | `.` |
+| `cwd` | Current working directory. Path from where resolve `docs-dir`, `files-pattern`, and search for the configuration file. It must be relative to the repository folder | No | `.` |
 
 > [!NOTE]
 > Some markdown-confluence-sync options are not available as inputs in the action, as `preprocessor`. If you need to use them, you can set them in the [configuration file](#configuration-file) or using [environment variables](#environment-variables). Refer to the [Markdown Confluence Sync library docs](https://github.com/Telefonica/cross-confluence-tools/tree/main/components/markdown-confluence-sync#configuration-file) for further info about all available options.

dist/index.js

@@ -1,7 +1,7 @@
 {
   "name": "markdown-confluence-sync-action",
   "description": "GitHub Action to sync markdown files to Confluence",
-  "version": "1.2.0",
+  "version": "2.0.0",
   "author": "Telefónica Innovación Digital",
   "homepage": "https://github.com/Telefonica/markdown-confluence-sync-action",
   "repository": {

dist/index.js.map

@@ -6,8 +6,8 @@ import { MarkdownConfluenceSync } from "@tid-xcut/markdown-confluence-sync";
 import { parse } from "yaml";
 import { join, isAbsolute } from "path";
 
+// NOTE: Change this value to a relative path to the repository root to test the node.js code locally, such as "test-action". Docs and configuration should be placed there.
 const BASE_CWD = "/github/workspace";
-// const BASE_CWD = "test-action";
 
 function valueIfDefined<T = string>(value: T | undefined): T | undefined {
   return value === "" ? undefined : value;