build: Add codecov token (#1373)

.github/workflows/e2e-cli.yml

@@ -37,6 +37,8 @@ jobs:
         run: bin/ratify version
       - name: Upload coverage to codecov.io
         uses: codecov/codecov-action@7afa10ed9b269c561c2336fd862446844e0cbf71 # v4.2.0
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
       - name: Run helm lint
         run: helm lint charts/ratify
   build_test_cli:
@@ -63,6 +65,8 @@ jobs:
           make test-e2e-cli GOCOVERDIR=${GITHUB_WORKSPACE}/test/e2e/.cover
       - name: Upload coverage to codecov.io
         uses: codecov/codecov-action@7afa10ed9b269c561c2336fd862446844e0cbf71 # v4.2.0
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
   markdown-link-check:
       runs-on: ubuntu-latest
       steps:

ROADMAP.md

@@ -0,0 +1,95 @@
+# Roadmap
+
+## Overview
+
+At Ratify, our mission is to safeguard the container supply chain by ratifying trustworthy and compliant artifacts. We achieve this through a robust and pluggable verification engine that includes built-in verifiers. These verifiers can be customized to validate supply chain metadata associated with artifacts, covering essential aspects such as signatures and attestations (including vulnerability reports, SBOM, provenance data, and VEX documents). As the landscape of supply chain security evolves, we actively develop new verifiers, which can be seamlessly integrated into our verification engine. Additionally, if you have a specific use case, you can create your own verifier following our comprehensive guidance. Each verifier will generate detailed verfication reports, which can be consumed by various policy controllers to enforce policies.
+
+Ratify is designed to address several critical scenarios. It seamlessly integrates with OPA Gatekeeper, acting as the Kubernetes policy controller that shields your cluster from untrustworthy and non-compliant container images. As an external data provider for Gatekeeper, Ratify delivers artifact verification results that are in alignment with defined policies. Additionally, Ratify enhances security at the Kubernetes node level by extending its capabilities to container runtime through its plugin interface, which allows for detailed policy evaluations based on artifact verification outcomes. Lastly, incorporating Ratify into your CI/CD pipeline ensures the trustworthiness and compliance of container images prior to their usage.
+
+This document presents the roadmap of Ratify that translates our strategy into practical steps.
+
+## Milestones
+
+The Ratify roadmap is divided into milestones, each with a set of features (high level) and timeline. The milestones marked as `Tentative` are subject to change based on the project’s priorities and the community’s feedback. We will prioritize releases for security or urgent fixes, so the roadmap may be adjusted and new features may be postponed to the next milestone. Any dates and features listed below in a given milestone are subject to change. See the [GitHub milestones](https://github.com/deislabs/ratify/milestones?state=open) for the most up-to-date issues and their status. We are targeting to release a new Ratify version every 3 or 4 months.
+
+### v1.0
+
+**Status**: Completed
+
+**Released date**: Sep 27, 2023
+
+**Release link**: [v1.0.0 Release Notes](https://github.com/deislabs/ratify/releases/tag/v1.0.0)
+
+**Major features**
+
+- Ratify as an external Data Provider for Gatekeeper
+- Plugin framework for extensibility
+- Policies for Notary Project signatures verification at admission control in kubernetes
+- Policies for Cosign keyless verification at admission control in kubernetes
+- High Availability support in Kubernetes (Experimental)
+
+### v1.1
+
+**Status**: Completed
+
+**Release date**: Dec 12, 2023
+
+**Release link**: [v1.1.0 Release Notes](https://github.com/deislabs/ratify/releases/tag/v1.1.0)
+
+**Major features**
+
+- Policies for assessing vulnerability reports at admission control in kubernetes
+- Policies for assessing software license at admission control in kubernetes
+- New diagnostic logs
+
+### v1.2
+
+**Status**: In progress
+
+**Target date**: Apr 30, 2024
+
+**major features**
+
+- Kubernetes multi-tenancy support (Namespace-specific policies)
+- OCI v1.1 compliance
+- Cosign signatures verification using keys in AKV
+- Error logs improvements
+
+See details in [GitHub milestone v1.2.0](https://github.com/deislabs/ratify/issues?q=is%3Aopen+is%3Aissue+milestone%3Av1.2.0).
+
+### v1.3
+
+**Status**: Not started
+
+**Target date**: Jun 30, 2024
+
+**Major features**
+
+- Kubernetes multi-tenancy support (Verifying Common images across namespaces)
+- Cosign keyless verification using OIDC settings
+- Notary Project signature verification with Time-stamping support
+- Signing Certificate/key rotation support
+
+See details in [GitHub milestone v1.3.0](https://github.com/deislabs/ratify/issues?q=is%3Aopen+is%3Aissue+milestone%3Av1.3.0).
+
+### v1.4
+
+**Status**: Tentative
+
+**Target date**: Sep 30, 2024
+
+**Major features**
+
+- Attestations support
+- Use Ratify at container runtime (Preview)
+
+### v2.0
+
+Status: Tentative
+
+Target date: TBD
+
+**Major features**
+
+- Use Ratify in CI/CD pipelines (Preview)
+- Support CEL as additional policy language