Description
The test-plugin-examples CI workflow is failing during the dependency synchronization check. The dependencies-sync.js script detects that the dependencies in plugins/headlamp-plugin/package.json do not match the dependencies in frontend/package.json, causing the CI job to exit with an error.
Error Message
Some frontend/package.json dependencies changed. Please run "npm run update-dependencies" to sync dependencies from frontend/.
Error: Process completed with exit code 1.
Steps to Reproduce
1.Add new dependencies (such as @emnapi/core or @emnapi/runtime) to frontend/package.json.
2.Commit the changes without running the plugin sync script.
3.Push to GitHub and wait for the CI to run.
4.Observe the test-plugin-examples workflow fail during the Check Dependencies step.
Expected Behavior
The plugins/headlamp-plugin/package.json should automatically track and stay in sync with required frontend dependencies so that plugin developers have access to the exact same package versions used in the core frontend. The CI check should pass cleanly.
Actual Behavior
Because the dependencies were updated in the frontend but not synced to the plugin package, the dependencies-sync.js script catches the mismatch and intentionally fails the build to prevent out-of-sync packages from being published.
Proposed Solution
Run the update script to sync the packages and regenerate the lockfile:
1.Navigate to the plugin directory: cd plugins/headlamp-plugin
2.Run the sync command: npm run update-dependencies
3.Commit the resulting changes to plugins/headlamp-plugin/package.json and plugins/headlamp-plugin/package-lock.json.
Description
The
test-plugin-examplesCI workflow is failing during the dependency synchronization check. Thedependencies-sync.jsscript detects that the dependencies inplugins/headlamp-plugin/package.jsondo not match the dependencies infrontend/package.json, causing the CI job to exit with an error.Error Message
Steps to Reproduce
1.Add new dependencies (such as @emnapi/core or @emnapi/runtime) to frontend/package.json.
2.Commit the changes without running the plugin sync script.
3.Push to GitHub and wait for the CI to run.
4.Observe the test-plugin-examples workflow fail during the Check Dependencies step.
Expected Behavior
The plugins/headlamp-plugin/package.json should automatically track and stay in sync with required frontend dependencies so that plugin developers have access to the exact same package versions used in the core frontend. The CI check should pass cleanly.
Actual Behavior
Because the dependencies were updated in the frontend but not synced to the plugin package, the dependencies-sync.js script catches the mismatch and intentionally fails the build to prevent out-of-sync packages from being published.
Proposed Solution
Run the update script to sync the packages and regenerate the lockfile:
1.Navigate to the plugin directory: cd plugins/headlamp-plugin
2.Run the sync command: npm run update-dependencies
3.Commit the resulting changes to plugins/headlamp-plugin/package.json and plugins/headlamp-plugin/package-lock.json.