search

docker / compose-on-kubernetes

Deploy applications described in Compose onto Kubernetes clusters
Apache License 2.0
1.42k stars 159 forks source link

Bump github.com/Masterminds/semver from 1.4.2 to 3.0.1 #141

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Bumps github.com/Masterminds/semver from 1.4.2 to 3.0.1.

Release notes *Sourced from [github.com/Masterminds/semver's releases](https://github.com/Masterminds/semver/releases).* > ## 3.0.1 > [#125](https://github-redirect.dependabot.com/Masterminds/semver/issues/125): Fixes issue with module path for v3 > > ## v3.0.0 > This is a major release of the semver package which includes API changes. The Go > API is compatible with ^1. The Go API was not changed because many people are using > `go get` without Go modules for their applications and API breaking changes cause > errors which we have or would need to support. > > The changes in this release are the handling based on the data passed into the > functions. These are described in the added and changed sections below. > > ### Added > > - StrictNewVersion function. This is similar to NewVersion but will return an > error if the version passed in is not a strict semantic version. For example, > 1.2.3 would pass but v1.2.3 or 1.2 would fail because they are not strictly > speaking semantic versions. This function is faster, performs fewer operations, > and uses fewer allocations than NewVersion. > - Fuzzing has been performed on NewVersion, StrictNewVersion, and NewConstraint. > The Makefile contains the operations used. For more information on you can start > on Wikipedia at https://en.wikipedia.org/wiki/Fuzzing > - Now using Go modules > > ### Changed > > - NewVersion has proper prerelease and metadata validation with error messages > to signal an issue with either of them > - Handles space separated AND conditions in addition to , > - ^ now operates using a similar set of rules to npm/js and Rust/Cargo. If the > version is >=1 the ^ ranges works the same as v1. For major versions of 0 the > rules have changed. The minor version is treated as the stable version unless > a patch is specified and then it is equivalent to =. One difference from npm/js > is that prereleases there are only to a specific version (e.g. 1.2.3). > Prereleases here look over multiple versions and follow semantic version > ordering rules. This pattern now follows along with the expected and requested > handling of this packaged by numerous users. > > ## Release 1.5.0 > ## Added > > - [#103](https://github-redirect.dependabot.com/Masterminds/semver/issues/103): Add basic fuzzing for `NewVersion()` (thanks [@​jesse-c](https://github.com/jesse-c)) > > ## Changed > > - [#82](https://github-redirect.dependabot.com/Masterminds/semver/issues/82): Clarify wildcard meaning in range constraints and update tests for it (thanks [@​greysteil](https://github.com/greysteil)) > - [#83](https://github-redirect.dependabot.com/Masterminds/semver/issues/83): Clarify caret operator range for pre-1.0.0 dependencies (thanks [@​greysteil](https://github.com/greysteil)) > - [#72](https://github-redirect.dependabot.com/Masterminds/semver/issues/72): Adding docs comment pointing to vert for a cli > - [#71](https://github-redirect.dependabot.com/Masterminds/semver/issues/71): Update the docs on pre-release comparator handling > - [#89](https://github-redirect.dependabot.com/Masterminds/semver/issues/89): Test with new go versions (thanks [@​thedevsaddam](https://github.com/thedevsaddam)) > ... (truncated)
Changelog *Sourced from [github.com/Masterminds/semver's changelog](https://github.com/Masterminds/semver/blob/master/CHANGELOG.md).* > ## 3.0.1 (2019-09-13) > > ### Fixed > > - [#125](https://github-redirect.dependabot.com/Masterminds/semver/issues/125): Fixes issue with module path for v3 > > ## 3.0.0 (2019-09-12) > > This is a major release of the semver package which includes API changes. The Go > API is compatible with ^1. The Go API was not changed because many people are using > `go get` without Go modules for their applications and API breaking changes cause > errors which we have or would need to support. > > The changes in this release are the handling based on the data passed into the > functions. These are described in the added and changed sections below. > > ### Added > > - StrictNewVersion function. This is similar to NewVersion but will return an > error if the version passed in is not a strict semantic version. For example, > 1.2.3 would pass but v1.2.3 or 1.2 would fail because they are not strictly > speaking semantic versions. This function is faster, performs fewer operations, > and uses fewer allocations than NewVersion. > - Fuzzing has been performed on NewVersion, StrictNewVersion, and NewConstraint. > The Makefile contains the operations used. For more information on you can start > on Wikipedia at https://en.wikipedia.org/wiki/Fuzzing > - Now using Go modules > > ### Changed > > - NewVersion has proper prerelease and metadata validation with error messages > to signal an issue with either of them > - ^ now operates using a similar set of rules to npm/js and Rust/Cargo. If the > version is >=1 the ^ ranges works the same as v1. For major versions of 0 the > rules have changed. The minor version is treated as the stable version unless > a patch is specified and then it is equivalent to =. One difference from npm/js > is that prereleases there are only to a specific version (e.g. 1.2.3). > Prereleases here look over multiple versions and follow semantic version > ordering rules. This pattern now follows along with the expected and requested > handling of this packaged by numerous users. > > ## 1.5.0 (2019-09-11) > > ### Added > > - [#103](https://github-redirect.dependabot.com/Masterminds/semver/issues/103): Add basic fuzzing for `NewVersion()` (thanks [@​jesse-c](https://github.com/jesse-c)) > > ### Changed > > - [#82](https://github-redirect.dependabot.com/Masterminds/semver/issues/82): Clarify wildcard meaning in range constraints and update tests for it (thanks [@​greysteil](https://github.com/greysteil)) > ... (truncated)
Commits - [`fe7c210`](https://github.com/Masterminds/semver/commit/fe7c21038085e01e67044ec1efe3afb1eaa59f75) Merge pull request [#126](https://github-redirect.dependabot.com/Masterminds/semver/issues/126) from mattfarina/modfix - [`7e17568`](https://github.com/Masterminds/semver/commit/7e17568ada15d790f50e89b073b51b09d368faca) Fixes issue with module path for v3 - [`0337c9b`](https://github.com/Masterminds/semver/commit/0337c9b20b861d2c2e7b25450779f5d91caca32e) Merge pull request [#124](https://github-redirect.dependabot.com/Masterminds/semver/issues/124) from mattfarina/v3-rel-notes - [`be888df`](https://github.com/Masterminds/semver/commit/be888dfcc01a5c1563253956285ddb3e151a0325) Updating the docs for the 3.0.0 release - [`4492473`](https://github.com/Masterminds/semver/commit/4492473e338702d28d03e516480141b48afa3f81) Merge pull request [#121](https://github-redirect.dependabot.com/Masterminds/semver/issues/121) from mattfarina/fuzzing - [`b01f0c4`](https://github.com/Masterminds/semver/commit/b01f0c4920e5c85d5f9cde6bc1bb4d79cec1eea7) Adding fuzzing for v3 - [`3c3e3c7`](https://github.com/Masterminds/semver/commit/3c3e3c79b8d850de7bcab3f2d02260c62dd53a15) Merge pull request [#123](https://github-redirect.dependabot.com/Masterminds/semver/issues/123) from mattfarina/changelog-update3 - [`c4400c9`](https://github.com/Masterminds/semver/commit/c4400c985096195a914216e05c5b7107ddbb96f6) Updating changelog for 1.5.0 release - [`0873dd6`](https://github.com/Masterminds/semver/commit/0873dd604da5e3a3d0c7dbfdaf62d007a009e93c) Merge pull request [#120](https://github-redirect.dependabot.com/Masterminds/semver/issues/120) from mattfarina/fix-119 - [`6d097ca`](https://github.com/Masterminds/semver/commit/6d097ca3a866d8319434365232fe4c1935c815d0) Handling ^ correctly with additional tests - Additional commits viewable in [compare view](https://github.com/Masterminds/semver/compare/v1.4.2...v3.0.1)


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.
dependabot-preview[bot] commented 5 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.