-
I'm getting the error `unexpected error: Resource not accessible by integration` when running the version bump [here](https://github.com/maxhollmann/github-workflow-tests/actions/runs/4812439092/jobs…
-
### Jenkins and plugins versions report
Environment
```text
Paste the output here
```
### What Operating System are you using (both controller, and any agents involved in th…
-
## Bug Report
### Description
If the version variable includes a pre-release segment , post-release segment or development segment (PEP440 / PyPA Version Specifiers), the version is not getting up…
-
When multiple lightweight tags are applied to the same commit, it chooses the first one. Usually, we prefer to return the "latest" tag (largest version number)
To reproduce:
```
git tag 1.1.0
gi…
-
# Feature Request
# Problem Statement
Our current release process does not automatically adjust the latest tag to the most recent official version based on semantic versioning. This limitation ari…
-
This bug spans from the feature added in #1049
Semver resolver seems to be confuse when we put variables into tag. If you have set input as `tag: v$RESOLVED_VERSION-rc+1234` as allowable with semv…
-
### Description
Dear Gittyup Developers,
I have noticed an inconsistency in the version tagging within the releases section that could potentially confuse users trying to track changes or unders…
-
### Describe the bug
Watchtower detects an image update by monitoring updates to the exact image tag of a running container. The docs don't appear to explain this well? Digging through issues (_or …
-
I believe the semver ordering does not work correctly when "--next-release" is used.
I can confirm that when I use semver sorting and a backport is the target of the "--next-tag" tag, the generate…
-
### What version of Bun is running?
1.1.26+0a37423ba
### What platform is your computer?
Microsoft Windows NT 10.0.22621.0 x64
### What steps can reproduce the bug?
Oh, if only I knew.
…