IBX-11778: Updated deprecated GitHub Actions in auto_tag workflow#286
Draft
alongosz wants to merge 4 commits into
Draft
IBX-11778: Updated deprecated GitHub Actions in auto_tag workflow#286alongosz wants to merge 4 commits into
alongosz wants to merge 4 commits into
Conversation
Aligned with the IBX-11778 treatment from ibexa/gh-workflows#103, adjusted for metapackages: - Bumped actions/create-github-app-token from v2 to v3, switching the deprecated app-id input to client-id - Replaced tibdex/github-app-token@v1 with actions/create-github-app-token@v3 in the action job - Replaced octokit/request-action with equivalent gh api calls, preserving the data output consumed by later steps - Bumped actions/checkout to v7 and both jobs to ubuntu-26.04 - Removed steps guarded by other editions' repository names (the file was designed to be copy-pasted between edition repositories, but the copies have since diverged) and the unused cs2pr tool. Headless deliberately does not wait for its parent package (ibexa/oss), which is available on Packagist, not via Satis; a comment now records that Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 21, 2026
The Commit, tag and push step used the EZROBOT_PAT personal access token and rewrote the origin remote URL to embed it, while the job already generates a GitHub App installation token. Now: - the push step receives the app token via its GITHUB_TOKEN env and authenticates git through gh auth setup-git (gh acting as the git credential helper), keeping the whole credential flow local to the step - checkout stays credential-free and no secret is written to .git/config - the release commit is authored as github-actions[bot] instead of ezrobot, which no longer plays any role here - inputs.version is passed to the shell via the step's VERSION env instead of raw workflow-expression interpolation Note before merging: this path only runs with real_op: true, so PR CI does not exercise it. The automation GitHub App must have contents write permission and any tag protection allowances previously granted to the ezrobot account. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Create Tag workflow now keeps only its edition-specific data and delegates the mechanics to two composite actions in ibexa/gh-workflows: - check-composer-package (preparation) checks that the required package version is available on the Composer repository that composer update will actually consume — more accurate than the previous GitHub-tag probe, which could pass while the package was not yet installable; - create-metapackage-tag (action) fetches the release definition, derives minimum stability, pins the parent/assets packages, patches require versions, updates composer.lock and, with real_op, commits, tags and pushes using the GitHub App token. Behavior is unchanged apart from the more accurate preparation check and the dropped sponge/moreutils dependency. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Allows testing the new composite actions before the ibexa/gh-workflows pull request that introduces them is merged. Drop before merging. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Caution
Related PRs:
Description:
Upgraded or replaced the GitHub Actions in the
auto_tag.ymlworkflow that still run on the deprecated Node.js 20 runtime (to be removed from GitHub runners on September 16th, 2026):actions/create-github-app-tokenfrom v2 to v3, switching the deprecatedapp-idinput toclient-id;tibdex/github-app-token@v1withactions/create-github-app-token@v3in theactionjob;octokit/request-action@v2.xusages with equivalentgh apicalls, preserving thedataoutput consumed by later steps;actions/checkoutto v7 and both jobs to theubuntu-26.04runner;cs2prtool. Headless deliberately does not wait for its parent package (ibexa/oss), which is available on Packagist, not via Satis; a comment now records that.EZROBOT_PAT(ezrobot personal access token) in theCommit, tag and pushstep with the GitHub App token the job already generates: the step authenticates git throughgh auth setup-gitwith the token in its env — the credential flow stays local to the step and no secret is written into the remote URL /.git/config. The release commit is now authored asgithub-actions[bot], andinputs.versionis passed to the shell via the step env instead of raw workflow-expression interpolation.All other workflows in this repository only call
ibexa/gh-workflows/...@mainreusable workflows (deliberately trunk-tracking, already covered by ibexa/gh-workflows#103) and required no changes.Update: the workflow has since been refactored on this branch to use the shared composite actions from ibexa/gh-workflows#105 (
check-composer-package+create-metapackage-tag) — the file now keeps only edition-specific data. The preparation check now queries the Composer repository (Packagist/Satis) thatcomposer updateactually consumes, instead of probing for a GitHub tag. A[TMP]commit points the action references at the gh-workflows feature branch for testing; it must be dropped before merging.For QA:
No manual QA required. The workflow can be validated by dispatching Create Tag with
real_op: false(dry run — no tag is pushed) once a suitablerelease.jsonexists in ibexa/release-maker.Before merging: the
Commit, tag and pushpath only runs withreal_op: true, so PR CI does not exercise it — verify the automation GitHub App has contents write permission and any tag protection allowances previously granted to the ezrobot account.Documentation:
No documentation required.