Add character count in text area

.circleci/config.yml

@@ -269,6 +269,7 @@ jobs:
   jsdocs-deploy:
     docker:
       - image: node:8.10.0
+    working_directory: /home/circleci/build
     steps:
       - checkout
       - attach_workspace:
@@ -317,19 +318,53 @@ jobs:
             # Extract tag from CIRCLE_TAG environment variable
             TAG=${CIRCLE_TAG}
 
-            # Create the release using GitHub API
-            RESPONSE=$(curl -s -X POST \
-              -H "Authorization: token $GITHUB_TOKEN" \
-              -H "Content-Type: application/json" \
-              -d '{
-                "tag_name": "'"$TAG"'",
-                "name": "'"$TAG"'",
-                "body": "Release notes for version '"$TAG"'"
-              }' \
-              "https://api.github.com/repos/$CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME/releases")
+            # Maximum number of retries
+            MAX_RETRIES=3
+
+            # Function to create the release using GitHub API
+            create_release() {
+              local response
+              response=$(curl -s -X POST \
+                -H "Authorization: token $GITHUB_TOKEN" \
+                -H "Content-Type: application/json" \
+                -d '{
+                  "tag_name": "'"$TAG"'",
+                  "name": "'"$TAG"'",
+                  "body": "Release notes for version '"$TAG"'"
+                }' \
+                "https://api.github.com/repos/$CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME/releases")
+
+              echo "$response"
+            }
+
+            # Function to extract upload URL from GitHub API response
+            extract_upload_url() {
+              local response="$1"
+              echo "$response" | jq -r '.upload_url' | sed -e 's/{.*}//'
+            }
+
+            # Create the release with retries
+            for ((retry_count=1; retry_count<=MAX_RETRIES; retry_count++)); do
+              echo "Attempt $retry_count to create the release..."
+
+              RESPONSE=$(create_release)
+              echo "RESPONSE: $RESPONSE"
+              UPLOAD_URL=$(extract_upload_url "$RESPONSE")
+              echo "UPLOAD_URL: $UPLOAD_URL"
+
+              # Check if UPLOAD_URL is not null or empty
+              if [ -n "$UPLOAD_URL" ] && [ "$UPLOAD_URL" != "null" ]; then
+                echo "Release successfully created."
+                break  # Successful response, exit the loop
+              elif [ "$retry_count" -lt "$MAX_RETRIES" ]; then
+                echo "Failed to create release. Retrying..."
+                sleep 3  # Add a delay before the next attempt
+              else
+                echo "Error: Unable to create release after $MAX_RETRIES attempts."
+                exit 1
+              fi
+            done
 
-            # Get the upload URL from the response
-            UPLOAD_URL=$(echo "$RESPONSE" | jq -r '.upload_url' | sed -e 's/{.*}//')
 
             # Upload release artifacts
             for ARTIFACT in ./all/target/*.zip; do
@@ -350,28 +385,38 @@ jobs:
       - run:
           name: Update VERSIONS.md and README.md with the new released version
           command: |
+            # Echo Git version
+            echo "Git Version: $(git --version)"
+
+            # Echo Circle CI tag
             echo "CIRCLE_TAG: $CIRCLE_TAG"
-            RELEASE_BRANCH=$(git branch --contains ${CIRCLE_TAG} | awk 'FNR==2 {print $1}')
+            # Hardcoding the branch on master, since finding branch name with tag does not return correct output
+            RELEASE_BRANCH="master"
 
             # Debugging output
             echo "RELEASE_BRANCH: $RELEASE_BRANCH"
 
             # Checkout branch
             git checkout $RELEASE_BRANCH
 
+            # Fetch all branches and tags from the remote repository
+            git fetch --tags
+
             # Retrieve the branch name
             BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)
 
             # Debugging output
             echo "BRANCH_NAME: $BRANCH_NAME"
 
-            # Find the last two tags on the branch
-            LAST_TWO_TAGS=$(git tag -l --sort=-v:refname "core-forms-components-reactor-*" | head -n 2)
+            # Find the last tag on the branch, ignoring the private release
+            LAST_TAG=$(git tag -l --sort=-v:refname "core-forms-components-reactor-*" | grep -v -- '-[[:alnum:]]*$' | awk -v tag="$CIRCLE_TAG" '$0 < tag' | head -n 1)
+
             # Debugging output
-            echo "LAST_TWO_TAGS: $LAST_TWO_TAGS"
+            # echo "LAST_TWO_TAGS: $LAST_TWO_TAGS"
 
             # Extract the last released from the output
-            LAST_TAG=$(echo "$LAST_TWO_TAGS" | tail -n 1)
+            # LAST_TAG=$(echo "$LAST_TWO_TAGS" | tail -n 1)
+
             # Debugging output
             echo "LAST_TAG: $LAST_TAG"
 

.circleci/settings.xml

@@ -62,7 +62,7 @@
             </pluginRepositories>
         </profile>
         <profile>
-            <id>ossrh</id>
+            <id>central</id>
             <activation>
                 <activeByDefault>true</activeByDefault>
             </activation>

.cursor/mcp.json

@@ -0,0 +1,43 @@
+{
+  "mcpServers": {
+    "Corp Jira": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "--name",
+        "corp-jira-mthvu",
+        "--env-file",
+        "~/.easymcp/adobe-mcp-servers/src/corp-jira/.env",
+        "corp-jira"
+      ]
+    },
+    "Corp GitHub": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "--name",
+        "corp-github-nuwhz",
+        "--env-file",
+        "~/.easymcp/adobe-mcp-servers/src/corp-github/.env",
+        "corp-github"
+      ]
+    },
+    "PR Review MCP Server": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "--name",
+        "pr-review-mcp-server-kherg",
+        "--env-file",
+        "~/.easymcp/adobe-mcp-servers/src/pr-review-mcp/.env",
+        "pr-review-mcp-server"
+      ]
+    }
+  }
+}

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -14,6 +14,10 @@ about: Having an issue? Please create a report to explain what it is about.
 
 #### Platform and Version
 
+#### AEM Version (mention the exact version in case of cloud SDK)
+
+#### AEM Forms Version
+
 #### Sample Code that illustrates the problem
 
-#### Logs taken while reproducing problem
+#### Logs taken while reproducing problem

.github/workflows/sync-pr.yml

@@ -35,6 +35,7 @@ jobs:
           echo "::set-output name=base_ref::${{ github.event.pull_request.base.ref }}"
 
       - name: Sync with Base Branch
+        if: ${{ github.event.pull_request.base.ref != 'master' }}
         run: |
           git fetch origin ${{ steps.validate.outputs.head_ref }}
           git fetch origin ${{ steps.validate.outputs.base_ref }}

.gitignore

@@ -6,6 +6,8 @@
 .project
 .settings
 .DS_Store
+.codex/
+reasoning/
 
 # auto-generated clientlib
 ui.af.apps/src/main/content/jcr_root/apps/core/fd/af-clientlibs/core-forms-components-runtime-base/**
@@ -59,6 +61,8 @@ frontend-maven-plugin
 yarn-error.log
 .env
 .npmrc
+**/npm-debug.log
+
 
 # UI Tests
 node/

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Adobe Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at Grp-opensourceoffice@adobe.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/