-
Updated
Mar 14, 2022 - Go
versioning
Here are 904 public repositories matching this topic...
-
Updated
Apr 3, 2022 - Python
-
Updated
Apr 3, 2022 - C#
-
Updated
Jan 11, 2021 - Python
-
Updated
Mar 5, 2022 - Go
-
Updated
Jan 13, 2022 - Ruby
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
Switch to Java 18
-
Updated
Feb 22, 2022 - JavaScript
-
Updated
Apr 1, 2022 - Ruby
-
Updated
Feb 26, 2022 - Kotlin
-
Updated
Apr 7, 2018 - JavaScript
-
Updated
Apr 2, 2022 - JavaScript
-
Updated
Mar 9, 2022 - C#
-
Updated
Mar 16, 2022 - JavaScript
-
Updated
Mar 31, 2022 - Elixir
-
Updated
Mar 31, 2022 - Groovy
-
Updated
Dec 29, 2021 - Ruby
-
Updated
Oct 6, 2021 - CSS
-
Updated
Feb 24, 2022 - Python
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
Improve logging
Actually, the logging is made by standard version, we should first disable it and log ourself the following events:
- bump version from
{from}
to{to}
- output changes in
{projectRoot}/{path-to-changelog}.md
- commit created
- tag
{tag}
created - push success (if git push occurred)
- run postTargets
{postTargets}
- postTarget
{postTargetName}
failure - postTarget `{postTarge
Improve this page
Add a description, image, and links to the versioning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the versioning topic, visit your repo's landing page and select "manage topics."
Describe the bug
refreshVersions is not able to find the latest versions of artifact in local maven repository.
To Reproduce
maven-publish
plugin to local maven repository, e.g. via./gradlew publishToMavenLocal