Dominik Picheta

Problem: #head installations go stale

1

 Click to expand! ```bash dom@DESKTOP-AAP3EIS:/mnt/c/Users/morfe/projects/httpbeast$ nimble install hottie@\#head Downloading https://github.com/treeform/hottie using git Verifying dependencies for hottie@#head Info: Dependency on cligen@>= 1.3.2 already satisfied Verifying dependencies for cligen@#head Info: Dependency...

the ca certs requirements break it on macos.

Fatal on windows when Nimble clones to dir ending with dot

7

``` Installing stb_image@>= 2. Downloading https://gitlab.com/define-private-public/stb_image-Nim.git using git Tip: 66 messages have been suppressed, use --verbose to show them. Error: Execution failed with exit code 128 ... Command: git clone...

Locking of dependencies

36

When you build your package a nimble.lock file should be created. This nimble.lock file should contain some metadata about the package as well as the dependencies which your package has...

> https://forum.nim-lang.org/t/7067 The publish command is broken for some, we should add a fallback like: go to this URL and edit the packages.json file. Maybe we can even directly link...

Scoped packages by default

2

I believe this was already requested by some people. The more I think about it the more I believe I should enforce it. Here is npm's description of what scoped...

Difficult to verify that `develop` dep is being used

1

``Verifying dependencies for [email protected]`` is misleading as it doesn't even mention ``@#head``.

Implement `tag` command

22

Usage: ``nimble tag v0.1.1`` Nimble will run ``git tag v0.1.1`` (or equivalent) and verify that the package's .nimble file has been updated with that version. Bonus feature: * Enforce semantic...

Hoping this version has the CVE fixed.

Update CI to new Nim when it's released

1

(We don't build with old anymore because of reasons)