starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00

[GH-ISSUE #2600] Github extension does not upgrade #1184

New issue

Open

opened 2026-03-01 21:49:31 +03:00 by kerem · 5 comments

kerem commented

2026-03-01 21:49:31 +03:00

Owner

Originally created by @socketbox on GitHub (Jan 3, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/2600

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]»

Originally created by @socketbox on GitHub (Jan 3, 2025). Original GitHub issue: https://github.com/nektos/act/issues/2600 ### Bug report info Act notifies of an update being available, but does not upgrade. ```sh 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: ```sh [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 ```yml N/A ``` ### Relevant log output ```sh N/A ``` ### Additional information ```sh [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]» ```

kerem added the

kind/bug

label

2026-03-01 21:49:31 +03:00

kerem commented

2026-03-01 21:49:32 +03:00

Author

Owner

@ChristopherHX commented on GitHub (Jan 5, 2025):

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

@ChristopherHX commented on GitHub (Jan 5, 2025): 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_

kerem commented

2026-03-01 21:49:32 +03:00

Author

Owner

@socketbox commented on GitHub (Jan 6, 2025):

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

@socketbox commented on GitHub (Jan 6, 2025): 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 ```

kerem commented

2026-03-01 21:49:32 +03:00

Author

Owner

@jordanblakey commented on GitHub (Jun 1, 2025):

@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?

@jordanblakey commented on GitHub (Jun 1, 2025): @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?

kerem commented

2026-03-01 21:49:32 +03:00

Author

Owner

@ChristopherHX commented on GitHub (Jun 1, 2025):

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.

@ChristopherHX commented on GitHub (Jun 1, 2025): > 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.

kerem commented

2026-03-01 21:49:32 +03:00

Author

Owner

@jordanblakey commented on GitHub (Jun 1, 2025):

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

@jordanblakey commented on GitHub (Jun 1, 2025): 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 ```

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1184

No description provided.

Rows
Columns