changelog.yaml

## -------------------------------------------------------------------------------
## Changelog Entry Documentation
## -------------------------------------------------------------------------------
#  type             The type of this change.
#                     Possible values:
#                     - 'bug'           Bug has been fixed
#                     - 'documentation' Documentation change
#                     - 'enhancement'   Feature has been implemented or some general improvements
#                     - 'internal'      Internal change which does not affect consumers directly (e.g. refactorings)
#                     - 'security'      A security relevant fix
#                     - 'hotfix'        Emergency bug fix which needs to be rolled out immediately via hotfix process
# impact            The impact this change has regarding consumption. The impact also affects the semantic version.
#                     Possible values:
#                     - 'incompatible'  An incompatible change requires more information in the warning
#                                       and updateNotes sections. Affects major or minor SemVer digit.
#                     - 'minor'         A compatible change which introduces a new feature or enhancement.
#                     - 'patch'         A compatible change without new features.
# title             The title of the change
# description       The description of the change (markdown syntax possible)
# warning           [optional] A warning for consumers if appropriate
# upgradeNotes      [optional] Everything a consumer needs to know and adapt in order to consume this change.
# deprecations      [optional] If this change deprecates something we need to inform consumers to adapt early,
#                              before we remove it completely in the next months.
# pullRequestNumber The number of this pull request.
#                       A list is also possible in case more than one pull requests are involved in this change, e.g. [123, 456].
# jiraIssueNumber   The number of the Jira issue.
#                       A list is also possible in case more than one Jira issues are affected by this change, e.g. [123, 456].

## --------------------------------------------------------------------------------------------------
## For new change entries copy the template below to 'changes:' of the 'version: NEXT' array element.
## --------------------------------------------------------------------------------------------------
#    - type: [bug, enhancement, security, internal, hotfix, documentation]
#      impact: [incompatible, minor, patch]
#      title: <title>
#      description: |-
#        <description (markdown syntax)>
#      warning: |-
#        <optional warning message (markdown syntax)>
#      upgradeNotes: |-
#        <optional upgrade guidelines (markdown syntax)>
#      deprecations: |-
#        <optional deprecation notes (markdown syntax)>
#      pullRequestNumber: <pull request number(s)>
#      jiraIssueNumber: <Jira issue number(s)>


# Paste new changelog entries below 'changes:' of the 'version: NEXT' array element.
# ! Do NOT add change entries to already released versions! Only add to version 'NEXT'.
# ! Do NOT change any 'version' or 'date' values manually! The pipeline will take care.
# ! Do NOT change the order of version blocks! 'NEXT' needs to stay the first version block.
- version: NEXT
  date: TBD
  changes:

- version: "0.15.0"
  date: 2021-12-06
  changes:

    - type: bug
      impact: patch
      title: "Fix: Integration tests are failing because of changed revision"
      description: |-
        The revision of the pipelines used in the integration tests changed.
        It is adjusted with this pull request.
      pullRequestNumber: 290

    - type: enhancement
      impact: patch
      title: Don't panic but exit gracefully
      description: |-
        Instead of panicking (which prints stack dumps), just exit with error message.
      pullRequestNumber: 285

    - type: internal
      impact: patch
      title: Refactor metric support
      description: |-
        The metric support code needs refactoring.
      pullRequestNumber: 282

    - type: enhancement
      impact: minor
      title: Embed workqueue metrics
      description: |-
        Embed metrics provided by package `k8s.io/client-go/util/workqueue` into
        Steward Core metrics.
      upgradeNotes:
        Metric `steward_queued_total` has been removed.
        Change existing monitoring tools to use `steward_piperuns_workqueue_depth`
        instead.
      pullRequestNumber: 282

    - type: enhancement
      impact: minor
      title: Embed client-go rest client metrics
      description: |-
        Embed metrics provided by package `k8s.io/client-go/util/rest` into
        Steward Core metrics.
      pullRequestNumber: 282

    - type: enhancement
      impact: minor
      title: Use consistent metric names
      description: |-
        Steward Core metrics had inconsistent names.
        New metrics with consistent names have been added, while old ones have
        been deprecated.
      deprecations: |-
        -   Metric `steward_pipelinerun_ongoing_state_duration_periodic_observations_seconds` is deprecated.
            Use `steward_pipelineruns_ongoing_state_duration_periodic_observations_seconds` instead.
        -   Metric `steward_pipelinerun_state_duration_seconds` is deprecated.
            Use `steward_pipelineruns_state_duration_seconds` instead.
        -   Metric `steward_tenants_total` is deprecated.
            Use `steward_tenants_count_total` instead.
      pullRequestNumber: 282

    - type: enhancement
      impact: minor
      title: Add metrics for retry loops
      description: |-
        For the analysis of performance issues it can be helpful to have metrics
        for retry loops (number of retries, latency).
      pullRequestNumber: 282

    - type: enhancement
      impact: patch
      title: Deprecate metric `steward_pipelinerun_update_seconds`
      description: |-
        Besides the deprecation nothing has been changed.
      deprecations: |-
        -   Metric `steward_pipelinerun_update_seconds` is deprecated.
            Use REST client metrics and retries metrics instead.
      pullRequestNumber: 282

    - type: documentation
      impact: patch
      title: Add metrics reference documentation
      description: |-
        A new page `docs/monitoring/Metrics Reference.md` describes all metrics
        exposed by Steward binaries.
      pullRequestNumber: 282

    - type: internal
      impact: patch
      title: Own Go module for Helm chart tests
      description: |-
        The tests for the Helm chart should not belong to the main Go module,
        because they are completely independent of it.
      pullRequestNumber: 284

    - type: internal
      impact: minor
      title: Update Go build dependencies
      description: |-
        Most noteworthy:

        - Kubernetes libraries to v1.21.7
        - Tekton to v0.30.0
      upgradeNotes: |-
        Steward should still _run_ with lower versions of Kubernetes and Tekton.
        However, this has not been tested.
        Therefore, test your setup carefully.
      pullRequestNumber: 284

    - type: internal
      impact: minor
      title: Increase Go language version to 1.16
      description: |-
        Steward now needs Go 1.16 to build.
      upgradeNotes: |-
        When using Steward as a Go dependency (which should not be the case
        as Steward is not designed as a library), make sure it still can be
        built in your context.
      pullRequestNumber: 284

    - type: bug
      impact: patch
      title: Fix improper error handling
      description: |-
        In `pkg.k8s` the functions
        `(*serviceAccountHelper) GetServiceAccountSecretName` and
        `(*serviceAccountHelper) GetServiceAccountSecretNameRepeat` swallow
        errors that can occur when performing K8s API calls.
      pullRequestNumber: 287

    - type: bug
      impact: patch
      title: Fix improper error handling
      description: |-
        The run controller did not put back a pipeline run into its work queue
        for later retry if it was in state `running` but updating the resource
        status failed.
      pullRequestNumber: 288

    - type: enhancement
      impact: patch
      title: Update Go SDK to v1.16.11
      description: |-
        Build with Go SDK [v1.16.11](https://golang.org/doc/go1.16).
      pullRequestNumber: 292

- version: "0.14.4"
  date: 2021-11-17
  changes:

    - type: security
      impact: patch
      title: Updated JFR to 211116_03f24d5
      description: |-
        Updated JFR to [211116_03f24d5](https://github.com/SAP/stewardci-jenkinsfilerunner-image/releases/tag/211116_03f24d5)
        with latest dependencies and fixed vulnerabilities.
      pullRequestNumber: 280
      jiraIssueNumber: 1182

    - type: internal
      impact: patch
      title: Prepare `build.sh` for Go v1.16+
      description: |-
        Adjust 'build.sh' script to be compatible with Go v1.16+.
      pullRequestNumber: 278
      jiraIssueNumber: 1131

    - type: bug
      impact: patch
      title: fix heartbeat
      description: |-
        Heartbeat was not working correctly. It was only working if items were queued or processed.
        This change is fixing the heartbeat.
      pullRequestNumber: 275
      jiraIssueNumber: 1131

    - type: internal
      impact: patch
      title: Use Go v1.16.10
      description: |-
        Use Go [v1.16.10](https://golang.org/doc/go1.16) to build the project.
      pullRequestNumber: 277

- version: "0.14.3"
  date: 2021-10-29
  changes:

    - type: bug
      impact: patch
      title: "Fix: Tekton fails to start JFR pod if container registry rate limit is exceeded"
      description: |-
        Steward uses Tekton to run JFR pods for pipeline runs.
        The respective ClusterTask contains a pod template that does _not_ specify
        the entrypoint of the JFR container.
        Therefore Tekton tries to obtain the entrypoint by downloading the
        container image manifest from the registry.
        This may fail if the registry's rate limit is exceeded.
        As a workaround, specify the JFR container entrypoint in the ClusterTask.
      pullRequestNumber: 272
      jiraIssueNumber: 1109

- version: "0.14.2"
  date: 2021-10-14
  changes:

    - type: internal
      impact: patch
      title: add additional logging for commitState
      description: |-
        Logging of pipelineRun.CommitState() function is extended on log level 6.
      pullRequestNumber: 268

- version: "0.14.1"
  date: 2021-10-14
  changes:

    - type: bug
      impact: patch
      title: fix binary names on helm level
      description: |-
        In v0.14.0 the binary names has been changed. The binary names has not
        been adjusted on helm level. The binary names are adjusted now.
      pullRequestNumber: 266

- version: "0.14.0"
  date: 2021-10-13
  changes:

    - type: enhancement
      impact: minor
      title: Write stack dumps on sig quit
      description: |-
        Enable writing threaddumps. Similar to jstack for java. Makes troubleshooting easier.
        On SIGQUIT (3) the dumps are written to the log with severity info.
      pullRequestNumber: 256

    - type: enhancement
      impact: minor
      title: Provide reasonable names for the binaries
      description: |-
        For troubleshooting cases we need to be able to send signals to
        the processes which corresponds to the binaries (run controller,
        tenant controller). In order to be able to send those signals we
        need to be able to distinguish these processes.
      pullRequestNumber: 260

- version: "0.13.3"
  date: 2021-10-08
  changes:

    - type: bug
      impact: patch
      title: Fix nil pointer dereference when Tekton task run failed to create pod
      description: |-
        Currently a nil pointer dereference error occures if a Tekton task is finished but has no
        finished time. This is fixed with this change.
      pullRequestNumber: 259
      jiraIssueNumber: 179

    - type: internal
      impact: patch
      title: Fix stewardci-example-pipelines repo branch name
      description: |-
        The `master` branch of repo `stewardci-example-pipelines`
        has been renamed to `main` which made the examples fail.
      pullRequestNumber: 257

- version: "0.13.2"
  date: 2021-10-05
  changes:

    - type: internal
      impact: patch
      title: Increase default log level
      description: |-
        Default log level was increaset to 3.
        Small adjustments to log output.
      pullRequestNumber: 254
      jiraIssueNumber: CLOUDCIFEAT1-173

    - type: bug
      impact: patch
      title: Fix measuring ongoing state durations
      description: |-
        Measuring ongoing state duration failed for pipeline runs in state `new`
        with error message:

        ```
        cannot observe StateItem if StartedAt is not set
        ```
      pullRequestNumber: 255

- version: "0.13.1"
  date: 2021-09-27
  changes:

    - type: internal
      impact: patch
      title: Updated JenkinsfileRunner image to 210924_6ec1ff6
      description: |-
        JenkinsfileRunner image was updated to [210924_6ec1ff6](https://github.com/SAP/stewardci-jenkinsfilerunner-image/releases/tag/210924_6ec1ff6)
      pullRequestNumber: 252

- version: "0.13.0"
  date: 2021-08-17
  changes:

     - type: bug
       impact: minor
       title: Avoid non atomic status updates
       description: |-
         Without this change the state might be upated e.g. to a final state
         without setting a corresponding result. The result is provided a short period
         of time later with an other update. In the meantime we have an invalid state.
         With this change we apply both changes to the memory representation of a
         pipeline run and send the update only once. With this approach there is no
         short period of time with an invalid state
       warning: |-
         needs to be validated carefully since this is a bigger refactoring
       pullRequestNumber: 248
       jiraIssueNumber: CLOUDCIFEAT1-130

     - type: bug
       impact: patch
       title: Fix deletion bug #241
       description: |-
         When a pipeline run was deleted the state and the result were not updated in some edge cases. This is fixed now.
       pullRequestNumber: 250

- version: "0.12.1"
  date: 2021-07-28
  changes:
     - type: bug
       impact: patch
       title: Fix deletion bug #241
       description: |-
         When a pipeline run was deleted the state and the result has not been updated. This is fixed now.
       upgradeNotes: |-
         `ResultDeleted` was only used in the metrics before. Now it can also occur as a pipeline run result.
       pullRequestNumber: 242

- version: "0.12.0"
  date: 2021-07-28
  changes:

    - type: enhancement
      impact: minor
      title: Meter ongoing state durations periodically
      description: |-
        Introduced a new histogram metric `steward_pipelinerun_ongoing_state_duration_periodic_observations_seconds`.
        The purpose of this metric is the detection of overly long processing times, caused by e.g. hanging controllers.
      pullRequestNumber: 236
      jiraIssueNumber: 719

    - type: enhancement
      impact: incompatible
      title: Rename metric
      description: |-
        Metric `steward_pipelinerun_duration_seconds` has been renamed to
        `steward_pipelinerun_state_duration_seconds` to better express the
        fact that durations are reported for pipeline run _states_, not pipeline
        runs as a whole.
      upgradeNotes: |-
        Adapt consumers of monitoring data to the new metric name.
      pullRequestNumber: 236

- version: "0.11.1"
  date: 2021-07-28
  changes:

    - type: internal
      impact: patch
      title: Update JenkinsfileRunner image to 210728_f8be088
      description: |-
        JenkinsfileRunner image was updated to [210728_f8be088](https://github.com/SAP/stewardci-jenkinsfilerunner-image/releases/tag/210728_f8be088)
      pullRequestNumber: 244

- version: "0.11.0"
  date: 2021-06-29
  changes:

    - type: enhancement
      impact: minor
      title: Configurable pod security policies
      description: |-
        There are new chart parameters to specify which _existing_ pod security
        policies should be used by pipeline run pods and Steward controllers:

        - `pipelineRuns.podSecurityPolicyName`
        - `tenantController.podSecurityPolicyName`
        - `runController.podSecurityPolicyName`

        If such parameters are _not_ specified, the chart generates default
        pod security policies as before.

        See the chart README for details.
      pullRequestNumber: 237
      jiraIssueNumber: 738

- version: "0.10.0"
  date: 2021-06-16
  changes:

    - type: enhancement
      impact: minor
      title: Make PodSecurityPolicies for pipelineRun and both controllers configurable
      description: |-
        Make 'PodSecurityPolicy' configurable to be able to change the policy during installation with helm.
        steward helmchart loads default 'PodSecurityPolicy' from a file if corresponding fields are not set inside 'Values.yaml' file.
      pullRequestNumber: 234
      jiraIssueNumber: 738

- version: "0.9.0"
  date: 2021-05-18
  changes:

    - type: enhancement
      impact: minor
      title: Updated Jenkinsfile Runner image to 210518_50469d1
      description: |-
        The Jenkinsfile Runner image has been updated to [210518_50469d1](https://github.com/SAP/stewardci-jenkinsfilerunner-image/releases/tag/210518_50469d1).
        This image version contains an updated LTS Jenkins Core version 2.277.4, updated plugins and an updated Jenkinsfile Runner 1.0-beta-27 with
        [steward specific adjustments](https://github.com/SAP/stewardci-jenkinsfilerunner-image/tree/jenkinsfile-runner--1.0-beta-27-steward-1).
      deprecations: |-
        The following plugins were removed: 'analysis-collector', 'badge', 'email-ext'. Make sure your pipelines do not use those plugins.
      pullRequestNumber: 229
      jiraIssueNumber: 722

- version: "0.8.3"
  date: 2021-05-04
  changes:

  - type: internal
    impact: patch
    title: Fixed checkmarx scan
    description: |-
      The checkmarks scan reported some low findings which are fixed now.
    pullRequestNumber: 223

  - type: security
    impact: patch
    title: Update JFR image to 210413_777e270 with secure agent protocols
    description: |-
      Insecure Jenkins agent protocols have been disabled by configuring only secure ones.
      Here you can see the [Jenkinsfile Runner Image changes](https://github.com/SAP/stewardci-jenkinsfilerunner-image/compare/210205_1988c5e...210413_777e270).
    pullRequestNumber: 222
    jiraIssueNumber: 62

  - title: Introduce auxiliary pipeline run namespaces
    type: enhancement
    impact: patch
    description: |-
      In the future Steward will be enabled to provision service instances
      per pipeline run, e.g. a pipeline log forwarder.
      This change introduces auxiliary pipeline run namespaces where
      those run-specific service instances are defined in Kubernetes.

      The pattern of pipeline run namespace names changes.

      By default auxiliary namespaces are not created because they are not
      used yet. Enabling the feature flag `CreateAuxNamespaceIfUnused`
      enforces creating auxiliary namespaces.
    pullRequestNumber: 168

  - type: documentation
    impact: patch
    title: "Update secret examples"
    description: |-
      Move secret examples to own folder and extend the documentation.
    pullRequestNumber: 203

- version: "0.8.2"
  date: 2021-03-05
  changes:

    - type: internal
      impact: patch
      title: Updated release pipeline
      description: |-
        The release pipeline has been updated with compliance aspects
      pullRequestNumber: 220

- version: "0.8.1"
  date: 2021-02-23
  changes:

  - type: bug
    impact: patch
    title: fix args qps and burst of tenant controller deployment
    description: |-
      fix use qps and burst of tenant controller from the corresponding config values and not from run controller configuration
    warning:
    deprecations:
    pullRequestNumber: 218
    jiraIssueNumber: 214

- version: "0.8.0"
  date: 2021-02-19
  changes:

  - type: enhancement
    impact: minor
    title: "Make threadiness configurable for controllers"
    description: |-
      The threadiness for both run controller and tenant controller is now configurable.
      This allows for adjusting to the needs of particular usage scenarios.
    pullRequestNumber: 216
    jiraIssueNumber: 502

  - type: documentation
    impact: patch
    title: Add network policy examples
    description: Add examples for pipeline runs with configured network profiles.
    pullRequestNumber: 188

  - type: internal
    impact: patch
    title: "[Developer] update-codegen.sh: make generators selectable"
    description: |-
      The code generation script `hack/update-codegen.sh` got two new options `--gen-clients`
      and `--gen-mocks` to select what should be generated.
      If none of the `--gen-*` options is specified, _all_ generators are enabled.
    pullRequestNumber: 208

  - type: enhancement
    impact: minor
    title: "Client-side rate limiting configurable for tenant controller"
    description: |-
      The default values of are equal to those of the rest api.
      If many tenants exists, increasing the limit will make the processing of tenants faster e.g. creating a new tenant will take less time.
    pullRequestNumber: 214

  - type: bug
    impact: patch
    title: Delete finalizer after pipeline run is cleaned.
    description: |-
      Delete finalizer after pipeline run is cleaned.
    warning:
    deprecations:
    pullRequestNumber: 210
    jiraIssueNumber: 413

- version: "0.7.0"
  date: 2021-02-08
  changes:

  - type: enhancement
    impact: minor
    title: Make retry parameters for cloning the pipeline repo configurable
    description: |-
      Jenkinsfile Runner container entrypoint retries cloning the pipeline
      repository. The retry parameters (retry interval and timeout) are now
      configurable via Helm chart parameters.
      Jenkinsfile Runner image version which enables configuring retry
      parameters is also updated in the same PR. Changes in the new
      release of JFR image can be found [here](https://github.com/SAP/stewardci-jenkinsfilerunner-image/releases/tag/210205_1988c5e).
    pullRequestNumber: 209
    jiraIssueNumber: 350

  - type: enhancement
    impact: minor
    title: Update Jenkinsfile-runner image version
    description: |-
      Update Jenkinsfile-runner image to a newer version.
      All the changes on this version can be found [here](https://github.com/SAP/stewardci-jenkinsfilerunner-image/releases/tag/210202_42eb583).
    pullRequestNumber: 207
    jiraIssueNumber: [350, 441]

  - type: enhancement
    impact: minor
    title: "Add maintenance mode to run controller"
    description: |-
      Steward can be put in _maintenance mode_.
      It prevents _new_ pipeline runs to be processed, while pipeline runs that are in progress _already_ still run to completion.
    pullRequestNumber: 204
    jiraIssueNumber: 393

  - type: bug
    impact: patch
    title: "Fix update of state history"
    description: |-
      The state history of a pipeline run is not updated correctly if a concurrent change happens.
      This change will fix this bug.
    pullRequestNumber: 206

  - type: security
    impact: patch
    title: "network: don't allow local subnet multicast traffic"
    description: |-
      Local subnet multicast addresses (224.0.0.0/24; see [Wikipedia](https://en.wikipedia.org/wiki/Multicast_address))
      should not be allowed by rule "allow internet access" of the pipeline run network policy.
    warning: You should apply the network policy change from [#200](https://github.com/SAP/stewardci-core/pull/200) manually in case you override the default network policy from the Helm chart.
    pullRequestNumber: 200

- version: "0.6.3"
  date: 2020-12-14
  changes:
  - type: enhancement
    impact: minor
    title: Allow renamed secrets in run namespaces if annotation is provided
    description: Secrets can be renamed if you provide an annotation when they are copied to the run namespace.
    pullRequestNumber: 165
    jiraIssueNumber: 315

- version: "0.6.2"
  date: 2020-12-08
  changes:

  - type: bug
    impact: patch
    title: Fixed struct field tag syntax
    description: Fixed struct field tag syntax for "pkg/apis/steward/v1alpha1".JenkinsfileRunnerSpec
    warning:
    upgradeNotes:
    deprecations:
    pullRequestNumber: 186
    jiraIssueNumber:

  - title: Upgrade Go dependencies
    type: internal
    impact: patch
    description: |-
      Upgrade `github.com/aws/aws-sdk-go` from v1.32.1 to [v1.34.1](https://github.com/aws/aws-sdk-go/releases/tag/v1.34.1)
    pullRequestNumber: 183

  - title: Make Elasticsearch index URL configurable per pipeline run
    type: enhancement
    impact: minor
    description: >-
      Enhance the `pipelineruns.steward.sap.com` CRD by fields to configure the
      Elasticsearch index URL and credential to be used to store build logs.

      However, these values are still ignored by Steward. Log destinations per
      pipeline run will be enabled with a later change.
    pullRequestNumber: 172
    jiraIssueNumber: 984

- version: "0.6.1"
  date: 2020-11-11
  changes:
  - type: internal
    impact: patch
    title: The release pipeline is now enabled for hotfix releases
    description: See [developer documentation](https://github.com/SAP/stewardci-core/blob/master/docs/development/README.md#hotfix-releases) for more information.
    warning:
    upgradeNotes:
    deprecations:
    pullRequestNumber: 179
    jiraIssueNumber: 316

  - title: Upgrade Go dependencies
    type: internal
    impact: patch
    description: |-
      - upgrade Kubernetes libs from v1.17.6 to v1.17.13 (see [K8s changelog](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.17.md))
    pullRequestNumber: 180

  - title: improve pkg/runctl/cfg
    type: internal
    impact: patch
    description: |-
      - fix: pipeline run fails with `error_config` if its `spec.profiles.network` is set to the name of the _default_ network profile
      - do not trim whitespace from configured network policies, as it may destroy YAML wellformedness
      - fail loading the pipeline runs configuration if the network policies config map does not exist
      - give more precise error messages in case of erroneous pipeline runs configuration
      - lots of refactoring in `pkg/runctl/cfg`
    pullRequestNumber: 181

- version: "0.6.0"
  date: 2020-11-09
  changes:
  - title: Introduce feature flags
    type: internal
    impact: patch
    description: |-
      There's a new Go package `pkg/featureflag` to deal
      with feature flags in Steward controllers.
      Feature flags can be configured via Helm Chart.
    pullRequestNumber: 178

  - type: enhancement
    impact: minor
    title: Introduce network profiles
    description: |-
      Allow Steward clients to select a network profile per pipeline run.

      Network profiles are named network-related configurations defined by Steward operators.
      Currently they define a Kubernetes network policy. Additional network-related settings may be
      added in the future.

      Clients can choose a network profile via `spec.profiles.network` of a PipelineRun
      resource object.
    warning: ""
    upgradeNotes: |-
      - PiplineRun objects may now have a `status.result` value `error_config` (see Steward API docs).
      - Activating the new feature flag `RetryOnInvalidPipelineRunsConfig` will let the pipeline run controller retry reconciling in case the controller configuration (in ConfigMaps) is invalid or cannot be loaded. Without the feature flag all PipelineRun objects will be set to finished with result code `error_infra`. The new behaviour will become the default in a future release of Steward.
    deprecations: |-
      Helm configuration value `pipelineRuns.networkPolicy` is deprecated:
      use `pipelineRuns.networkPolicies` instead.
    pullRequestNumber: 160
    jiraIssueNumber: 1305

  - type: enhancement
    impact: incompatible
    title: Make Jenkinsfile Runner properties configurable in PipelineRun custom resource objects.
    description: |-
      Jenkinsfile Runner properties are configurable in Steward PipelineRun manifests at `spec.jenkinsfileRunner` now.
    warning: |-
        Old configuration will not work anymore! See upgrade notes.
    upgradeNotes: |-
      Helm Chart Configuration changed:

      - `pipelineRuns.jenkinsfileRunner.image.repository` is outdated: use `pipelineRuns.jenkinsfileRunner.image` instead
      - `pipelineRuns.jenkinsfileRunner.image.tag` is outdated: use `pipelineRuns.jenkinsfileRunner.image` instead
      - `pipelineRuns.jenkinsfileRunner.image.pullPolicy` is outdated: use `pipelineRuns.jenkinsfileRunner.imagePullPolicy` instead
    deprecations:
    pullRequestNumber: 162
    jiraIssueNumber: 983
  - type: enhancement
    impact: minor
    title: Replace insensitive terms with inclusive language
    description: |-
      Insensitive terms should be replaced by inclusive language in all SAP open source repositories.
    warning:
    upgradeNotes:
    deprecations:
    pullRequestNumber: 176
    jiraIssueNumber: 20

- version: "0.5.2"
  date: 2020-10-28
  changes:

  - type: internal
    impact: patch
    title: Fix clustertask
    description: |-
      Fix variables in clustertask to changed structure.
    warning:
    upgradeNotes:
    deprecations:
    pullRequestNumber: 173

  - type: internal
    impact: patch
    title: Updated Jenkinsfile Runner based on adoptopenjdk11 instead of openjdk8
    description: |-
      Besides plugin updates, Jenkins Core update and a Jenkinsfile Runner update the
      Jenkinsfile Runner image has been switched to adoptopenjdk11, mainly to reduce the attack vector.
    warning:
    upgradeNotes:
    deprecations:
    pullRequestNumber: 175
    jiraIssueNumber: 1348

- version: "0.5.1"
  date: 2020-10-05
  changes:

  - type: bug
    impact: patch
    title: Fix clustertask
    description: |-
      Fix clustertask to match v1beta1 specification.
    pullRequestNumber: 163

- version: "0.5.0"
  date: 2020-08-29
  changes:

  - type: enhancement
    impact: incompatible
    title: Upgrade dependency to Tekton v0.14.3
    description: |-
      Build and run against Tekton v0.14.3.
    warning: Requires Tekton v0.14.3.
    upgradeNotes: |-
      The target Kubernetes system must have Tekton v0.14.3 installed. Higher versions may also work.
      In addition, Steward Jenkinsfile Runner Image version [200921_6cc247f](https://github.com/SAP/stewardci-jenkinsfilerunner-image/releases/tag/200921_6cc247f) or later is required.
    pullRequestNumber: 151
    jiraIssueNumber: 1330