Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating release doc with recent releases #6821

Merged
merged 1 commit into from
Jun 16, 2023

Conversation

vdemeester
Copy link
Member

Changes

This updates the release.md document with the most recent versions.

This should probably be generated (and auto-updated as well) as it seems a bit tedious to maintain — probably why it was not up-to-date 🙃 @tektoncd/core-maintainers

/kind docs

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

@tekton-robot
Copy link
Collaborator

@vdemeester: The label(s) kind/docs cannot be applied, because the repository doesn't have them.

In response to this:

Changes

This updates the release.md document with the most recent versions.

This should probably be generated (and auto-updated as well) as it seems a bit tedious to maintain — probably why it was not up-to-date 🙃 @tektoncd/core-maintainers

/kind docs

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

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.

@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Jun 13, 2023
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 13, 2023
@vdemeester
Copy link
Member Author

/kind doc

@tekton-robot
Copy link
Collaborator

@vdemeester: The label(s) kind/doc cannot be applied, because the repository doesn't have them.

In response to this:

/kind doc

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.

@vdemeester
Copy link
Member Author

/kind documentation

@tekton-robot tekton-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Jun 13, 2023
Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @vdemeester - it's part of the release manager duty to update this, but yeah, ideally we should automate it. I think if we start doing planned patch releases it will become easier to maintain as well.
/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 13, 2023
releases.md Outdated Show resolved Hide resolved
releases.md Outdated Show resolved Hide resolved
@lbernick
Copy link
Member

ty @vdemeester! would you mind squashing the commits?

@afrittoli
Copy link
Member

I think the missed updates were my fault because I forgot to update my own PR #6583

@afrittoli
Copy link
Member

I'll close my PR as superseded by this one.

@afrittoli afrittoli mentioned this pull request Jun 16, 2023
7 tasks
This updates the release.md document with the most recent versions.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
Co-authored-by: Lee Bernick <leebernick@google.com>
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester
Copy link
Member Author

@lbernick squashed 👼🏼

@lbernick
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2023
@tekton-robot tekton-robot merged commit cb2248f into tektoncd:main Jun 16, 2023
@vdemeester vdemeester deleted the update-release-doc branch June 16, 2023 14:01
@chuangw6 chuangw6 mentioned this pull request Jun 16, 2023
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants