Migrate to 🦋 changesets

[iiroj]

This PR is for random cleanup targeted at preparing to switch to 🦋 changesets, by:

• add lint-staged version, node version and platform to debug logs
• install commitlint for linting commit messages according to the conventional commits specification
  • for pull requests, validate all commit messages in CI
• adjusting the current semantic-release job to use conventionalcommits instead of default angular
• limit the security analysis CI jobs to run only on master (or PR targeting master)
• extract the npm ci CI step into its own separate job with caching

...and finally:

• replace semantic-release with changesets

[codecov]

Codecov Report

Patch has no changes to coverable lines.

📢 Thoughts on this report? Let us know!.

[iiroj]

Ping @okonet you might want to install the Changesets bot to this repo: https://github.com/apps/changeset-bot

[iiroj]

I'll copy a similar implementation to one of my own repos to make sure it works as expected.

[iiroj]

Had to tweak it more than expected, but got it working here: https://github.com/iiroj/iiro.fi

• this PR implemented 🦋 changesets with an empty changeset file: https://github.com/iiroj/iiro.fi/pull/17/files
• this PR added a minor changeset: docs(release): add changeset iiroj/iiro.fi#18
• and finally this was the automatic version bump PR: 🦋 Changeset release iiroj/iiro.fi#20
• this is the created GitHub release/tag: https://github.com/iiroj/iiro.fi/releases/tag/v30.2.0

I mostly had to tweak the version commands to get the package-lock.json file updated, and to only create a single commit. The trick was to commit manually:

https://github.com/iiroj/iiro.fi/blob/0b69b1010e3119183dfc7ad4d23e27037dc450c6/package.json#L17-L18

    "version": "npx changeset version",
    "postversion": "npm i --package-lock-only && git commit -am \"chore(changeset): release\"",

and run npm run version in the CI.

[iiroj]

I generated the CHANGELOG.md file because going forward it will be committed to the repo during 🦋 changeset versioning. I used this tool and tweaked manually: https://github.com/rhysd/changelog-from-release

[iiroj]

Ping @okonet it would be nice to test dropping Node.js 16 support using changesets. It goes EOL in two days, on September 11th 2023: https://nodejs.dev/en/about/releases/

[okonet]

Sure let’s give it a go. What’s required from my end? Approval or do I need to test it somehow?

[iiroj]

I tested and synced this config with the https://github.com/iiroj/iiro.fi repo, so after this PR is merged, versioning should happen via 🦋 changesets. Since this PR has an empty changeset file, no automatic version PR should be opened.

After I create a new PR for the Node.js 16 deprecation with a changeset file, we should see some new functionality.

So, should I just merge this?