[Bug]: Auto Changelog & Versioned Docs is falling when triggred

[utkarsh232005]

Bug Description

This error is showing while running the action
Run VERSION="v1.2.2" /home/runner/work/_temp/2a0482e7-544d-4fd6-b1bb-2bbb927e553d.sh: line 12: ${#template_items[@]}: bad substitution Error: Process completed with exit code 1.

Steps to Reproduce

when retrigger the action it will fall

Expected Behavior

Should be able to generate new changelog based on released patch

Actual Behavior

Fall into errors

Environment

ubuntu linux

[github-actions]

🤖 Hi @utkarsh232005, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[github-actions]

🤖 I'm sorry @utkarsh232005, but I was unable to process your request. Please see the logs for more details.

[utkarsh232005]

@CodeRabbit plan

[coderabbitai]

Coding Plan

Summary

• Single-line fix targeting the exact syntax error reported in the workflow failure
• The fix corrects a bash array length expression that has backticks erroneously inserted around the #template_items variable name
• Once corrected, the workflow will properly evaluate whether template files exist and copy them to versioned docs directories as intended

Implementation Steps

Fix Bash Array Syntax Error

This phase addresses the root cause of the workflow failure by correcting the malformed bash array length check that contains erroneous backticks.

Correct Array Length Syntax in Workflow Script

Fix the invalid bash syntax causing the "bad substitution" error at runtime.

• Update .github/workflows/changelog.yml line 59 to remove the erroneous backticks from the array length expression
• The current malformed syntax ${`#template_items`[@]} must be corrected to the valid bash array length syntax ${#template_items[@]}
• This is the conditional check that determines whether template files exist to copy; fixing it allows the template copying logic to execute properly instead of always falling through to the fallback mkdir path

🤖 Prompt for AI agents

Fix a single-line bash syntax error in `.github/workflows/changelog.yml` at line
59 that is causing a "bad substitution" runtime failure.

- Locate line 59 in `.github/workflows/changelog.yml`
- Find the malformed array length expression `` ${`#template_items`[@]} `` which
contains erroneous backticks around `#template_items`
- Replace it with the correct bash array length syntax `${`#template_items`[@]}`,
removing the backticks entirely
- This fix restores the conditional check that determines whether template files
exist to copy, allowing the template copying logic to execute properly instead
of always falling through to the fallback `mkdir` path

Research

The repository uses GitHub Actions for CI/CD automation, with .github/workflows/changelog.yml handling automatic changelog generation and versioned documentation scaffolding on release events. The workflow uses mikepenz/release-changelog-builder-action for changelog generation and a bash script to copy template files from .github/docs-template/ into versioned docs/ directories. The workflow runs on ubuntu-latest with bash as the default shell.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Fix a single-line bash syntax error in `.github/workflows/changelog.yml` at line
59 that is causing a "bad substitution" runtime failure.

- Locate line 59 in `.github/workflows/changelog.yml`
- Find the malformed array length expression `` ${`#template_items`[@]} `` which
contains erroneous backticks around `#template_items`
- Replace it with the correct bash array length syntax `${`#template_items`[@]}`,
removing the backticks entirely
- This fix restores the conditional check that determines whether template files
exist to copy, allowing the template copying logic to execute properly instead
of always falling through to the fallback `mkdir` path

💡 Iterate on the plan with: `@coderabbitai` <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!