Fix release workflow version detection

[koszti]

Description

The release-and-publish github action is currently failing on the main branch when attempting to detect a version change, producing the following error:

Error: Can't find version field

To fix this, we need to update the configuration as follows:

• Add file-name: ./precise/package.json so the action looks for package.json in the correct directory. Setting a job-level working-directory is not sufficient for this action.
• Add diff-search: true : By default, the action only checks commit messages. If the version is bumped in package.json without explicitly mentioning it in the commit message, the release is not detected.

Additional context and related issues

These changes were tested independently in a forked repository

[mosabua]

Awesome.. I noticed the failure too but did not get around to investigating. Thanks!

[koszti]

@mosabua worfklow in main branch now looks just fine:

Searching for version update...
Searching in 1 commit...
  Package file name: "precise/package.json"
  Package file URL: undefined
  Version assumptions: undefined
No standard npm version commit found, switching to diff search (this could take more time...)
Checking the diffs of 1 commit...
  - 1ceb733: no changes to the package file
No matching commit found.
Outputs:
  changed: false

next time when we merge a version bump commit to main it should generate release notes, create release in GH and publish to npm. let’s see how it goes

[mosabua]

Yeah.. if I get around to it I might cut another release tonight