Collection of development scripts/tools for Eove applications.

git clone git@github.com:eove/eo-dev-tools.git
cd eo-dev-tools.git
nix develop
npm install

Display help:

npm start -- --help

npx @eove/dev-tools --help

• get-changelog-from-file: get a changelog from a file
• get-changelog-from-git: get a changelog based on commits between two revisions
• get-closed-issues: get a changelog from a file
• get-version: get project version
• get-latest-release: get the latest GitHub release
• validate-issue: validate issue
• cpu-project start-release: release a cpu project
• cpu-project finalize-release: finalize a cpu project release

Get the changelog for provided version:

npx @eove/dev-tools get-changelog-from-file --file ./CHANGELOG.md 1.3.4

When latest is used and changelog is not empty, the first changes will be returned.

When provided version uses a v prefix (v1.2.3), it will be automatically omitted (1.2.3 will be used).

When provided version is a prerelease (1.2.3-dev.1), this exact version will be looked for, then the release one ( 1.2.3).

Get the changelog for provided repository between 2 git revisions:

GITHUB_TOKEN=<your_token> npx @eove/dev-tools get-changelog-from-git --base 1b19f3e --head f2f790a --repo eo70-cpu-software

Get all closed issues for provided repository between 2 git revisions:

GITHUB_TOKEN=<your_token> npx @eove/dev-tools get-closed-issues --base 1b19f3e --head f2f790a --repo eo70-cpu-software

Get versions from the found package.json files:

npx @eove/dev-tools get-version --root ~/sources/myproject

Validate issue:

GITHUB_TOKEN=<your_token> npx @eove/dev-tools validate-issue --repository eo70-cpu-software 1008

To plan a eo70-cpu-software release:

GITHUB_TOKEN=<your_token> npx @eove/dev-tools cpu-project plan-release \
  --project-directory ~/Sources/eove/eo70-cpu-software \
  --cpu-version C070000002 \
  --cpu-extra-version rc.30

To apply previously planned eo70-cpu-software release:

GITHUB_TOKEN=<your_token> npx @eove/dev-tools cpu-project apply-release \
  --project-directory ~/Sources/eove/eo70-cpu-software \
  '{ the whole plan json}'

This command is run on CI.

Package is published in Eove private npm registry hosted by Github.

Just use npm version.

A commit/tag will be created and pushed on github then artifact will be published on private registry.

For instance:

• npm version 1.2.0: to create this specific version
• npm version major: to increase major version part

MIT