Lint: CI/CD: auto-publish npm package if push to main passes validation about lint HOT 2 CLOSED

Will stick to manual publishing because a release should manually be created prior to publish. It is not desirable to auto-publish on push because of lack of semantic versioning enforcement. Instead, publishing on release tied to a pull request is desired. There are benefits to using this PR auto release model, e.g. attestation that a package was published from the repo source, and stricter process guarantees around picking up a git tag : npm version : release triad, and the ability to gate releases behind test automation. That said, it's a lot of work and not a lot of immediate payoff for a personal project. Wontfixing this, but I'll likely implement the above whenever I feel like it.

from lint.

Revisiting this: Publish if passes validation:

1. Builds
2. Passes code test
3. Version greater than current published version

from lint.