ESLint config for TypeScript following Wikimedia code conventions - the idea is to make this repository here obsolete in the medium term and upstream these rules.
To make a new release:
-
Bump the version number in a pull request. (Edit
package.jsonmanually, then runnpm installto update the version number inpackage-lock.json.) The usual commit message is “Bump version to 1.2.3”. Example pull request. -
Get that pull request reviewed and merged.
-
Tag the merge commit locally. A “lightweight” tag is usually enough:
git pull, thengit tag v1.2.3. -
Push the tag.
git push origin v1.2.3 -
Turn it into a proper release on GitHub: draft a new release. Example release.
-
Once the GitHub release is published, it should be automatically published to NPM via GitHub Actions.
-
Submit a Gitlab change to
ci-tools/libup-configto update the version of the package inreleases.json(example).