NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #1588 by repository stars
Last release 9 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 4 months
Nearly every release is documented
notes for 25 of 27 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
150 releases · first in 2014
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
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
Nothing published for this version
Minor release of the spec with one critical bug/consistency fix and a few tooling enhancements.
Minor release of the spec with one critical bug/consistency fix and a few tooling enhancements.
0.7.0 introduced a field to the app section of ImageManifests to allow users to specify supplementary group IDs. Unfortunately, this was implemented with inconsistent naming: supplementaryGids in the text of the spec itself, but supplementaryGroups in the schema code.
In this release we standardise both the spec and the schema to supplementaryGIDs. See #516 for more information.
Other changes in this release:
--owner-root flag to acbuild to adjust the uid/gid of all files in an ACI to 0:0 (#509)--supplementary-gids flag to actool's patch-manifest subcommand to adjust the supplementary group IDs of an ACI (#506, #516)lastditch package (#508)NewAppFromString parser in the discovery package to URL-encode label values before parsing them (#514)Nothing published for this version
Nothing published for this version
Next major release of the spec, with a lot of tooling improvements, wording clarifications, and one breaking schema change from the previous release.
Next major release of the spec, with a lot of tooling improvements, wording clarifications, and one breaking schema change from the previous release.
Spec changes since v0.6.1:
mount objects in pod manifests now refer directly to a path rather than referencing an app's mountPoint. This makes it easier for implementations to provide supplementary, arbitrary mounts in pods without needing to modify app sections in the pod manifest. This is a breaking schema change; however, implementations are suggested to preserve similar behaviour to the previous three-level mount mappings by continuing to use mountPoints name fields to generate mount<->volume mappings (#364, #495)supplementaryGroups field, which allows users to specify a list of additional GIDs that the processes of the app should run with (#339)Tooling changes and features:
IsValidOSArch function implementations can useapp section in their manifest, actool will now automatically inject an App iff the user specifies an exec statement (#473, #489)Schema and tooling bugfixes:
actool patch-manifest is supplied with an ACI with no app section in its ImageManifest (#473)build_aci now works if NO_SIGNATURE is setbuild_aci properly generates an armored signature (#460)Other changes:
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
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
Minor release of the spec; the most important change is adjusting the type for annotations to ACIdentifier (#442). This restores the ability for annot
Minor release of the spec; the most important change is adjusting the type for
annotations to ACIdentifier (#442). This restores the ability for annotation
fields to be namespaced with DNS names.
Other changes:
arm6vl as valid arch for Linux (#440)This is an important milestone release of the spec. Critically, there are two backwards-incompatible schema changes from previous releases:
This is an important milestone release of the spec. Critically, there are two backwards-incompatible schema changes from previous releases:
app field has been renamed to the more accurate and
unambiguous imageName: #397ACName has been redefined (with a stricter specification) to be suitable
for relative names within a pod, and a new type, ACIdentifier, has been
introduced for image, label and isolator names: #398This release also sees the sections of the specification - image format, discovery process, pods and executor definitions - being split into distinct files. This is a first step towards clarifying the componentised nature of the spec and the value in implementing individual sections.
Other changes of note in this release:
size field. If this field is
specified, executors should validate that the size of resolved dependency
images is correct before attempting to retrieve them: #422container environment
variable to some value to indicate to applications that they are being run
inside a container: #302Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release features a considerable number of changes over the previous (0.5.1) release. However, the vast majority are syntactical improvements to c
This release features a considerable number of changes over the previous
(0.5.1) release. However, the vast majority are syntactical improvements to
clarity and wording in the text of the specification and do not change the
semantic behaviour in any significant way; hence, this should remain a
backwards-compatible release. As well as the changes to the spec itself, there
are various improvements to the schema/tooling code, including new
functionality in actool.
Some of the more notable changes since v0.5.1:
linux/aarch64, linux/armv7l and linux/armv7b added as recognised
os/arch combinations for imagescat-manifest and patch-manifest subcommands to actool to manipulate
existing ACIsNothing 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
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
Nothing published for this version
Nothing published for this version
This is primarily a bugfix release to catch 2a342dac which resolves an issue preventing PodManifests from being successfully serialized.
This is primarily a bugfix release to catch 2a342dac which resolves an issue preventing PodManifests from being successfully serialized.
Other changes:
Nothing published for this version
The major change in this release is the introduction of _pods_, via #207 and #248. Pods are a refinement (and replacement) of the previous ContainerRu
The major change in this release is the introduction of pods, via #207 and #248. Pods are a refinement (and replacement) of the previous ContainerRuntimeManifest concept that define the minimum deployable, executable unit in the spec, as a grouping of one or more applications. The move to pods implicitly resolves various issues with the CRM in previous versions of the spec (e.g #83, #84)
Other fixes and changes in this release:
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is a minor bugfix release to fix marshalling of isolators.
This is a minor bugfix release to fix marshalling of isolators.
Nothing published for this version
Major changes and additions since v0.3.0:
Major changes and additions since v0.3.0:
.asc filename extension for signaturesNothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →