chore: enrich package.json

[kentbull]

Bump version to 0.3.0-dev0 (latest code from today's main branch) and enrich the package.json with useful package metadata to support discovery via NPM.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.63%. Comparing base (f368351) to head (941a7e2).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #298   +/-   ##
=======================================
  Coverage   83.63%   83.63%           
=======================================
  Files          48       48           
  Lines        4235     4235           
  Branches     1055     1055           
=======================================
  Hits         3542     3542           
  Misses        663      663           
  Partials       30       30           

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

[2byrds]

lgtm

[lenkan]

If we want to do this, can you run npm install locally on your machine to ensure package-lock.json is updated with the new version?

Otherwise, the idea was that the version field on the main branch is the next minor/major version. Then you publish pre-releases from that by temporarily doing an in place edit in package.json before npm publish. That way, you can implement a workflow that publishes a pre-release on every commit to main, and every git tag. To elaborate:

• version: 0.3.0 on package.json on main.
• Commit with sha abc123 is pushed to main.
• Workflow triggers and publishes 0.3.0-abc123 to npm
• Commit with sha zyx123 is pushed to main.
• Workflow triggers and publishes 0.3.0-xyz123 to npm
• Repeat n number of times
• Maintainer decides to publish a beta tag:
  • Create git tag 0.3.0-dev.1
  • This triggers the workflow that publishes 0.3.0-dev.1 to npm
• Maintainer decides to publish 0.3.0:
  • Create git tag 0.3.0
  • This triggers the workflow that publishes 0.3.0 to npm
  • Create new commit on main that changes version: 0.4.0.
  • Any bug fixes to 0.3.x can be branched of from the 0.3.0 tag.

[lenkan]

I did some work on this before: #260 (comment)

However, the current NPM_DEPLOY_SECRET does not have sufficient rights to publish. I also have a simplified version of the workflow that allows you to do the same thing locally, but I never finished that work. If we can get a new working deploy secret, either for signify-ts or @weboftrust/signify package, I can pick it up again over the weekend.