HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
majkinetor
au
PowerShell2019–2022
majkinetor / au · Archived

au

Chocolatey Automatic Package Updater Module

2Distinct people
5Mentions
0Explicit recommenders
224GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Chocolatey Automatic Package Updater Module

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2019-04-26 18:10:39 UTC to 2022-02-06 14:36:45 UTC.

0122019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

5 sources
Meh... Here is the exact case you mention, just WAY worst. This is something I did for chocolatey community: https://gist.github.com/choco-bot/a14b1e5bfaf70839b338eb1ab7... This page is report of the PowerShell framework I developed mostly in first year of development (https://github.com/majkinetor/au) that checks ~250 web sites for updates on various software. Today it has 6 errors and usually never much more. On my own location I keep ~60 packages and I I tackle errors maybe once a year. Stuff just work, and you rarely have to visit, otherwise I would be involved entire day into this and I am not, while those packages have many millions of users. Now I spend almost 0 time maintaining packages and I am one of the top choco package owners. Check out the options used, some of which make it so robust: https://github.com/chocolatey-community
Read the rest
/chocolatey-packages/... > It’s sources keep changing frequently, robust automation here is probably a research project and simple automation is orders of magnitude more bang for buck. Even if the source changes frequently its better to automate. Its not when it keeps changing daily or more then that. By automating you learn something new, so it pays more for your experience. Manually working every day the same thing (that may move around) doesn't involve complex thinking and is just waste of time.
In Ask HN: Best books on managing software complexity?
> I mean, it is a chocolatey, because they allow multiple packaged for the same software. I think this is more healthy then having one with maintainers refusing to do stuff you may need. The real thing would be for vendors releasing packages but we are far from that in Windows land. My hope for MS WinGet was that since it is backup from MS that vendors will adopt it, but since it sucks, this will probably not be the case. > I meant that packages are often not updated by the maintainers. Yeah, that was the problem far more before then today. I created AU to solve that issue [1]. [1]: https://github.com/majkinetor/au
In WinGet is terrible, I want AppGet back
Chocolatey is the only thing I use to install stuff both on CI and on each dev machine and I regularly create packages for it [1]. I worked hard to make what I need stable and not depend on their existence - [2] and all the repos using the same methodology release packages on GH [4] and there is a handy script to install from there. I also created AU for it [3] and managed to convince people to embed software in packages [5] so packages always work (you can cache them on your own via file system, artifactory, nexus etc). You can also host your own gallery in number of different ways. So, in short, there is escape plan. TBH, it looks like choco is going better then ever. And you can't simply find any better repository for sw, its better and more up to date then most linux package repos (on par with Arch). > I am not that into the way MS is
Read the rest
doing the winget thing, That is years away IMO, no scripting there too, and it moves like a snail. I would really be embarrassed if I were leading that team. > I see a lot of manual scripts for installing things on Windows CI systems Yeah, most people suck, like their scripts :-) There is literary 0 chance for you to make reliable installation script in general that works in any context. > I really like chocolatey but I am worried it will disappear soon. Just use it. I don't work for them. I maintain core team repo [2]. Its great tool now. What will happen tomorrow nobody knows but like I said, you have escape plan and even if they go down your CI will still work for many years if you set it up properly. --- [1] https://gist.github.com/majkinetor/a700c70b8847b29ebb1c918d4... [2] https://github.com/chocolatey-community/chocolatey-coreteamp... [3] https://github.com/majkinetor/au [4] https://github.com/majkinetor/au-packages/tags [5] https://github.com/chocolatey-community/chocolatey-coreteamp...
In Bash_unit – bash unit testing framework
I disagree. All GUI tools are limited and soon you get out of the comfort zone if you use them for more then 2 things. That is the main reason I created AU framework[^1] for chocolatey which main choco repo uses to daily watch and update 250+ packages[^2]. Previously they used Ketarin tool which is GUI and was very limited and hard to on-board too. Its basically this, but you program simple PowerShell functions that can check for changes using whatever available in .NET. The same goes for any declarative tool - you simply need a good programming language all the time. [^1] https://github.com/majkinetor/au [^2] https://gist.github.com/choco-bot/a14b1e5bfaf70839b338eb1ab7...
In WatchMe – Watch for Changes on a Page

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.