Chains v1.0.0

[wlynch]

We want to cut a stable release for Chains.

Most of our actual feature set has been stable for some time - we don't expect any major changes to how chains operates.

However, there are still things we want to tackle before a v1 is cut, primarily around library stability and testing:

• Pipelines Regression Testing
  • Run e2e tests against different Pipeline versions #716
  • Add tests to catch changes in pipelines versions.
• The default builderID needs to be changed. #640 (Should we remove this from here?)
• Ensure Chains works with the v1 version of TaskRuns and PipelineRuns #665
• Limit client libraries for external usage #1044
• [rfc] Separate Chains controller system and userspace identities. #968
  • Needs a lot of effort. We may end up rushing this if we want this for v1. Instead we could add it as a feature that needs to be enabled.

Things that are not in scope:

• SLSA v1.0 support (additive feature)

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aaron-prindle]

Is it possible to re-open this? Seems it was auto-closed but some of the chains v1.0.0 TODO issues are still open.

[wlynch]

/reopen
/lifecycle froze

[tekton-robot]

@wlynch: Reopened this issue.

In response to this:

/reopen
/lifecycle froze

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[wlynch]

/lifecycle frozen

[aaron-prindle]

Created an issue for the client lib work:
#1044