Modernize GitHub Actions workflows for Node 20 deprecation and release-tag propagation#1167
Draft
Copilot wants to merge 2 commits into
Draft
Modernize GitHub Actions workflows for Node 20 deprecation and release-tag propagation#1167Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
Copilot created this pull request from a session on behalf of
hyphaltip
June 3, 2026 18:25
View session
Collaborator
|
@nextgenusfs I wanted to update the workflow for singularity deploy - do you want to look over this and see if is okay? |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR modernizes GitHub Actions workflows to address Node runtime deprecation warnings by upgrading legacy action versions and simplifying release-tag propagation for Docker image publishing workflows.
Changes:
- Upgraded deprecated GitHub Actions pins across Docker build, dispatch, and deployment workflows.
- Removed the legacy Node12-based “get latest release tag” helper by deriving tags from the triggering event or manual inputs.
- Added release tag propagation through
repository_dispatchpayloads for downstream release workflows.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/main.yml | Updates Docker build workflow action versions (checkout/docker/*/repository-dispatch). |
| .github/workflows/triggered-build.yml | Updates action versions for the repository-dispatch triggered Docker build. |
| .github/workflows/singularity-deploy.yml | Upgrades checkout and deployment/deployment-status actions used for Singularity deployment. |
| .github/workflows/release.yml | Refreshes Docker actions and replaces legacy release-tag helper with event/input-driven tag selection and dispatch payload propagation. |
| .github/workflows/release-triggered.yml | Refreshes Docker actions and switches tagging to consume the dispatched tag (with manual fallback). |
| .github/workflows/python-publish.yml | Updates checkout/setup-python action versions for PyPI publishing workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| file: ./Dockerfile | ||
| push: true | ||
| tags: nextgenusfs/funannotate-slim:${{ steps.get_release.outputs.tag_name }} | ||
| tags: nextgenusfs/funannotate-slim:${{ inputs.release_tag || github.event.release.tag_name }} |
| repository: nextgenusfs/funannotate | ||
| event-type: docker-hub-release-complete | ||
| client-payload: '{"ref": "${{ github.ref }}", "sha": "${{ github.sha }}"}' | ||
| client-payload: '{"ref": "${{ github.ref }}", "sha": "${{ github.sha }}", "tag": "${{ inputs.release_tag || github.event.release.tag_name }}"}' |
| file: ./Dockerfile2 | ||
| push: true | ||
| tags: nextgenusfs/funannotate:${{ steps.get_release.outputs.tag_name }} | ||
| tags: nextgenusfs/funannotate:${{ inputs.release_tag || github.event.client_payload.tag }} |
Comment on lines
23
to
27
| steps: | ||
| - uses: actions/checkout@v3 | ||
| - uses: actions/checkout@v6 | ||
| - name: Set up Python | ||
| uses: actions/setup-python@v3 | ||
| uses: actions/setup-python@v6 | ||
| with: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub Actions runs were emitting Node 20 deprecation and
set-outputwarnings from legacy action versions, with the singularity deploy workflow as the primary source. This PR updates deprecated action pins across workflows and removes the Node12-based release tag helper by switching to native event/input-driven tag propagation.Singularity deploy runtime upgrade
.github/workflows/singularity-deploy.yml:actions/checkout@v1→@v6chrnorm/deployment-action@releases/v1→@v2.0.8chrnorm/deployment-status@releases/v1→@v2.0.4Docker workflow action refresh
.github/workflows/main.yml.github/workflows/triggered-build.yml.github/workflows/release.yml.github/workflows/release-triggered.ymlactions/checkout→v6docker/login-action→v4docker/setup-buildx-action→v4docker/build-push-action→v7peter-evans/repository-dispatch→v4Removed legacy release-tag action (Node12)
kaliber5/action-get-release@v1in release workflows.release.ymlnow derives tag fromworkflow_dispatch.inputs.release_tagorgithub.event.release.tag_name.tag, andrelease-triggered.ymlconsumesgithub.event.client_payload.tag(withworkflow_dispatchfallback input).Python publish workflow modernization
.github/workflows/python-publish.yml:actions/checkout@v3→@v6actions/setup-python@v3→@v6