✨ scaffold(v4): add Alpha Update workflow to scaffold

[vitorfloriano]

This PR adds the Alpha Update workflow to the .github/workflows directory on the initial project scaffold.

The workflow:

1. Checks out the project.
2. Performs an update using the kubebuilder alpha update command
3. Pushes the changes to a new branch
4. Creates an Issue with a link for opening a PR using the new branch

The template:

name: Alpha Update
permissions:
  contents: write
  issues: write

on:
  workflow_dispatch:
  schedule:
    - cron: "0 0 * * 2" # Every Tuesday at 00:00 UTC

jobs:
  alpha-update:
    runs-on: ubuntu-latest
    env:
      GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

    steps:
    - name: Checkout repository
      uses: actions/checkout@v4
      with:
        token: ${{ secrets.GITHUB_TOKEN }}
        fetch-depth: 0
    
    - name: Configure Git
      run: |
        git config --global user.name "github-actions[bot]"
        git config --global user.email "github-actions[bot]@users.noreply.github.com"
    
    - name: Set up Go
      uses: actions/setup-go@v5
      with:
        go-version: stable

    - name: Install Kubebuilder
      run: |
        curl -L -o kubebuilder "https://go.kubebuilder.io/dl/latest/$(go env GOOS)/$(go env GOARCH)"
        chmod +x kubebuilder
        sudo mv kubebuilder /usr/local/bin/
        kubebuilder version

    - name: Run kubebuilder alpha update
      run: |
        kubebuilder alpha update \
          --force \
          --squash \
          --preserve-path .github/workflows \
          --open-gh-issue

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vitorfloriano
Once this PR has been reviewed and has the lgtm label, please assign camilamacedo86 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @vitorfloriano. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[camilamacedo86]

Just give a space / empty line at the end to fix the symbol

And is missing run make install and make generate to have all samples/docs re-generated within

[vitorfloriano]

And is missing run make install and make generate to have all samples/docs re-generated within

Doesn't alpha update already do that?

INFO Preparing Merge branch and performing merge branch_name=tmp-merge-15-08-25-11-41
...
INFO Running make manifests command=make manifests
...
...
INFO Running make generate command=make generate
...
...
INFO Running make fmt command=make fmt
...
...
INFO Running make vet command=make vet
...
...
INFO Running make lint-fix command=make lint-fix

[camilamacedo86]

The PR is created now manually; we need the URL for it.
Due this, could we remove from the default the --preserve-path?

[vitorfloriano]

GitHub Token does not have permission to alter the workflows directory by any means and it will fail to push the branch if we remove --preserve-path .github/workflows.

It's not only necessary for the PR. That's why I suggested we implement it internally, since it's mandatory for us.

[vitorfloriano]

See this workflow: https://github.com/vitorfloriano/test-operator/actions/runs/16989236871/workflow

And the error we get: https://github.com/vitorfloriano/test-operator/actions/runs/16989236871/job/48164585385#step:6:161

[camilamacedo86]

But if we create the URL for the PR without gh
AND then we create the PR is valid?

[vitorfloriano]

We first need to push the branch. If we are not able to push, we can't construct the URL.

With GITHUB_TOKEN, we can't push the branch if it has changes in the .github/workflows directory.

[vitorfloriano]

Also, we can't add workflows: write permisson to the workflow because that's not valid syntax. I've tried that.

We can only give permission to change workflows when we are creating a PAT or GitHub App.

See the available permissions for GITHUB_TOKEN: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#defining-access-for-the-github_token-scopes