chore: Update package versions

[seeratawan01]

PR Type

enhancement, configuration changes

---

Description

• Enhanced the CI/CD workflow to update package versions and dependencies more effectively.
• Replaced "workspace:*" with the actual version in all package.json files to ensure consistency.
• Changed the artifact paths from packages-dist to packages for better clarity and organization.
• Added a step to reinstall dependencies to ensure the lockfile is updated, improving dependency management.

---

Changes walkthrough 📝

	Relevant files
Enhancement	cd-develop.yml Enhance CI/CD workflow for package versioning and dependencies .github/workflows/cd-develop.yml Updated the job to increment package versions and dependencies. Replaced "workspace:*" with the actual version in all package.json files. Changed artifact paths from packages-dist to packages. Added a step to reinstall dependencies to update the lockfile. +28/-13

---

💡 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: 85

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Bug The sed command used to replace "workspace:*" with actual versions might not handle cases where the version string contains special characters that could be interpreted by sed, such as dots or dashes. Performance Issue Running 'pnpm install' after updating package versions might lead to redundant network requests if dependencies have not changed. Consider optimizing this step to check for actual changes in dependencies before reinstalling.

Code feedback:

---

relevant file	.github/workflows/cd-develop.yml
suggestion	Consider using a more robust approach for replacing versions in package.json files to handle special characters in version strings. For example, use a different delimiter in the sed command that does not conflict with version string characters. [important]
relevant line	find packages -name 'package.json' -print0 | xargs -0 sed -i "s/\"workspace:\*\"/\"$RC_VERSION\"/g"

---

relevant file	.github/workflows/cd-develop.yml
suggestion	To avoid unnecessary network requests, add a condition to check if the dependencies have actually changed before running 'pnpm install'. This can be done by comparing checksums of package.json files before and after the update. [medium]
relevant line	pnpm install

---

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	Improve the robustness of the version replacement in package.json files Ensure that the sed command used to replace "workspace:*" with the actual version in package.json files handles different variations of whitespace around the colon and asterisk to avoid missing replacements due to formatting differences. .github/workflows/cd-develop.yml [71] -find packages -name 'package.json' -print0 | xargs -0 sed -i "s/\"workspace:\*\"/\"$RC_VERSION\"/g" +find packages -name 'package.json' -print0 | xargs -0 sed -i "s/\"workspace:[[:space:]]*\*\"/\"$RC_VERSION\"/g" Suggestion importance[1-10]: 8 Why: The suggestion enhances the robustness of the sed command by accounting for variations in whitespace, which can prevent potential issues with version replacements in package.json files. This is a valuable improvement for ensuring consistent version updates across different formatting styles.	8
Best practice	Ensure dependency versions are locked during installation to prevent unintended upgrades Verify that the pnpm install command after updating package.json versions does not unintentionally upgrade unrelated dependencies, potentially leading to compatibility issues. .github/workflows/cd-develop.yml [74] -pnpm install +pnpm install --frozen-lockfile Suggestion importance[1-10]: 7 Why: Using --frozen-lockfile with pnpm install ensures that the lockfile is respected, preventing unintended upgrades of dependencies. This is a good practice to maintain consistency and avoid compatibility issues.	7
	Add verification to ensure successful version updates in package.json Consider adding error handling or a verification step after the sed command to ensure that the version replacement in package.json files was successful, especially since this operation is critical for the build process. .github/workflows/cd-develop.yml [71] -find packages -name 'package.json' -print0 | xargs -0 sed -i "s/\"workspace:\*\"/\"$RC_VERSION\"/g" +find packages -name 'package.json' -print0 | xargs -0 sed -i "s/\"workspace:\*\"/\"$RC_VERSION\"/g" && echo "Version replacement successful" || echo "Error in version replacement" Suggestion importance[1-10]: 6 Why: Adding a verification step after the sed command can help catch errors in the version replacement process, which is critical for the build process. This suggestion improves reliability but is not essential, hence a moderate score.	6
Possible issue	Verify and correct the artifact paths to ensure only necessary files are included Ensure that the artifact paths updated in the workflow match the expected directory structure and contents, especially since the path was changed from packages//dist to packages/. This change might include more files than intended or necessary. .github/workflows/cd-develop.yml [82] -path: packages/* +path: packages/*/dist Suggestion importance[1-10]: 5 Why: The suggestion to revert the artifact path to packages/*/dist is context-dependent. While it may prevent unnecessary files from being included, it requires verification against the intended changes in the PR. The suggestion is valid but needs careful consideration of the workflow's requirements.	5