You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ npm run release
> [email protected] release
> bumpp && npm publish
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
i No commits since the last version
✔ Current version 1.0.0-beta.0 › next 1.0.0-beta.1
files package-lock.json
package.json
commit chore: release v1.0.0-beta.1
tag v1.0.0-beta.1
push yes
from 1.0.0-beta.0
to 1.0.0-beta.1
✔ Bump? … yes
✔ Updated package-lock.json to 1.0.0-beta.1
✔ Updated package.json to 1.0.0-beta.1
Process exited with non-zero status (128)
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Suggested solution
Add support using jj binary, just like it is done for git.
Alternative
Don't support jj, leave that to a fork. jj can't create git tags yet and it is still indev so commands may change, so jj support may be a noticeable maintenance burden.
Additional context
Currently I have resorted to using this command to publish new releases:
cd (mktemp -d) && git clone <url> . && npm install && npm run release &&rm-rf (pwd)
Clear and concise description of the problem
See: https://jj-vcs.github.io/, https://github.com/jj-vcs/jj?tab=readme-ov-file#readme
Current behaviour:
Suggested solution
Add support using
jj
binary, just like it is done forgit
.Alternative
Don't support
jj
, leave that to a fork.jj
can't create git tags yet and it is still indev so commands may change, so jj support may be a noticeable maintenance burden.Additional context
Currently I have resorted to using this command to publish new releases:
Validations
The text was updated successfully, but these errors were encountered: