Workflow to release midstream plugin

[aliok]

• Workflow to release midstream plugin
• Publishing to GitHub packages
• Uses a PAT from myself

Tested here: https://github.com/aliok/backstage-plugins-no-fork-test/

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[pierDipi]

can we append the short commit sha instead of the datetime?

[aliok]

I think commit hash alone is not good, but I can add it to the end like release-1.2.3-202401010101-deadbeef

[pierDipi]

why is not good?

[pierDipi]

Also the - is an indicator of pre-releases, I think what we want is the build identifier with a +, eg 1.33.0+<buid-id>

[pierDipi]

I'm also wondering if we should increment the patch version versus pre-releases or build numbers

[pierDipi]

I think we can also list versions and figure out what's the "next patch for a major.minor" ?

[aliok]

Yeah, all commits in a release branch would cause a new package being published.

[pierDipi]

BASE_RELEASE_NAME="0.1"; npm view @knative-extensions/plugin-knative-event-mesh-backend versions --json | grep ${BASE_RELEASE_NAME} | tail -1 | tr -d '"' | awk -F \. '{print $3+1}'

This will give us the next patch version for @knative-extensions/plugin-knative-event-mesh-backend package, which is 3, given the BASE_RELEASE_NAME being 0.1

[aliok]

Ok, what can go wrong, right? :D Let me incorporate this

[pierDipi]

A lot can go wrong :) but I think it's a little better

for sure we need to add the concurrency https://docs.github.com/en/actions/using-jobs/using-concurrency as a follow up

[pierDipi]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, pierDipi

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:

• OWNERS [aliok,pierDipi]

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

[pierDipi]

/test all

[pierDipi]

Pipeline failed https://github.com/openshift-knative/backstage-plugins/actions/runs/9018345667/job/24778750006

go: modules disabled by GO111MODULE=off; see 'go help modules'
Error: Process completed with exit code 1.

[aliok]

Sorry, my bad. This wasn't ready!

I wrote you in private that I will test stuff locally before merging, but didn't add a hold.

Reverting now.