(autohotkey.install) Package did not push to the repository

[DarthJake]

Checklist

• I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
• I have verified that this is happening in the latest available version of the package.

Chocolatey Version

2.3.0

Chocolatey License

None

Package Version

2.0.18

Current Behaviour

AutoHotkey (Install) 2.0.18 was pushed on 7/6, but was put into the "Waiting for Maintainer" state as the reviewer requested a note regarding the high virus count.

This was remedied in #2508, but it seems AU never repackaged and pushed the package to the community repository. Maybe because the remote version is the same as the version in the repository?

For the expansion of my own knowledge of AU, is this when you would use a commit message to tell AU to force update autohotkey.install with version 2.0.18? Or is there another better way this is done? Please let me know if I'm misunderstanding how something works.

Thank you very much!

Expected Behaviour

The updated package should be pushed to the community repository.

Steps To Reproduce

1. Look at autohotkey.install 2.0.18 on the community repo and see its in a 'waiting for maintainer' state
2. Look at the github repo and see that the requested changes were made

Environment

N/A

Chocolatey Log

N/A

Anything else?

No response

[github-actions]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue will be closed in 14 days if it continues to be inactive.

Please do not add a comment to circumvent automatic closure unless you plan to help move it forward.
Doing this may lead to the issue being closed immediately instead.

[github-actions]

Dear contributor,

As this issue seems to have been inactive for quite some time now, I've automatically closed it.
If you feel this is a valid issue, please feel free to re-open the issue if/when a pull request
has been added.
Thank you for your contribution.

[AdmiringWorm]

Re-opening this as it is still something we need to look at