Skip to content

ci: drop arm64 from release builds, opt into Node 24, bump timeout #132

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.

Sign up for GitHub

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

Merged
rg4444 merged 1 commit into from
May 23, 2026
Merged

ci: drop arm64 from release builds, opt into Node 24, bump timeout #132

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,11 +30,18 @@ concurrency:
group: release-${{ github.ref }}
cancel-in-progress: false

# Opt into Node 24 for JavaScript-based actions ahead of GitHub's June 2026
# default switch. Suppresses the deprecation warning emitted for actions
# that still ship Node 20 bindings (setup-go, docker/*, etc.). When the
# default flips in June 2026 this line becomes a no-op and can be removed.
env:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"

jobs:
release:
name: Build, sign, publish
runs-on: ubuntu-24.04
timeout-minutes: 60
timeout-minutes: 90

steps:
- name: Checkout
Expand Down Expand Up @@ -108,7 +115,7 @@ jobs:
with:
context: .
file: deploy/Dockerfile.processgit
platforms: linux/amd64,linux/arm64
platforms: linux/amd64
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 23, 2026

Choose a reason for hiding this comment

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

P2 Badge Keep published release notes in sync with built platforms

After changing the build platform to linux/amd64 here, the release-notes generator in the same workflow still hardcodes both linux/amd64 and linux/arm64 in its output (see the Generate release notes step around lines 333–336). On every tagged release this will advertise arm64 support that is no longer built, so arm64 users can follow the notes and hit a missing-manifest pull failure. Please update the notes generation to use the same platform source as the build/release metadata.

Useful? React with 👍 / 👎.

push: ${{ github.event_name == 'push' || inputs.dry_run == false }}
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
Expand Down Expand Up @@ -184,7 +191,7 @@ jobs:
with:
context: updater
file: updater/Dockerfile
platforms: linux/amd64,linux/arm64
platforms: linux/amd64
push: ${{ github.event_name == 'push' || inputs.dry_run == false }}
tags: ${{ steps.meta_updater.outputs.tags }}
labels: ${{ steps.meta_updater.outputs.labels }}
Expand Down Expand Up @@ -251,7 +258,7 @@ jobs:
IMAGE_REGISTRY: ghcr.io
IMAGE_REPOSITORY: algomation-ai/processgit
IMAGE_DIGEST: ${{ steps.build.outputs.digest }}
IMAGE_PLATFORMS: linux/amd64,linux/arm64
IMAGE_PLATFORMS: linux/amd64
SIGNING_ISSUER: https://token.actions.githubusercontent.com
SIGNING_IDENTITY_REGEX: '^https://github.com/Algomation-AI/ProcessGit/\.github/workflows/release\.yml@.*'
RELEASE_NOTES_URL: https://github.com/${{ github.repository }}/releases/tag/${{ steps.version.outputs.tag }}
Expand Down
Loading