-
See below screenshot:
![image](https://github.com/jefflinse/pr-semver-bump/assets/51723690/b2587eeb-53c7-4048-83cf-6ba2aa8b3a1a)
Below is the workflow file that triggers the error:
```
name:…
-
Hi!
Due to the various semantic versioning checks for the image tags, you cannot use a non-semver compliant tag. Particularly Im trying to use the `ai-beta` tag.
e.g. this in deployments.yaml is…
-
### What are you trying to do?
Expanding on https://github.com/dagger/dagger/issues/6605 which addresses the case for a `dagger update` command.
However, currently `dependencies` in `dagger.json` …
-
This matters because I can't (at least not easily) specify a dependency on `4.0.0.beta.4` using the swift package manager version 3.0.2.
The format for a release version must be `X.y.z-beta.Q`. The…
-
## Description
Currently, the only way for someone to determine what version of the gnovm they are using is to look at the git commit hash of whatever version they have installed (and hope that the…
-
## Description
I have the following syncpack configuration:
```json
{
"versionGroups": [
{
"label": "Use workspace protocol for local packages",
"dependencies": ["$LOCAL"]…
-
I've trying to push my images to github registry
And faced error
` > NX buildx failed with: ERROR: failed to solve: failed to push backend:main: server message: insufficient_scope: authorization…
-
-
### Prerequisites
- [X] I have written a descriptive issue title
- [X] I have searched [issues](https://github.com/GitTools/GitVersion/issues) to ensure it has not already been reported
### Git…
-
Apparently there is a convention for prefixing git version number tags with the letter `v`. At one time, this was even [recommended in the semver spec](https://semver.org/spec/v1.0.0.html#tagging-spec…