Trigger publish on creation of a branch

[alexluckett]

Proposed change

Trigger publish on creation of a branch, rather than waiting for a push. Since major versions may commonly arrive, we might end up with 2.x.x, 3.x.x, 4.x.x never having their initial release published.

Type of change

• Bug fix
• New feature
• Breaking change
• Misc. (documentation, build updates, etc)

Checklist

• You have executed this code locally and it performs as expected.
• You have added tests to verify your code works.
• You have added code comments and JSDoc, where appropriate.
• There is no commented-out code.
• You have added developer docs in README.md and docs/* (where appropriate, e.g. new features).
• The tests are passing (npm run test).
• The linting checks are passing (npm run lint).
• The code has been formatted (npm run format).

[alexluckett]

Oops. This created 2.1.3 before it was merged....

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud