fix: failing patch release bumper on missing package-lock.json

[jescalada]

Description

Related Issue

Resolves #

Checklist

General

• I have read the CONTRIBUTING.md guidelines
• Commit messages follow Conventional Commits format
• I have a FINOS CLA on file

Documentation

• Documentation has been added/updated for any new features

Configuration

• If configuration schema (config.schema.json) was modified:
  • TypeScript types regenerated (npm run generate-config-types)
  • Schema reference docs regenerated (npm run gen-schema-doc)

Tests

• Tests have been added/updated for new functionality
• Unit tests pass (npm test)
• Linting and formatting pass (npm run lint and npm run format:check)
• Type checks pass (npm run check-types)

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	ab23dec
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/6aa7f08751b7b00008b41a55

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.10%. Comparing base (bdcccc6) to head (ab23dec).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1730   +/-   ##
=======================================
  Coverage   86.10%   86.10%           
=======================================
  Files         101      101           
  Lines        5577     5577           
  Branches      996      996           
=======================================
  Hits         4802     4802           
  Misses        525      525           
  Partials      250      250           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kriswest]

LGTM, although co-pilot had a few suggestions you could apply:

1. Check version tag doesn't already exist

if git rev-parse "v$VERSION" >/dev/null 2>&1; then
  echo "::error::Version v$VERSION already exists"
  exit 1
fi

2. Verify files actually changed

git diff --quiet && {
  echo "::error::No version changes detected"
  exit 1
}

3. Validate lockfile integrity

npm install --package-lock-only
git diff --exit-code

For a FINOS/open-source release process, I'd consider the "version tag already exists" check the most important omission because it prevents accidentally generating a PR for a version that's already been released.