Skip to content
#

versioning

Here are 919 public repositories matching this topic...

jo-kerr
jo-kerr commented Sep 11, 2020

Describe the bug

refreshVersions is not able to find the latest versions of artifact in local maven repository.

To Reproduce

  1. Publish any project/library that uses maven-publish plugin to local maven repository, e.g. via ./gradlew publishToMavenLocal
  2. Use it as a dependency in another project with refreshVersions, specifying the local repository via `repositories {
bug good first issue
TheOddler
TheOddler commented Sep 6, 2021

When trying out Niv and following the example from the readme to add GHC:

$ niv add ghc   \
    -v 8.4.3    \
    -t 'https://downloads.haskell.org/~ghc/<version>/ghc-<version>-i386-deb8-linux.tar.xz'

But instead using the latest ghc version (9.0.1 as of writing), I get the following error:

$ niv add ghc -v 9.0.1 -t 'https://downloads.haskell.org/~ghc/<version>/ghc-<versi
docat
dgkf
dgkf commented Oct 12, 2021

We encountered this on an internal deployment, but wanted to post a related bug report here for tracking.

We were trying to deploy to a tag that was "broken" (still not entirely sure what that means), and got the response

$ curl --request POST \
       --header "Docat-Api-Key: $TOKEN" \
       --form "file=@site.zip" \
       "http://www.mydocat.com/api/myproj/brokentag"

<!DOCTYP
bug enhancement help wanted good first issue
edbzn
edbzn commented May 27, 2022

As we don't particularly need RxJS in semver (no retry, only one value emitted) RxJS can be a barrier for new contributors because not everyone is familiar with RxJS.

A bunch of functions used in semver return an Observable and we should migrate to Promise, no need to refactor the whole project in one commit we can refactor one function by one making sure tests still pass.

This is a good

enhancement good first issue

Improve this page

Add a description, image, and links to the versioning topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the versioning topic, visit your repo's landing page and select "manage topics."

Learn more