feat: fix the release flow and upgrade the docusaurus to the latest version

.github/CODEOWNERS

@@ -1,6 +1,6 @@
 # These owners will be the default owners for everything in
 # the repo. Unless a later match takes precedence
-* @petevielhaber 
+* @petevielhaber @yshyn-iohk @amagyar-iohk @bvoiturier @lohanspies @mkbreuningIOHK @Dale-iohk @elribonazo @essbante-io
 
 # Docs:
 *.md @petevielhaber

.github/workflows/mega-linter.yml

@@ -0,0 +1,85 @@
+---
+# MegaLinter GitHub Action configuration file
+# More info at https://megalinter.io
+name: MegaLinter
+
+on:
+  pull_request:
+    branches: [ main, feature/*, feat/*, docs/*, ci/*, bug/*, fix/* ]
+
+env: # Comment env block if you don't want to apply fixes
+  # Apply linter fixes configuration
+  APPLY_FIXES: all # When active, APPLY_FIXES must also be defined as environment variable (in github/workflows/mega-linter.yml or other CI tool)
+  APPLY_FIXES_EVENT: pull_request # Decide which event triggers application of fixes in a commit or a PR (pull_request, push, all)
+  APPLY_FIXES_MODE: pull_request # If APPLY_FIXES is used, defines if the fixes are directly committed (commit) or posted in a PR (pull_request)
+
+concurrency:
+  group: ${{ github.ref }}-${{ github.workflow }}
+  cancel-in-progress: true
+
+jobs:
+  megalinter:
+    name: MegaLinter
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      issues: write
+      pull-requests: write
+    steps:
+      # Git Checkout
+      - name: Checkout Code
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          fetch-depth: 0 # If you use VALIDATE_ALL_CODEBASE = true, you can remove this line to improve performances
+
+      - name: MegaLinter
+        id: ml
+        uses: oxsecurity/megalinter@v7
+        env:
+          # All available variables are described in documentation
+          # https://megalinter.io/configuration/
+          VALIDATE_ALL_CODEBASE: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }} # Validates all source when push on main, else just the git diff with main. Override with true if you always want to lint all sources
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      # Upload MegaLinter artifacts
+      - name: Archive production artifacts
+        if: success() || failure()
+        uses: actions/upload-artifact@v4
+        with:
+          name: MegaLinter reports
+          path: |
+            megalinter-reports
+            mega-linter.log
+
+      - uses: crazy-max/ghaction-import-gpg@v3
+        if: failure() && steps.ml.outputs.has_updated_sources == 1
+        id: import_gpg
+        with:
+          gpg_private_key: ${{ secrets.HYP_BOT_GPG_PRIVATE }}
+          passphrase: ${{ secrets.HYP_BOT_GPG_PASSWORD }}
+          git_user_signingkey: true
+          git_commit_gpgsign: true
+          git_config_global: true
+          git_tag_gpgsign: false
+
+      # Create pull request if applicable (for now works only on PR from same repository, not from forks)
+      - name: Create Pull Request with applied fixes
+        id: cpr
+        if: steps.ml.outputs.has_updated_sources == 1 && (env.APPLY_FIXES_EVENT == 'all' || env.APPLY_FIXES_EVENT == github.event_name) && env.APPLY_FIXES_MODE == 'pull_request' && (github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository) && !contains(github.event.head_commit.message, 'skip fix')
+        uses: peter-evans/create-pull-request@v6
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          base: ${{ github.head_ref }}
+          branch-suffix: short-commit-hash
+          commit-message: "style: apply linters automatic fixes"
+          title: "style: apply linters automatic fixes"
+          signoff: true
+          committer: "Hyperledger Bot <hyperledger-bot@hyperledger.org>"
+          author: "Hyperledger Bot <hyperledger-bot@hyperledger.org>"
+
+      - name: Create PR output
+        if: steps.ml.outputs.has_updated_sources == 1 && (env.APPLY_FIXES_EVENT == 'all' || env.APPLY_FIXES_EVENT == github.event_name) && env.APPLY_FIXES_MODE == 'pull_request' && (github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository) && !contains(github.event.head_commit.message, 'skip fix')
+        run: |
+          echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}"
+          echo "Pull Request URL - ${{ steps.cpr.outputs.pull-request-url }}"

.github/workflows/release.yml

@@ -3,6 +3,11 @@ name: Release docs image
 on:
   workflow_call:
   workflow_dispatch:
+    inputs:
+      release-branch:
+        description: "Branch to release from"
+        required: false
+        default: "main"
 
 jobs:
   release:
@@ -17,7 +22,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           submodules: recursive
-          token: ${{ secrets.IDENTUS_CI }}
+          token: ${{ secrets.GITHUB_TOKEN }}
           ref: ${{ github.event.inputs.release-branch }}
           fetch-depth: 0
 
@@ -26,15 +31,15 @@ jobs:
         with:
           node-version: 16
 
-      - uses: crazy-max/ghaction-import-gpg@v5
+      - uses: crazy-max/ghaction-import-gpg@v6
         id: import_gpg
         with:
           gpg_private_key: ${{ secrets.HYP_BOT_GPG_PRIVATE }}
           passphrase: ${{ secrets.HYP_BOT_GPG_PASSWORD }}
           git_user_signingkey: true
           git_commit_gpgsign: true
           git_config_global: true
-          git_tag_gpgsign: true
+          git_tag_gpgsign: false
 
       - name: Login to GitHub Container Registry
         uses: docker/login-action@v2
@@ -49,6 +54,12 @@ jobs:
           npm install -g log4brains
           log4brains build --out ../static/adrs --basePath /adrs
           touch ../static/adrs/.nojekyll
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "lts/*"
+
       - name: Release
         env:
           GIT_AUTHOR_EMAIL: ${{ steps.import_gpg.outputs.email }}

.mega-linter.yml

@@ -0,0 +1,61 @@
+# MegaLinter configuration for Docusaurus
+
+ENABLE:
+  - JAVASCRIPT_ES
+  - TYPESCRIPT_ES
+  - MARKDOWN_MARKDOWNLINT
+  - YAML_YAMLLINT
+  - JSON_JSONLINT
+  - HTML_HTMLHINT
+
+FILE_EXTENSIONS:
+  - js
+  - jsx
+  - ts
+  - tsx
+  - md
+  - yml
+  - yaml
+  - json
+  - html
+
+DIRECTORY_INCLUDE:
+  #  - src TODO: consider to uncomment this line later
+  - infra
+  - documentation
+
+DIRECTORY_EXCLUDE:
+  - node_modules
+  - static
+  - identus-cloud-agent
+  - identus-edge-agent-ts
+  - .docusaurus
+  - src
+
+MARKDOWN_MARKDOWNLINT:
+  config: .markdownlint.json
+
+YAML_YAMLLINT:
+  config: .yamllint
+
+JSON_JSONLINT:
+  config: .jsonlintrc
+
+HTML_HTMLHINT:
+  config: .htmlhintrc
+
+JAVASCRIPT_ES:
+  config: .eslintrc.js
+  prettier: true
+
+TYPESCRIPT_ES:
+  config: .eslintrc.js
+  prettier: true
+
+REPORT_OUTPUTS:
+  - json
+  - html
+  - markdown
+
+DISABLE_LINTERS_ERRORS_REPORT: false
+LINTERS_CLI_OPTIONS: '--fix'

documentation/docs/identus/cloud-agent/authentication.md

@@ -201,7 +201,9 @@ and the `KEYCLOAK_ROLES_CLAIM_PATH` should be set to `resource_access.<KEYCLOAK_
 
 The current authorization logic is built on the UMA specification, configuring permissions as user A controls resource W. In this model, user A is a registered user in Keycloak, and wallet W is a resource registered in Keycloak.
 
-These configurations are managed manually in Keycloak. However, for a better experience, the Agent can execute these actions through the REST API endpoint. For each wallet, a corresponding resource gets created with the name wallet-{wallet_id} in Keycloak. Similarly, a corresponding policy is created for each user and resource with the name user {userId} on wallet {wallet_resource_name} permission.
+These configurations are managed manually in Keycloak. However, for a better experience, the Agent can execute these actions through the REST API endpoint. 
+For each wallet, a corresponding resource gets created with the name wallet-`wallet_id` in Keycloak. 
+Similarly, a corresponding policy is created for each user and resource with the name user `userId` on wallet `wallet_resource_name` permission.
 
 The REST API endpoint to configure permissions in Keycloak is:
 

documentation/docs/quick-start.md

@@ -401,7 +401,7 @@ Follow the steps in your desired platform as stated below:
 
 The below code examples show how to establish mediation when building your own application.
 
-<details><summary>Code examples</summary>
+<summary>Code examples</summary>
 3. The following code examples represent establishing mediation and instantiating the Cloud Agent.
 
 <Tabs>
@@ -487,9 +487,6 @@ agent.startFetchingMessages()
 
 </TabItem>
 </Tabs>
-</details>
-
-
 
 ## Establish Holder connections
 To connect the Holder to both Cloud Agent instances, you must run this in both Issuer and Verifier endpoints.
@@ -556,7 +553,7 @@ curl --location \
 </TabItem>
 </Tabs>
 
-<details><summary>Code examples</summary>
+<summary>Code examples</summary>
 <Tabs>
 <TabItem value="js" label="Typescript">
 
@@ -583,7 +580,6 @@ agent.acceptOutOfBandInvitation(invitation)
 
 </TabItem>
 </Tabs>
-</details>
 
 ## Issue a Credential from the Issuer to the holder
 
@@ -649,7 +645,7 @@ automaticIssuance is optional. It can also be manually triggered and confirmed b
 </Tabs>
 
 
-<details><summary>Code examples</summary>
+<summary>Code examples</summary>
 
 5. The exchange between CredentialOffer and CredentialRequest is demonstrated through more advanced code samples below, showcasing how different platforms handle it.
 
@@ -731,7 +727,6 @@ agent.handleReceivedMessagesEvents().collect { list ->
 
 </TabItem>
 </Tabs>
-</details>
 
 ### Store the Issued Credential [Holder]
 :::caution
@@ -740,7 +735,7 @@ The sample application are using an insecure storage solution which should only
 
 :::
 
-<details><summary>Code examples</summary>
+<summary>Code examples</summary>
 6. Once the Holder receives a credential from the Cloud Agent, it needs to store the credential somewhere:
 
 <Tabs>
@@ -807,7 +802,6 @@ agent.handleReceivedMessagesEvents().collect { list ->
 
 </TabItem>
 </Tabs>
-</details>
 
 ## Request a verification from the Verifier Cloud Agent to the Holder (JWT W3C Credential)
 Now that the Holder has received a credential, it can be used in a verification workflow between a Holder and a Verifier. This requires the following steps:
@@ -857,7 +851,7 @@ curl --location \
 
 6. The Holder needs an Edge Agent running with the message listener active. It will receive the presentation proof request from the Verifier Cloud Agent for the correct type of messages as detailed below:
 
-<details><summary>Code examples</summary>
+<summary>Code examples</summary>
 
 <Tabs>
 <TabItem value="js" label="Typescript">
@@ -945,8 +939,6 @@ agent.handleReceivedMessagesEvents().collect { list ->
 </TabItem>
 
 </Tabs>
-</details>
-
 
 ### Verifier: Will then check on the API if the Presentation Request has been completed or not.
 

docusaurus.config.js

@@ -1,8 +1,8 @@
 // @ts-check
 // Note: type annotations allow type checking and IDEs autocompletion
 
-const lightCodeTheme = require('prism-react-renderer/themes/github');
-const darkCodeTheme = require('prism-react-renderer/themes/dracula');
+import {themes as prismThemes} from 'prism-react-renderer';
+
 const path = require('path')
 // const {useColorMode} = require('@docusaurus/theme-common');
 // const {colorMode} = useColorMode()
@@ -164,8 +164,8 @@ const config = {
                 copyright: `© ${new Date().getFullYear()} Identus. All rights reserved.`,
             },
             prism: {
-                theme: lightCodeTheme,
-                darkTheme: darkCodeTheme,
+                theme: prismThemes.github,
+                darkTheme: prismThemes.dracula,
             },
 
         },