fix npm ci

[rubenmarcus]

PR Type

bug fix, enhancement

---

Description

• Added npm install command before npm ci in the CI workflow to ensure package-lock.json is in sync.

---

Changes walkthrough 📝

	Relevant files
Enhancement	branch-publish.yml Add npm install step in CI workflow                                            .github/workflows/branch-publish.yml Added npm install command before npm ci to ensure package-lock.json is in sync. +1/-0

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[mintbase-codium-pr-agent]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[mintbase-codium-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Replace npm install with npm ci to ensure consistent dependency versions in CI environments Replace npm install with npm ci to ensure that the installation respects the exact versions defined in package-lock.json, which is more suitable for CI/CD environments to maintain consistency across installations. .github/workflows/branch-publish.yml [33] -npm install # Ensure package-lock.json is in sync +npm ci # Use npm ci to install exact versions from package-lock.json Suggestion importance[1-10]: 10 Why: The suggestion to replace npm install with npm ci is valid and improves the consistency of dependency installations in CI/CD environments, which is crucial for maintaining reliability across different builds.	10