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

Add a bump (and bump-bugfix) command to operator-tool #932

Merged
merged 3 commits into from
Jul 30, 2022

Conversation

vdemeester
Copy link
Member

@vdemeester vdemeester commented Jul 27, 2022

Changes

The idea is similar to the check subcommand, but it edits the
components.yaml with the latest found version (either bugfix or "in
general").

With this subcommand, we can have a cronjob and a "bot" that
automatically updates the versions of the main components.yaml
file. And we could have a similar one for the release branches.

/cc @sm43 @concaf @tektoncd/operator-maintainers

This is part of the effort to automate bumping payloads and release of the operator 👼🏼

/kind misc

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

NONE

@tekton-robot tekton-robot requested a review from concaf July 27, 2022 14:02
@tekton-robot tekton-robot added release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. kind/misc Categorizes issue or PR as a miscellaneuous one. labels Jul 27, 2022
@tekton-robot tekton-robot requested review from sm43 and a team July 27, 2022 14:02
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 27, 2022
@vdemeester
Copy link
Member Author

There is 2 commits that "showcase" a bump-bugfix and a bump 👼🏼
Next step, is a cronjob (or a github workflow or something) that run this periodically on this repository.

@vdemeester vdemeester force-pushed the operator-tool-add-bump-command branch 2 times, most recently from 0081247 to 3d0f505 Compare July 27, 2022 14:08
The idea is similar to the check subcommand, but it edits the
components.yaml with the latest found version (either bugfix or "in
general").

With this subcommand, we can have a cronjob and a "bot" that
automatically updates the versions of the main components.yaml
file. And we could have a similar one for the release branches.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester vdemeester force-pushed the operator-tool-add-bump-command branch from 3d0f505 to 3ae451b Compare July 27, 2022 14:13
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester vdemeester force-pushed the operator-tool-add-bump-command branch from 3ae451b to d19f61f Compare July 27, 2022 14:15
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. labels Jul 27, 2022
@sm43 sm43 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 28, 2022
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

@piyush-garg
Copy link
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 30, 2022
@tekton-robot tekton-robot merged commit 3c0ce51 into tektoncd:main Jul 30, 2022
@vdemeester vdemeester deleted the operator-tool-add-bump-command branch August 1, 2022 05:59
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/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants