chore: pdate package versions and dependencies

[seeratawan01]

PR Type

enhancement

---

Description

• Enhanced the workflow to manually update the version field in package.json files for all packages.
• Introduced a loop to iterate over packages and update their versions.
• Added a step to reinstall dependencies, ensuring the lockfile is updated.

---

Changes walkthrough 📝

	Relevant files
Enhancement	cd-develop.yml Enhance package version update and dependency management  .github/workflows/cd-develop.yml Added manual update of version field in package.json files. Introduced a loop to update versions in all packages. Added a step to reinstall dependencies to update the lockfile. +12/-2

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🏅 Score: 82

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The script lacks error handling for the operations performed on package.json files, which could lead to silent failures in the workflow. Performance Issue Using sed in a loop for multiple files might be inefficient. Consider a method to batch process these files.

Code feedback:

---

relevant file	.github/workflows/cd-develop.yml
suggestion	Consider adding error handling or a check after updating the package.json files to ensure the operation was successful. This could prevent issues in the deployment process if the file update fails. [important]
relevant line	sed -i "s/\"version\": \".*\"/\"version\": \"$RC_VERSION\"/g" "$pkg/package.json"

---

relevant file	.github/workflows/cd-develop.yml
suggestion	Instead of using a loop with sed, consider using a single find command combined with sed to update all package.json files in one command. This could improve the performance of the script. [medium]
relevant line	for pkg in packages/*; do

---

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Improve the reliability of JSON manipulation by using jq Consider using a more robust method for updating JSON files, such as jq or a Node.js script, instead of using sed. This ensures proper JSON structure and avoids potential issues with regex matching. .github/workflows/cd-develop.yml [78] -sed -i "s/\"version\": \".*\"/\"version\": \"$RC_VERSION\"/g" "$pkg/package.json" +jq '.version = env.RC_VERSION' "$pkg/package.json" > tmp.$$.json && mv tmp.$$.json "$pkg/package.json" Suggestion importance[1-10]: 8 Why: Using jq for JSON manipulation is a more robust and reliable method than sed, as it ensures proper JSON structure and avoids potential issues with regex matching. This suggestion significantly improves the reliability of the code.	8
	Enhance the robustness of dependency installation by adding error handling Add error handling for the pnpm install command to ensure the workflow does not continue if the installation fails. .github/workflows/cd-develop.yml [86] -pnpm install --no-frozen-lockfile +pnpm install --no-frozen-lockfile || exit 1 Suggestion importance[1-10]: 7 Why: Adding error handling to the pnpm install command ensures that the workflow does not continue if the installation fails, which enhances the robustness and reliability of the CI/CD process.	7
Reliability	Add validation to ensure the version update was successful in each package.json Consider verifying the success of the version update in each package.json by checking the output of the sed command or by using a script to validate the update. .github/workflows/cd-develop.yml [78] -sed -i "s/\"version\": \".*\"/\"version\": \"$RC_VERSION\"/g" "$pkg/package.json" +sed -i "s/\"version\": \".*\"/\"version\": \"$RC_VERSION\"/g" "$pkg/package.json" && grep -q "\"version\": \"$RC_VERSION\"" "$pkg/package.json" || echo "Update failed for $pkg/package.json" Suggestion importance[1-10]: 7 Why: Adding validation to check if the version update was successful increases the reliability of the script by ensuring that changes are correctly applied, which is an important improvement for maintaining consistency.	7
Compatibility	Ensure compatibility of the sed command across different systems Ensure that the sed command is compatible with both GNU and BSD versions of sed by avoiding in-place editing without a backup extension. .github/workflows/cd-develop.yml [78] -sed -i "s/\"version\": \".*\"/\"version\": \"$RC_VERSION\"/g" "$pkg/package.json" +sed -i.bak "s/\"version\": \".*\"/\"version\": \"$RC_VERSION\"/g" "$pkg/package.json" && rm "$pkg/package.json.bak" Suggestion importance[1-10]: 6 Why: Ensuring compatibility with both GNU and BSD versions of sed by using a backup extension improves the portability of the script across different environments, which is a beneficial enhancement.	6