release 0.1.2; apply 'npm pkg fix' changes required by provenance generation #161
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-on from #159
The release attempt failed to 'npm publish' in https://github.com/elastic/elastic-otel-node/actions/runs/8899712600/job/24439813707
... because provenance generation is apparently very picky about package.json changes, and the automatic 'npm pkg fix' during 'npm publish' broke that.