Skip to content

Conversation

rokatyy
Copy link
Contributor

@rokatyy rokatyy commented Sep 30, 2025

📝 Description

This PR updates the CI as follows:

  • On every release, a latest tag will now be published alongside the versioned tag.

  • Introduces a new workflow for marking a GA version as stable.
    This workflow re-tags the specified version’s images as stable, pushes them to the registry, and automatically opens a PR updating the stable badge in the README on GitHub. The PR description includes a note reminding maintainers to manually update the stable tag to the desired version. Manual action is required due to the issue described in #3826 (comment), where a Personal Access Token (PAT) is necessary for pushing changes that modify GitHub workflows.


✅ Checklist

  • I updated the documentation (if applicable)
  • I have tested the changes in this PR

🧪 Testing

gonna test after merge fully


🔗 References


🚨 Breaking Changes?

  • Yes (explain below)
  • No

@github-actions github-actions bot added the ci label Sep 30, 2025
Comment on lines 116 to 118
else
echo "::error::Version tag v${{ github.event.inputs.version }} does not exist in the repository."
exit 1
Copy link
Contributor

Choose a reason for hiding this comment

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

If the version doesn't exist, the previous step will fail in docker pull too, but I am not sure a docker pull failure will fail the step itself.
I suggest running the stable tag step first to ensure we fail fast if needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we can run them independently as it can be that for some reason one of tags somewhere isn't found(which is not likely, but technically is possible, so we can run again without thinking about the execution order)

@rokatyy rokatyy marked this pull request as draft October 3, 2025 09:48
@rokatyy
Copy link
Contributor Author

rokatyy commented Oct 3, 2025

During testing of my work I found out that if newest version contains workflow changes, github doesn't allow updating unless PAT is used:

To https://github.com/rokatyy/nuclio
 ! [remote rejected]     stable-update-1.14.4 -> stable-update-1.14.4 (refusing to allow a GitHub App to create or update workflow `.github/workflows/benchmark.yaml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/rokatyy/nuclio'

@rokatyy rokatyy marked this pull request as ready for review October 14, 2025 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants