wooga / atlas-release

98%

master: 81%

LAST BUILD ON BRANCH PR-47

branch: PR-47

CHANGE BRANCH

x

Reset

• PR-47
• 0.5.2
• PR-100
• PR-101
• PR-103
• PR-104
• PR-105
• PR-106
• PR-107
• PR-108
• PR-109
• PR-110
• PR-111
• PR-112
• PR-113
• PR-114
• PR-115
• PR-116
• PR-117
• PR-118
• PR-119
• PR-120
• PR-31
• PR-33
• PR-35
• PR-38
• PR-39
• PR-40
• PR-41
• PR-42
• PR-44
• PR-45
• PR-46
• PR-48
• PR-49
• PR-50
• PR-51
• PR-52
• PR-53
• PR-54
• PR-57
• PR-62
• PR-64
• PR-65
• PR-67
• PR-68
• PR-69
• PR-70
• PR-71
• PR-72
• PR-73
• PR-75
• PR-76
• PR-77
• PR-78
• PR-79
• PR-80
• PR-81
• PR-82
• PR-83
• PR-84
• PR-85
• PR-86
• PR-87
• PR-88
• PR-89
• PR-90
• PR-91
• PR-92
• PR-93
• PR-94
• PR-95
• PR-96
• PR-97
• PR-98
• PR-99
• configurable_meta_clean
• custom-github-release-body
• enhance/gradle_version_check
• feature/github_publish
• feature/meta_cleanup
• feature/release_note_with_dependencies
• fix/add_subproject_setup_task
• fix/change_set_icon_urls
• fix/ensure-release-notes
• fix/handle-multiple-hashsigns-in-commit
• fix/normalize_release_notes
• fix/paket-pack-multiple-template-files-with-same-id
• fix/plugin_crash_when_pull-request_can_not_be_found
• fix/publish-task-dependency
• fix/semver_2_version_strategy
• fix/strip_duplicate_changeset_icon_list
• fix_rc_error_messages
• githubrelease/set-is-prerelease-lazy
• gradle/update_build_dependencies
• master
• refactor/make_patch_release_default
• refactor/remove_release_notes_generator
• release/2.x
• release_notes_generator
• update/atlas-paket
• update/paket-get
• v0.10.0
• v0.10.1
• v0.10.2
• v0.11.0
• v0.11.1
• v0.12.0
• v0.13.0
• v0.14.0
• v0.15.0
• v0.15.1
• v0.2.0
• v0.3.0
• v0.4.0
• v0.5.0
• v0.5.1
• v0.5.2
• v0.6.0
• v0.7.0
• v0.8.0
• v0.9.0
• v0.9.1

Fix version precedence check for snapshot (ci) builds

Description
===========

The new `semver 2.0` snapshot strategy enforces version precedence due
to a configuration error. This is a clear bug because snapshot builds
are designed to be outside the version order for `rc` or `final` builds.
So how can this bug show itself. The only valid way at the moment to
trigger this bug is to build a prerelease build (`rc`) and then a
snapshot version with the same base version. This can happen in
`release/2.x` branches. A snapshot build should have no direct
connections to any pre or final release.

**gradle output**
```
> Inferred version (2.0.0-branch.release.2.x.0) cannot be lower than nearest (2.0.0-rc.1). Required by selected strategy.
```

This patch simply configures the snapshot strategy not to enforce
version precedence (the old v1 did this as well).

Changes
=======

![FIX] semver `2.0` snapsphot version prcedence check