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

Gh-236: Update GH actions #327

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Conversation

cn337131
Copy link
Member

@cn337131 cn337131 commented Jan 8, 2025

Updated the relevant GH actions. Also replaced the actions-ecosystem/action-get-latest-tag in the hotfix workflow.
Updated the release process to be the same as other Gaffer repos.

Related issue

@cn337131 cn337131 added the automation GitHub Actions, CI/CD label Jan 8, 2025
@cn337131 cn337131 added this to the v2.6.0 milestone Jan 8, 2025
@cn337131 cn337131 requested review from tb06904 and p29876 January 8, 2025 15:11
Copy link

sonarqubecloud bot commented Jan 8, 2025

@@ -60,3 +41,14 @@ jobs:
git checkout -b $BRANCH_NAME
git commit -a -m "prepare release $artifactId-$RELEASE_VERSION"
git push --set-upstream origin $BRANCH_NAME

- name: Tag release branch
Copy link
Member

Choose a reason for hiding this comment

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

Just to check, as the previous releases were tagged, I'm guessing that used to be done using the steps above which have been removed?

Copy link
Member

@tb06904 tb06904 Jan 9, 2025

Choose a reason for hiding this comment

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

I think the tags must have been applied manually the removed steps don't seem to have done any tagging they just worked out the version. The tagging was previously done by the release.yaml by the looks of it.

Copy link
Member

Choose a reason for hiding this comment

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

I don't recall them being applied manually - which is why I'd commented, but as you say there doesn't appear have been anything which did this. In any case, as it is now there won't be any other steps which could apply tags beyonf this one, so this should be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation GitHub Actions, CI/CD
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update GitHub Actions versions
4 participants