Merge branch 'layer5io:master' into master

Author: SAHU-01

.github/workflows/cloud-release-docs.yml

@@ -0,0 +1,50 @@
+name: Publish Meshery Cloud Version Dispatcher
+on:   
+  workflow_dispatch:
+
+jobs:
+  release_notes_docs_cloud_latest:
+    name: Release notes cloud with latest version
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.RELEASEDRAFTER_PAT }}
+          repository: layer5io/docs
+      - name: Get Latest Meshery Cloud Release
+        id: meshery-cloud
+        env:
+          ACCESS_TOKEN: ${{ secrets.RELEASEDRAFTER_PAT }}
+        run: |
+          release_tag=$(curl -sL -H "Authorization: token $ACCESS_TOKEN" -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/layer5io/meshery-cloud/releases/latest | jq -r ".tag_name")
+          echo "release_tag=$release_tag" >> $GITHUB_OUTPUT
+          current_tag=$(<build/meshery-cloud.version)
+          echo "current_tag=$current_tag" >> $GITHUB_OUTPUT
+      - name: Get Release Info
+        if: steps.meshery-cloud.outputs.current_tag != steps.meshery-cloud.outputs.release_tag
+        env:
+          ACCESS_TOKEN: ${{ secrets.RELEASEDRAFTER_PAT }}
+        run: |
+          curl -sL -H "Authorization: token $ACCESS_TOKEN" -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/layer5io/meshery-cloud/releases/latest > latest_release.json
+          
+          export RELEASE_TAG=$( cat latest_release.json | jq '.["tag_name"]' | tr -d '"')
+          export PRERELEASE=$( cat latest_release.json | jq '.["prerelease"]' | tr -d '"')
+          export RELEASE_BODY=$( cat latest_release.json | jq '.["body"]' | tr -d '"')
+          export DATE=$( cat latest_release.json | jq '.["published_at"]' | tr -d '"')
+          printf '%b\n' "---\ntitle: $RELEASE_TAG\ndate: $DATE\ntag: $RELEASE_TAG\nprerelease: $PRERELEASE\n---\n\n$RELEASE_BODY" > ./content/en/cloud/reference/releases/$RELEASE_TAG.md
+      - name: Update current release version
+        if: steps.meshery-cloud.outputs.current_tag != steps.meshery-cloud.outputs.release_tag
+        run: |
+            echo ${{ steps.meshery-cloud.outputs.release_tag }} > build/meshery-cloud.version
+      - name: Commit changes
+        if: steps.meshery-cloud.outputs.current_tag != steps.meshery-cloud.outputs.release_tag
+        uses: stefanzweifel/git-auto-commit-action@v5
+        with:
+          commit_message: "Release Notes Meshery Cloud version ${{ steps.meshery-cloud.outputs.release_tag }}"
+          branch: master
+          commit_options: "--signoff"
+          file_pattern: 'build/meshery-cloud.version ./content/en/cloud/reference/releases/${{ steps.meshery-cloud.outputs.release_tag }}.md'
+          commit_user_name: l5io
+          commit_user_email: [email protected]
+          commit_author: ${{ github.actor }} <${{ github.actor }}@users.noreply.github.com>

.github/workflows/meshery-extension-release-docs.yml

@@ -0,0 +1,50 @@
+name: Publish Meshery Extensions Version Dispatcher
+on:   
+  workflow_dispatch:
+
+jobs:
+  release_notes_docs_meshery_extensions_latest:
+    name: Release notes meshery extensions with latest version
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.RELEASEDRAFTER_PAT }}
+          repository: layer5io/docs
+      - name: Get Latest Meshery Extensions Release
+        id: meshery-extensions
+        env:
+          ACCESS_TOKEN: ${{ secrets.RELEASEDRAFTER_PAT }}
+        run: |
+          release_tag=$(curl -sL -H "Authorization: token $ACCESS_TOKEN" -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/layer5labs/meshery-extensions-packages/releases/latest | jq -r ".tag_name")
+          echo "release_tag=$release_tag" >> $GITHUB_OUTPUT
+          current_tag=$(<build/meshery-extensions.version)
+          echo "current_tag=$current_tag" >> $GITHUB_OUTPUT
+      - name: Get Release Info
+        if: steps.meshery-extensions.outputs.current_tag != steps.meshery-extensions.outputs.release_tag
+        env:
+          ACCESS_TOKEN: ${{ secrets.RELEASEDRAFTER_PAT }}
+        run: |
+          curl -sL -H "Authorization: token $ACCESS_TOKEN" -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/layer5labs/meshery-extensions-packages/releases/latest > latest_release.json
+          
+          export RELEASE_TAG=$( cat latest_release.json | jq '.["tag_name"]' | tr -d '"')
+          export PRERELEASE=$( cat latest_release.json | jq '.["prerelease"]' | tr -d '"')
+          export RELEASE_BODY=$( cat latest_release.json | jq '.["body"]' | tr -d '"')
+          export DATE=$( cat latest_release.json | jq '.["published_at"]' | tr -d '"')
+          printf '%b\n' "---\ntitle: $RELEASE_TAG\ndate: $DATE\ntag: $RELEASE_TAG\nprerelease: $PRERELEASE\n---\n\n$RELEASE_BODY" > ./content/en/kanvas/reference/releases/$RELEASE_TAG.md
+      - name: Update current release version
+        if: steps.meshery-extensions.outputs.current_tag != steps.meshery-extensions.outputs.release_tag
+        run: |
+            echo ${{ steps.meshery-extensions.outputs.release_tag }} > build/meshery-extensions.version
+      - name: Commit changes
+        if: steps.meshery-extensions.outputs.current_tag != steps.meshery-extensions.outputs.release_tag
+        uses: stefanzweifel/git-auto-commit-action@v5
+        with:
+          commit_message: "Release Notes Meshery Extension version ${{ steps.meshery-extensions.outputs.release_tag }}"
+          branch: master
+          commit_options: "--signoff"
+          file_pattern: 'build/meshery-extensions.version ./content/en/kanvas/reference/releases/${{ steps.meshery-extensions.outputs.release_tag }}.md'
+          commit_user_name: l5io
+          commit_user_email: [email protected]
+          commit_author: ${{ github.actor }} <${{ github.actor }}@users.noreply.github.com>

CONTRIBUTING-gitflow.md

@@ -91,5 +91,59 @@ git rebase -i master
 ```
 This will open up a text editor where you can specify which commits to squash.
 
+## Instructions on How to Sign Off Commits to Meet the Developer Certificate of Origin (DCO) Requirements
+
+Contributors to this project are required to sign off on their commits to comply with the Developer Certificate of Origin (DCO). The DCO is a simple statement that you, as the contributor, have the legal right to make the contribution.
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file.
+
+(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me.
+
+(c) The contribution was provided directly to me by some other person who certified (a), (b) and I have not modified it.
+
+(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
+
+**How to Sign Off on Your Commits**
+
+To add the required sign-off to your commits, follow these steps:
+
+1. Ensure Git is Configured with Your Name and Email
+
+    Your Git configuration must have your correct name and email address, as they will be used to generate the sign-off message. To configure Git, run the following commands:
+```
+git config --global user.name "Your Name"
+git config --global user.email "[email protected]"
+```
+2. Use the -s or --signoff Option in Your Commit
+
+    When making a commit, you must use the -s or --signoff option to add the sign-off line. This will append the following line to your commit message:
+```
+Signed-off-by: Your Name <[email protected]>
+```
+Example of a signed-off commit:
+```
+git commit -s -m "Fixing issue with Meshery module"
+```
+
+This ensures that your contribution complies with the DCO.
+
+3. Verify Your Sign-Off
+
+    To verify that your commit has the sign-off, you can inspect your commit log:
+```
+git log -1
+```
+The last commit should contain a Signed-off-by line that matches your name and email.
+
+4. Amending a Commit Without Sign-Off
+
+    If you've already made a commit but forgot to sign off, you can amend the commit with the sign-off using the following command:
+```
+git commit --amend --signoff
+```
+This will add the sign-off to your previous commit.
+
 ## Submitting
 Once you've committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes on your development branch and update.

README.md

@@ -1,4 +1,4 @@
-# Layer5 Product Documentation
+![image](https://github.com/user-attachments/assets/926e71c4-4f1b-4188-8540-6f951c173710)# Layer5 Product Documentation
 
 Explore tutorials and documentation by product in the docs.layer5.io website; documentation and developer resources of Layer5 products.
 
@@ -197,15 +197,15 @@ Find out more on the <a href="https://layer5.io/community">Layer5 community</a>.
   <img alt="Shows an illustrated light mode meshery logo in light color mode and a dark mode meshery logo dark color mode." src=".github/readme/images//slack-128.png" width="110px" align="right" style="margin-left:10px;padding-top:13px;">
 </picture>
 </a>
-
-<a href="https://meshery.io/community"><img alt="Layer5 Community" src=".github/readme/images//community.svg" style="margin-right:8px;padding-top:5px;" width="140px" align="left" /></a>
-
+<div class="flex">
+<a href="https://meshery.io/community"><img alt="Layer5 Community" src=".github/readme/images//community.svg" style="margin-right:8px;padding-top:9px;" width="140px" align="left" /></a>
 <p>
 ✔️ <em><strong>Join</strong></em> any or all of the weekly meetings on <a href="https://calendar.google.com/calendar/b/1?cid=bGF5ZXI1LmlvX2VoMmFhOWRwZjFnNDBlbHZvYzc2MmpucGhzQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20">community calendar</a>.<br />
 ✔️ <em><strong>Watch</strong></em> community <a href="https://www.youtube.com/playlist?list=PL3A-A6hPO2IMPPqVjuzgqNU5xwnFFn3n0">meeting recordings</a>.<br />
 ✔️ <em><strong>Access</strong></em> the <a href="https://drive.google.com/drive/u/4/folders/0ABH8aabN4WAKUk9PVA">Community Drive</a> by completing a community <a href="https://layer5.io/newcomer">Member Form</a>.<br />
 ✔️ <em><strong>Discuss</strong></em> in the <a href="https://discuss.layer5.io">Community Forum</a>.<br />
-✔️<em><strong>Explore more</strong></em> in the <a href="https://layer5.io/community/handbook">Community Handbook</a>.<br />
+✔️ <em><strong>Explore more</strong></em> in the <a href="https://layer5.io/community/handbook">Community Handbook</a>.<br />
 </p>
+</div>
 <p align="center">
 <i>Not sure where to start?</i> Grab an open issue with the <a href="https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+org%3Alayer5io+org%3Ameshery+org%3Aservice-mesh-performance+org%3Aservice-mesh-patterns+label%3A%22help+wanted%22+">help-wanted label</a>.</p>

build/meshery-cloud.version

@@ -0,0 +1 @@
+v0.8.34

build/meshery-extensions.version

@@ -0,0 +1 @@
+v0.7.124-1

content/en/cloud/reference/releases/v0.8.20.md

@@ -0,0 +1,22 @@
+---
+title: v0.8.20
+date: 2024-10-01T22:37:11Z
+tag: v0.8.20
+prerelease: false
+---
+
+## What's New
+**General**
+- Bump @rjsf/validator-ajv8 from 5.18.1 to 5.21.1 in /ui @dependabot (#2800)
+- Upgrade meshmap snapshot version @Aijeyomah (#2809)
+- Add robots.txt and sitmap-0.xml to router.go @leecalcote (#2799)
+- Bump @mui/x-date-pickers from 7.11.1 to 7.18.0 in /ui @dependabot (#2801)
+- Bump @fontsource/roboto from 5.0.8 to 5.1.0 in /ui @dependabot (#2802)
+- Bump husky from 4.3.8 to 9.1.6 in /ui @dependabot (#2803)
+- convert reusable autocomplete components to rtk fetching @sudhanshutech (#2810)
+
+## Contributors
+
+Thank you to our contributors for making this release possible:
+@Aijeyomah, @MUzairS15, @dependabot, @dependabot[bot], @l5io, @leecalcote and @sudhanshutech
+

content/en/cloud/reference/releases/v0.8.21.md

@@ -0,0 +1,16 @@
+---
+title: v0.8.21
+date: 2024-10-02T11:42:59Z
+tag: v0.8.21
+prerelease: false
+---
+
+## What's New
+**General**
+- Fixes @MUzairS15 (#2811)
+
+## Contributors
+
+Thank you to our contributors for making this release possible:
+@MUzairS15 and @l5io
+

content/en/cloud/reference/releases/v0.8.22.md

@@ -0,0 +1,18 @@
+---
+title: v0.8.22
+date: 2024-10-04T03:54:26Z
+tag: v0.8.22
+prerelease: false
+---
+
+## What's New
+**General**
+- [Chore] Update MeshMap references in Plans page @jameshorton2337 (#2813)
+- Bump github.com/meshery/schemas from 0.7.31 to 0.7.35 @dependabot (#2805)
+- [User Flows] Do not archive/delete user  record after migration. @MUzairS15 (#2814)
+
+## Contributors
+
+Thank you to our contributors for making this release possible:
+@MUzairS15, @dependabot, @jameshorton2337, @l5io and @leecalcote
+

content/en/cloud/reference/releases/v0.8.23.md

@@ -0,0 +1,19 @@
+---
+title: v0.8.23
+date: 2024-10-05T11:00:41Z
+tag: v0.8.23
+prerelease: false
+---
+
+## What's New
+**General**
+- Support inter domain issue of sessions @MUzairS15 (#2816)
+- Bump golang.org/x/oauth2 from 0.22.0 to 0.23.0 @dependabot (#2806)
+- Bump github.com/layer5io/meshkit from 0.7.73 to 0.7.78 @dependabot (#2807)
+- add function to create missing singup event @MUzairS15 (#2812)
+
+## Contributors
+
+Thank you to our contributors for making this release possible:
+@MUzairS15, @dependabot, @l5io and @leecalcote
+