tekton-dag/stacks/versions.yaml at main · jmjava/tekton-dag · GitHub

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
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
# ============================================================================
# Version Registry — infrastructure-level, independent of application code.
#
# This file lives in the platform repo, NOT in any app repo.
# It tracks the current and last-released version for every app
# across all stacks. Think of it as the "known good version set".
#
# How it's used:
#   - The pipeline reads this as the DEFAULT version set.
#   - You can OVERRIDE any version at run time by passing a
#     version-overrides parameter (JSON) to the pipeline.
#   - On PR pass:  the RC suffix auto-increments here.
#   - On merge:    the version promotes to release, the image gets
#                  tagged with that semver, and patch bumps for next cycle.
#
# Manual edits are expected for major/minor bumps:
#   change 1.2.1-rc.0 → 2.0.0-rc.0 to signal a breaking change.
# ============================================================================

apps:
  # --- Stack One: Vue FE + Spring Boot middleware + Spring Boot API ---
  demo-fe:
    version: "0.1.0-rc.1"
    last-released: "0.0.0"
  release-lifecycle-demo:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  demo-api:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  # --- Stack Two: mixed toolchain ---
  vendor-fe:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  vendor-middleware:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  vendor-adapter:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  internal-api:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  notifications-svc:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  # --- Standalone apps ---
  inventory-api:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"
  analytics-api:
    version: "0.1.0-rc.0"
    last-released: "0.0.0"