-
Notifications
You must be signed in to change notification settings - Fork 83
/
Copy path1697230491-Relax-version-checks-in-snapshot-builds.yaml
36 lines (30 loc) · 1.97 KB
/
1697230491-Relax-version-checks-in-snapshot-builds.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
# Kind can be one of:
# - breaking-change: a change to previously-documented behavior
# - deprecation: functionality that is being removed in a later release
# - bug-fix: fixes a problem in a previous version
# - enhancement: extends functionality but does not break or fix existing behavior
# - feature: new functionality
# - known-issue: problems that we are aware of in a given version
# - security: impacts on the security of a product or a user’s deployment.
# - upgrade: important information for someone upgrading from a prior version
# - other: does not fit into any of the other categories
kind: enhancement
# Change summary; a 80ish characters long description of the change.
summary: Relax version checks in snapshot builds
# Long description; in case the summary is not enough to describe the change
# this field accommodate a description without length limits.
# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment.
description: |
Relax version checking fleet-server does to client communication when built with SNAPSHOT=true.
Versions allowed will be <=X.Y+1.Z, that is to say snapshots will allow the next minor version to communicate.
This is done to avoid the chicken and egg prpoblem we face in automated testing when releasing new minor versions.
# Affected component; a word indicating the component this changeset affects.
component:
# PR URL; optional; the PR number that added the changeset.
# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added.
# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number.
# Please provide it if you are adding a fragment for a different PR.
#pr: https://github.com/owner/repo/1234
# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of).
# If not present is automatically filled by the tooling with the issue linked to the PR number.
issue: 2960