nektos
Github extension does not upgrade
Bug report info
Act notifies of an update being available, but does not upgrade.
INFO ️ 📣 A newer version of 'act' is available - consider ugrading to 0.2.71.
[origin tagging-and-releases][🅰 pbs-digi-preprod][tagging-and-releases]
[2025-01-03 15:23:54]» gh extension upgrade --all
[act]: already up to date
[copilot]: already up to date
[sbom]: upgraded from v0.0.10 to v0.1.0
[worktree]: already up to date
✓ Successfully checked extension upgrades
[origin tagging-and-releases][🅰 pbs-digi-preprod][tagging-and-releases]
[2025-01-03 15:23:58]» gh act --version
act version 0.2.70
[origin tagging-and-releases][🅰 pbs-digi-preprod][tagging-and-releases]
[2025-01-03 15:24:08]»
Command used with act
The command that ended with a notice regarding a new version:
[2025-01-03 15:24:08]» gh act workflow_call --rebuild -s GITHUB_TOKEN=XXXXX -e inputs_tag.json --secret-file .env --var-file
.env --env-file .env -W .github/workflows/_tag.yml
The command I used in an attempt to upgrade:
gh extension upgrade --all
Describe issue
Act notifies of an update being available, but does not upgrade when gh extension upgrade --all is issued.
Link to GitHub repository
No response
Workflow content
N/A
Relevant log output
N/A
Additional information
[2025-01-03 15:29:30]» gh extension list
NAME REPO VERSION
gh act nektos/gh-act v0.2.70
gh copilot github/gh-copilot v1.0.5
gh sbom advanced-security/gh-sbom v0.1.0
gh worktree despreston/gh-worktree v1.0.0
[origin tagging-and-releases][🅰 pbs-digi-preprod][tagging-and-releases]
[2025-01-03 15:29:41]» gh extension upgrade act
[act]: already up to date
✓ Successfully checked extension upgrades
[origin tagging-and-releases][🅰 pbs-digi-preprod][tagging-and-releases]
[2025-01-03 15:29:46]» gh extension upgrade --force act
[act]: already up to date
✓ Successfully checked extension upgrades
[origin tagging-and-releases][🅰 pbs-digi-preprod][tagging-and-releases]
[2025-01-03 15:29:53]»
Fixed now in https://github.com/nektos/gh-act/pull/12? please try again and if this is resolved close as completed.
I recommend you to take more care about sanitizing Personal Access Tokens or other Secrets in bug reports that has been removed by us, since this is a public issue tracker everyone could abuse it if GitHub didn't notify you about revoking it via GitHub Advanced Security
Thank you for the admonition, I will delete the token now.
Also, for what it's worth, I was able to update using this command: gh extension upgrade act
[2025-01-06 16:07:17]» gh extension upgrade act
[act]: upgraded from v0.2.70 to v0.2.71
✓ Successfully checked extension upgrades
@ChristopherHX I'm still seeing this:
INFO ️📣 A newer version of 'act' is available - consider ugrading to 0.2.77.
Just installed the gh extension and see:
$ gh extension upgrade --agh extension upgrade --all
[ act]: already up to date
✓ Successfully checked extension upgrades
But I am still on v0.2.76:
NAME REPO VERSION
gh act nektos/gh-act **v0.2.76**
Possibly the gh extension updates lag the releases a bit?
Possibly the gh extension updates lag the releases a bit?
Yes v0.2.77 was skipped to due lack of in time reviews of critical release pipeline bug fixes created my me.
TBH v0.2.77 changelog was almost empty.
Now you should have v0.2.78 available.
Thanks, yes I was able to upgrade to v0.2.78:
$ gh extension upgrade nektos/gh-act
[act]: already up to date
✓ Successfully checked extension upgrades
$ gh extension list
NAME REPO VERSION
gh act nektos/gh-act v0.2.78