Skip to content

Latest commit

 

History

History
239 lines (147 loc) · 5.99 KB

release-notes.hbs.md

File metadata and controls

239 lines (147 loc) · 5.99 KB
Raw

Release notes

{{#unless vars.hide_content}} This Handlebars condition is used to hide content. In release notes, this condition hides content that describes an unreleased patch for a released minor. {{/unless}} This topic contains release notes for Tanzu Application Platform v1.3

v1.3.0

Release Date: MONTH DAY, 2022

New features

This release includes the following changes, listed by component and area.

Application Accelerator

  • Feature 1
  • Feature 2

Application Live View

  • Feature 1
  • Feature 2

Application Single Sign-On

  • Feature 1
  • Feature 2

Tanzu CLI - Apps plug-in

  • Feature 1
  • Feature 2

Source Controller

  • Feature 1
  • Feature 2

Snyk Scanner (beta)

  • Feature 1
  • Feature 2

Supply Chain Choreographer

  • Feature 1
  • Feature 2

Supply Chain Security Tools - Scan

  • Feature 1
  • Feature 2

Supply Chain Security Tools - Sign

  • Feature 1
  • Feature 2

Supply Chain Security Tools - Policy Controller

  • Feature 1
  • Feature 2

Supply Chain Security Tools - Store

  • Feature 1
  • Feature 2

Tanzu Application Platform GUI

  • Supply Chain plug-in:
    • Added ability to visualize CVE scan results in the Details pane for both Source and Image Scan stages, as well as scan policy information without using the CLI.
    • Added ability to visualize the deployment of a workload as a deliverable in a multicluster environment in the supply chain graph.
    • Added a deeplink to view approvals for PRs in a GitOps repository so that PRs can be reviewed and approved, resulting in the deployment of a workload to any cluster configured to accept a deployment.
    • Added Reason column to the Workloads table to indicate causes for errors encountered during supply chain execution.
    • Added links to a downloadable log output for each execution of the Test and Build stages of the out of the box supply chains to enable more enhanced troubleshooting methods for workloads

Tanzu Developer Tools for VS Code

  • Feature 1
  • Feature 2

Tanzu Developer Tools for IntelliJ

  • Feature 1
  • Feature 2

Functions (beta)

  • Feature 1
  • Feature 2

Tanzu Build Service

  • Feature 1
  • Feature 2

Services Toolkit

  • Feature 1
  • Feature 2

Breaking changes

This release has the following breaking changes, listed by area and component.

Supply Chain Security Tools - Scan

  • Breaking change 1
  • Breaking change 2

Tanzu Build Service

  • Breaking change 1
  • Breaking change 2

Grype Scanner

  • Breaking change 1
  • Breaking change 2

Resolved issues

  • Resolved issue 1
  • Resolved issue 2

Application Accelerator

  • Resolved issue 1
  • Resolved issue 2

Supply Chain Security Tools - Scan

  • Resolved issue 1
  • Resolved issue 2

Grype Scanner

  • Resolved issue 1
  • Resolved issue 2

Tanzu CLI - Apps plug-in

  • Resolved issue 1
  • Resolved issue 2

Services Toolkit

  • Resolved issue 1
  • Resolved issue 2

Service Bindings

  • Resolved issue 1
  • Resolved issue 2

Spring Boot Conventions

  • Resolved issue 1
  • Resolved issue 2

Tanzu Application Platform GUI

  • Resolved issue 1
  • Resolved issue 2

Known issues

This release has the following known issues, listed by area and component.

Tanzu Application Platform

  • Known issue 1
  • Known issue 2

Application Live View

  • Known issue 1
  • Known issue 2

Application Single Sign-On

  • Known issue 1
  • Known issue 2

Convention Service

  • Known issue 1
  • Known issue 2

Functions (beta)

  • Known issue 1
  • Known issue 2

Supply Chain Security Tools - Scan

  • Known issue 1
  • Known issue 2

Grype scanner

Scanning Java source code that uses Gradle package manager may not reveal vulnerabilities:

  • For most languages, Source Code Scanning only scans files present in the source code repository. Except for support added for Java projects using Maven, no network calls are made to fetch dependencies. For languages using dependency lock files, such as Golang and Node.js, Grype uses the lock files to check the dependencies for vulnerabilities.

  • For Java using Gradle, dependency lock files are not guaranteed, so Grype uses the dependencies present in the built binaries (.jar or .war files) instead.

  • Because VMware does not encourage committing binaries to source code repositories, Grype fails to find vulnerabilities during a Source Scan. The vulnerabilities are still found during the Image Scan after the binaries are built and packaged as images.

Tanzu Application Platform GUI

  • Known issue 1
  • Known issue 2

VS Code Extension

  • Known issue 1
  • Known issue 2

Intellij Extension

  • Known issue 1
  • Known issue 2

Supply Chain Security Tools - Store

  • Known issue 1
  • Known issue 2