Chocolatey Community
Information about automic package updating #2451
-
|
Where can I find information about the automatic update process? The cause of this question is the nodejs package. I want to know more about the updating process. How is it triggered? Has someone be notified about a new version? What I found until now is:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
The automatic updates in this repository is using a module called Notifications about failures is sent to both common (private) emailing list, and is updated as part of the gist here: https://gist.github.com/choco-bot/a14b1e5bfaf70839b338eb1ab7f8226f In the terms of nodejs explicitly, it looks like it is failing due to getting the same binary for both 32bit and 64bit installers (and to prevent incompatible packages, it isn't updated in this case).
As this, this is a community maintained repository, the best option, no matter the situation, is to file an issue about the package being outdated (only for stable releases), or optionally provide a PR to address any issue that causes the package to not be updated. |
Beta Was this translation helpful? Give feedback.
-
I have updated those two links now to point to the correct location, thanks for bringing those to our attention. |
Beta Was this translation helpful? Give feedback.
-
|
Is the gist link somewhere linked? I couldnt find it. |
Beta Was this translation helpful? Give feedback.
-
|
It is yes. For the chocolatey-packages repository itself, it is listed in the Readme.md file in that repository (for other repositories, it can be different). There is a link called |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your answers and your time 😄 |
Beta Was this translation helpful? Give feedback.
The automatic updates in this repository is using a module called
Chocolatey-AU, and is triggered as part of a cron job on AppVeyor (I forget how often, but several times a day). We can trigger a forced update of a package, but this is generally not done.Notifications about failures is sent to both common (private) emailing list, and is updated as part of the gist here: https://gist.github.com/choco-bot/a14b1e5bfaf70839b338eb1ab7f8226f
In the terms of nodejs explicitly, it looks like it is failing due to getting the same binary for both 32bit and 64bit installers (and to prevent incompatible packages, it isn't updated in this case).
As this, this…