next-ver

next-ver copied to clipboard

I renamed master branch to main and it stopped working: GitHub Actions output: ``` Run yarn next-ver --go yarn run v1.22.18 $ /home/runner/work/magic/magic/node_modules/.bin/next-ver --go /home/runner/work/magic/magic/node_modules/q/q.js:87[6](https://github.com/Frank-Mayer/magic/runs/6032304461?check_suite_focus=true#step:7:6) throw error; ^ fatal: couldn't...

tsukinoko-kun

Bumps [minimist](https://github.com/substack/minimist) from 1.2.0 to 1.2.5. Commits aeb3e27 1.2.5 278677b 1.2.4 4cf1354 security notice 1043d21 additional test for constructor prototype pollution 6457d74 1.2.3 38a4d1c even more aggressive checks for protocol...

dependabot[bot]

So I can do the same thing that `next-ver --go` does using NPM module

bahmutov

on Node 8 ``` (node:64547) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead. ```

bahmutov

https://github.com/bahmutov/new-public-commits

bahmutov

If there is npm "build" script run it after updating the version

1

Maybe should define "preversion" script to point at the build?

bahmutov

Probably combination of Bash shell and API calls from unit tests

bahmutov