-
I didn't see anything in the documentation about how to get setuptools_scm to decide the next version number will bump the major version number (1.5 -> 2.0.devN###). Our setuptools_scm generated versi…
-
I'm still trying to reproduce the issue myself, since it pops up occasionally in my CI even with it inline.
Right now I'm having doubts as to whether or not "parallel" changes the behavior at all, …
-
Hello,
Could it be possible to not push "Snapshot" versions to the "latest" Docker Tag?
In my opinion "latest" is normally meant to be the latest **_stable_** Version of a Product/Image.
"Snapsho…
-
Currently, kobold updates the full image ref. This leads to the default registry being added to image for non fully qualified domain names. It would be better if only the tag / digest would be changed…
-
## Problem
Offer separate SecHub Client executables to download rather than a ZIP including all SecHub Client executables.
The SecHub Client ZIP includes a number of executables for different ar…
-
## CVE-2022-25883 - High Severity Vulnerability
Vulnerable Libraries - semver-7.3.5.tgz, semver-6.3.0.tgz, semver-5.7.1.tgz
semver-7.3.5.tgz
The semantic version parser used by npm.
Library home p…
-
# Story
Als Entwickler gaben wir einen stabilen Build für die Frontend SPA.
# Akzeptanzkriterien
* React Framework mit Typescript im Ordner `frontend/spa`.
* Builds mit `pnpm`
* Eine Demoseite mit…
-
Is this expected behavior?
When the latest tag moves to another hash/image, it is obvious that the image developers want this new latest-tagged-image to be used as latest, even if the version is no…
-
Would be great to use custom versioning format, e.g. "latest" or even using hash commits in the version itself.
Currently it's not possible to specify custom version format in --version or in Chart.y…
-
I've been trying to push my images to GitHub registry. I have no-monorepo with two projects
Example of my project target inside project.json
```
"container": {
"executor": "@nx-tools/nx-cont…