Skip to content

Conversation

@adambkaplan
Copy link
Member

Changes

Update the release pipeline so it can accept a git reference, so that we can maintain release branches. See SHIP-0038.

Fixes #139

/kind feature

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

Add git reference as input to release pipeline workflow.

Update the release pipeline so it can accept a git reference, so that
we can maintain release branches. See SHIP-0038 [1].

[1] https://github.com/shipwright-io/community/blob/main/ships/0038-release-branching-backports.md

Assisted-by: Cursor
Signed-off-by: Adam Kaplan <[email protected]>
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 2, 2025
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 2, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

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

The pull request process is described here

Details 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

@adambkaplan adambkaplan added this to the release-v0.17.0 milestone Sep 2, 2025
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 2, 2025
@adambkaplan adambkaplan moved this to In Progress in Shipwright Overview Sep 2, 2025
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit f7d11f8 into shipwright-io:main Sep 8, 2025
8 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Shipwright Overview Sep 8, 2025
@adambkaplan adambkaplan deleted the release-pipeline-alignment branch September 8, 2025 13:04
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/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[FEATURE] Develop Release Pipeline

2 participants