-
### Describe the feature
Always syncing to the most recent commit to `main` is useful, but in some release schedules, several PRs might be accumulated in `main` before a new release is made. Being …
-
> @aderito7 could you verify that the already existing tag `my-app-0.92.0` targets a `baseBranch` reference, otherwise, it will throw `fatal: tag already exists` because the tag is not reachable for c…
edbzn updated
2 years ago
-
I'd like to kick off semver tags based on git branch names, as opposed to git tag names.
For example:
push | refs/heads/release/v1.2.3 | `1.2.3`, `1.2`
-- | -- | --
It doesn't seem like this…
-
Hello!
We're trying to `skopeo sync` oci artifacts for use with helm. They are versioned according to semver, but also contain metadata (after the `+` character, which helm changes to an underscore…
-
## 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…
-
### The problem
I just tried to specify a build matrix that includes the latest beta, `go1.15beta1` (using `stable: 'false'`). This failed because `go1.15beta1` is not a valid version - `1.15.0-bet…
-
# Release of gatewayTranslate v1.1
## Preconditions
- [x] The develop branch has all changes merged for the next release
- [x] The develop branch has the semver for the next release
- [x] QA h…
-
## CVE-2022-25883 - High Severity Vulnerability
Vulnerable Libraries - semver-7.0.0.tgz, semver-6.3.0.tgz, semver-5.7.1.tgz
semver-7.0.0.tgz
The semantic version parser used by npm.
Library home p…
-
At the moment, working through a pre-release process can be a little tricky given the differences between how Python and Helm handle pre-releases. Helm enforces [a strict SemVer versioning scheme](htt…
-
## CVE-2021-3795 - High Severity Vulnerability
Vulnerable Library - semver-regex-1.0.0.tgz
Regular expression for matching semver versions
Library home page: https://registry.npmjs.org/semver-regex/…