NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #3176 by repository stars
Latest stable
v0.11.10
Last release 3 months ago
03 Aug 2026
Ships unpredictably
gaps range from 9 days to 6.0 years
Nearly every release is documented
notes for 35 of 35 stable releases
Nothing withdrawn
no release was ever pulled
13 years old
104 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
This announcement actually includes the info from both the 0.11.10 release and the 0.11.9 release as well. For a small variety of reasons, including t
This announcement actually includes the info from both the 0.11.10 release and the 0.11.9 release as well. For a small variety of reasons, including the fact that these past two releases were both pretty small and because I've been cranking on the Chef Server 12 support lately, I never got around to drafting formal releases and binaries. At last, here they are. There's a fix to remove a dependency that was being removed from Debian, and two small changes to support newer versions of the chef tools.
From the CHANGELOG:
0.11.10
-------
* It was brought to my attention by @joerg that 'create_key' is now a valid JSON
hash key for when creating clients with newer chef tools. Added it to the
whitelist of valid elements for creating clients. Thanks again for bringing
it to my attention.
0.11.9
------
* Follow chef RFC041. Newer chef-clients and knifes (knives?) were breaking
goiardi wasn't following this RFC by reporting the supported api versions.
(Thanks julian7 for the PR and bringing it to my attention.)
* Remove dependency on golang.org/x/exp/utf8string - it's failing some tests on
the Debian build servers, and goiardi's liable to get kicked out of testing
shortly if it isn't addressed. Since goiardi wasn't actually using utf8string
for anything real complicated, it was easy enough to tear that out and whip
up a replacement with built-in functions. (Thanks jordi for bringing this
situation to my attention as well.)
Your coding agent can read these notes before it upgrades. Set up the MCP server →
And commit the CHANGELOG update from last night - these commits were …
And commit the CHANGELOG update from last night - these commits were …
Nothing published for this version
While there are other sticks in the fire, both goiardi related and otherwise, here's another release with tweaks and improvements to brighten the days
While there are other sticks in the fire, both goiardi related and otherwise, here's another release with tweaks and improvements to brighten the days of anyone who happens to use goiardi.
From the CHANGELOG:
* Made some small tweaks and updates to the depsolver to make that a little
better. NB: Down the road, there may be some further changes to the depsolver,
especially where 'most constrained' cookbooks are concerned.
* Update the circleci config to use the version 2.0 syntax.
* Add purging old sandboxes that have been hanging around for too long.
Add purge-sandboxes-after option to sample config file, update help a…
Add purge-sandboxes-after option to sample config file, update help a…
Nothing published for this version
Yet another bugfix release that was brewing for an awfully long time, but the fixes in this release improve memory usage, the sizes of some database t
Yet another bugfix release that was brewing for an awfully long time, but the fixes in this release improve memory usage, the sizes of some database tables by allowing more control over how long to keep reports and node statuses and how much information to store in the event log tables, handle some of the more unusual search types I didn't even know anyone used with Chef, and more.
From the CHANGELOG:
* Allow access to /debug/pprof with a whitelist of IP addresses
* Properly index arrays of hashes, arrays of arrays, etc. in object attributes.
* Pretty serious memory usage improvements with search (both the in-memory
and postgres searches).
* Fix reconnecting to serf if the connection is somehow interrupted.
* Fix negated range queries (it turns out they *do* have a use after all), and
refactor how NOT queries are handled generally.
* Add options to purge old reports and node statuses.
* Add option to skip logging extended object information in the event log.
* A handful of other bugfixes.
* Bump up to using golang 1.9.3 for builds.
* Minor changes to the documentation.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
There's just some search fixes in this release. Important, but not especially interesting.
There's just some search fixes in this release. Important, but not especially interesting.
From the CHANGELOG:
* Several search fixes:
- With postgres search:
* Fixed reindexing after it broke with the previous update that eliminated
a lot of unneeded extra rows in the database.
* Fixed basic queries with NOT statements.
* Separately, fixed using NOT with subqueries. On a somewhat complicated
note, but in a way that appears to match standard Solr behavior, when
doing a query like "name:chef* AND NOT (admin:true OR admin:bleh)" it
works as is, but when a negated subquery is followed by another basic
query statement, it needs to have extra parentheses around the NOT +
subquery, like "name:chef* AND (NOT (admin:true OR admin:bleh)) AND
public_key:*". A convoluted and unlikely scenario, but it could happen.
- With in-memory search:
* NOT + subqueries was also broken with the in-mem search. The fixes for
the pg-search partially fixed it for in-mem in that it no longer made the
server panic, but it was returning incorrect results. Additional work
ended up being needed for in-mem search.
Nothing published for this version
Nothing published for this version
Mostly internal changes here that don't radically affect normal usage. The biggest change from an external perspective is that goiardi now supports Ch
Mostly internal changes here that don't radically affect normal usage. The biggest change from an external perspective is that goiardi now supports Chef auth v1.3, and many endpoints will respond to HEAD requests with the same HTTP status code as they would respond to a GET request (even if it might not be a particularly sensible response). Otherwise these changes are mostly done with the future in mind.
From the CHANGELOG:
* Move the custom goiardi error type out of util and into its own module.
Wrappers around the new module are in util still for convenience, and
because the functions and interface are used all over the place.
* Many endpoints now handle HEAD requests where appropriate. With some
endpoints this is not especially useful, but with others it's a lightweight
way to see what resources exist and so forth. Implements Chef RFC 090.
* Start using contexts with requests. This does mean that goiardi will require
at least go 1.7. (As of 0.11.3 goiardi only supported go 1.7+, but it was
likely to build with somewhat older versions anyway.)
* Minor bugfixes - deal with a possible race condition with the in-mem search
index, change some logging statements from Info to Debug that didn't need to
be Info level and removed a test log statement that was no longer necessary,
updated copyright dates.
* Add the Chef API version header to responses.
* Change behavior if the data file and use-(mysql|postgresql) are specified
together; formerly it was a fatal error, but now it'll just emit a warning
in the error log and ignore the data file setting.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Mark --use-unsafe-mem-store as deprecated. In the unlikely event someone's using that option, a warning will print in the log. This option may be remo…
Mostly housekeeping this time, but it's good housekeeping. There's one fairly important bug fix where, if you had arrays with duplicate items in objects being indexed, goiardi would crash trying to index it. Surprisingly, this didn't come up very often. Also, it was surprisingly difficult to duplicate the crash, with lots of false starts and ideas.
Otherwise, the biggest things are new command line flags so you can configure MySQL or Postgres without using the config file, being able to configure almost all command line flags via environment variables now (which should make running goiardi in docker a bit easier), and optionally trimming the length of values in objects stored in the index. Other than that, there was some documentation cleanup and tweaks to packaging.
From the CHANGELOG:
* Add an option to trim values in search indexes. Currently not enabled by
default, but will be in the next minor goiardi release (so, either 0.12.0 or
1.0.0, depending on which ends up being next). Existing indexes ought to be
reindexed upon upgrading, but they should still work if this is skipped.
* Fix a bug where duplicated items in slices in objects being indexed with the
in-memory trie based index would cause goiardi to crash. For good measure,
even though it isn't necessary to prevent a crash remove those same
duplicate items from objects being indexed with the postgres index.
* Mark --use-unsafe-mem-store as deprecated. In the unlikely event someone's
using that option, a warning will print in the log. This option may be
removed at any time.
* Allow setting configuration options via environment variables. (See
the documentation for the details.)
* Finally allow configuring MySQL or PostgreSQL connection options with
command line flags (or, now, environment variables).
* Fixed format issues and wording in a few places in the documentation, along
with updating the docs for the current version.
* Add a hidden flag to generate a simple man page.
* Add that simple man page, along with the html docs, to the packagecloud.io
packages.
* Add a Dockerfile to allow running the local goiardi source in docker.
* Add Debian "stretch" and Ubuntu "yakkety yak" to the distro versions we have
in the package repository.
Nothing published for this version
Nothing published for this version
A small release, with only two changes:
A small release, with only two changes:
That's about it.
Not a big release in and of itself, but these changes seemed worth getting released sooner rather than later to make it in before the stretch freeze i
Not a big release in and of itself, but these changes seemed worth getting released sooner rather than later to make it in before the stretch freeze if possible.
The most important change, generally, is the reworking of reindexing - now, reindexing jobs won't pile up on top of each other, and the jobs are split into smaller, hopefully more manageable chunks. Storing secrets in vault is pretty neat too, though.
The CHANGELOG, this time:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
It's been a while, but here's a new goiardi release with (IMHO) some pretty good stuff.
It's been a while, but here's a new goiardi release with (IMHO) some pretty good stuff.
From the CHANGELOG:
As noted, goiardi now needs at least PostgreSQL 9.4 to be able to run. (In-memory and MySQL users are of course unaffected.) The search index will need to be rebuilt with knife index rebuild -y. The new indexing scheme uses roughly half as many rows in the search_items table as before, though.
Also, thanks to golang 1.7, this release includes an experimental goiardi binary for Linux on z/Architecture. It's totally untested so far, but if all goes well maybe there'll even be a real package for it.
Convenient debs and rpms of goiardi can be found at https://packagecloud.io/ct/goiardi, as always.
Now development on 1.0.0 should actually get going for real, once, erm, it gets synced up again with master.
Not a huge release or anything, but it adds some interesting stuff (in my opinion).
Not a huge release or anything, but it adds some interesting stuff (in my opinion).
From the CHANGELOG:
The JSON number bug required a pretty specific set of circumstances to cause trouble; you needed a very large number (not a string), and it needed to be used somewhere where the very large number turning into a float would not be parsed correctly. Still, it can definitely be a problem, so you should probably upgrade.
The other items are more interesting. Goiardi now exports pprof info via /debug/pprof, but for safety's sake only to localhost. Even better, though, is how goiardi can send statistics about itself to statsd, which in turn can send it on to something like graphite so you can make nice visualizations about goiardi. See the relevant docs for more information.
The big and interesting thing with this release will be the metrics goiardi can export via statsd, which you can then do neat stuff like look at it in
The big and interesting thing with this release will be the metrics goiardi can export via statsd, which you can then do neat stuff like look at it in grafana or set up alerts in bosun or somesuch.
Nothing published for this version
Nothing published for this version
Bugfixes in this release, along with packaging work and dealing with some external libraries either being moved or deleted. This was originally going
Bugfixes in this release, along with packaging work and dealing with some external libraries either being moved or deleted. This was originally going to be 0.10.2 (and named "Incitatus", after Caligula's horse), but while compiling binaries I found a problem where the steps that should have allowed Windows binaries to be compiled weren't working for some reason. Now, goiardi has taken handling the case where someone tries to use syslog on Windows into its own hands.
From the CHANGELOG (for both 0.10.2 and 0.10.3):
0.10.3
------
* Handle someone trying to use syslog on Windows ourselves, rather than
letting the logging library do it (it was causing trouble with gox).
0.10.2
------
* Fix up packaging and deploy scripts a bit
* Add sql schemas to the deb
* Fixed a logic error when configuring the address to listen on where the
value specified in the config file was always ignored, and only an address
specified on the command line worked. (Thanks to jordi and DQEbert here for
bringing this to my attention.)
* Added options to specify proxy hostname and port different than what goairdi
itself is listening on. (Thanks to jordi and DQEbert here as well.)
* CoC
* Added Debian wheezy to the list of distros we generate packages for.
* The logging library goiardi used moved. It had been forked, but since the
dependencies of said fork also moved, goiardi switched to the new version of
that library. Happily the logger library had added logging to syslog as an
option, so we just went back to using upstream at the new location. (Thanks
to theckman for providing a fix for this.)
* In concert with the above, add a "fatal" log level.
* Terraform removed the depgraph module, so that's been vendored into goiardi
along with its digraph dependency.
Fix up packaging and deploy scripts a bit
Just a bugfix release, but there's quite a few fixed bugs to be found here.
Just a bugfix release, but there's quite a few fixed bugs to be found here.
From the CHANGELOG:
Development for 1.0.0 (orgs+RBAC) will restart after this release, I promise, but in the meantime here's a new goiardi release with some good stuff wi
Development for 1.0.0 (orgs+RBAC) will restart after this release, I promise, but in the meantime here's a new goiardi release with some good stuff with search.
For more about the new PostgreSQL backed search, the goiardi docs have more.
This release also has binaries for DragonflyBSD, if you're into that.
No matter what, whether you're using the new postgres search or not, if you're upgrading to this release you'll need to rebuild your search index. If you're using the old search, delete your index file first. Then, whether you're using the old trie index or the new postgres based search, run knife index rebuild -y.
Vastly improve search query performance when there's 10,000 nodes. Barring any complications, this will be the last prerelease of 0.10.0.
Vastly improve search query performance when there's 10,000 nodes. Barring any complications, this will be the last prerelease of 0.10.0.
Nothing published for this version
Unbreak posting reports where the report is sent with gzip encoding.
Unbreak posting reports where the report is sent with gzip encoding.
Nothing published for this version
Nothing published for this version
Nothing published for this version
The important information about this preview release can be seen on the pg-search preview announcement page .
The important information about this preview release can be seen on the <a href="http://goiardi.gl/blog/2015/06/22/postgres-search-in-preview/">pg-search preview announcement page</a>.
Nothing published for this version
Nothing published for this version
Nothing published for this version
A minor bug fix release. This fixes an issue where importing a json dump that included reports was breaking because a JSON tag in reports was inadvert
A minor bug fix release. This fixes an issue where importing a json dump that included reports was breaking because a JSON tag in reports was inadvertently renamed when bringing goiardi's variable names in line with golang conventions. The JSON tag is fixed, and the import function can import report tags with either the proper or improper tag for node names.
A bug fix release (see http://en.wikipedia.org/wiki/Arthropleura), but still with good stuff.
A bug fix release (see http://en.wikipedia.org/wiki/Arthropleura), but still with good stuff.
This is still not the release with orgs+RBAC (that's the 1.0.0 branch). This release fixes some issues that were brought to my attention in January and February, but unfortunately I found myself having to set goiardi work aside for a bit because of vacation and from having been cranking too hard on it for too long. I'm back in the saddle, though, and aim to turn around some more search improvements soon, then turn back to the 1.0.0 branch and push on releasing that.
It's been a few slow months for goiardi, but goiardi development's picking back up again after some time off for vacation and being busy with other, n
It's been a few slow months for goiardi, but goiardi development's picking back up again after some time off for vacation and being busy with other, non-goiardi related things.
This is the first prerelease for version 0.9.1. This release has fixes for serving zero byte files in a cookbook, documentation improvements, a fix for client creation in cheffish, a rewritten cookbook depsolver, and a search fix for the case when you might be searching for "foo:bar AND NOT foo:bar" where it was returning the incorrect number of results. With the last one, as an added bonus now searches with AND clauses are more efficient, only re-searching through the existing results rather than going back to the full index again with each clause.
More detailed notes about things to come will be in the full release notes when 0.9.1 is formally released.
Nothing published for this version
Another interim release while work continues in the 1.0.0-dev branch to bring Chef 12 functionality to goiardi, but it adds some nice new features:
Another interim release while work continues in the 1.0.0-dev branch to bring Chef 12 functionality to goiardi, but it adds some nice new features:
If upgrading, delete the existing index file and rebuild it with knife index rebuild. It's a minor step, but since the search index file format has changed it needs to be rebuilt.
Remember that if you are upgrading goiardi from source, make sure to run go get -u github.com/ctdk/goiardi - the go-trie package has been updated. This release requires at least go 1.3 to build, and go 1.4 is recommended.
Same stuff as the previous prerelease of 0.9.0 at https://github.com/ctdk/goiardi/releases/tag/v0.9.0-pre1, but with a change with saving index and da
Same stuff as the previous prerelease of 0.9.0 at https://github.com/ctdk/goiardi/releases/tag/v0.9.0-pre1, but with a change with saving index and datastore files added - now, these files only get written if there have been changes since the last time they were saved.
One column per quarter.