NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #804 by repository stars
Latest stable
v2.6.0+incompatible
Last release 4 years ago
no release in 18 months
Release timing varies
gaps range from 8 days to 4 months
Most releases are documented
notes for 22 of 32 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
102 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
docs(*): add releasing.md doc, bump strings in anticipation of v0.20.0 6b915d26f9414d1e35b2152be5cc974c8ceda4a4 (Vaughn Dice)
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Brigade release v0.19.0 bd26da8991c5bf9c00e7824c45be5a11a7a49776 (Vaughn Dice)
brig build list c8046a09417a83836f721d764b08648c34fa5d05 (Dimitris-Ilias Gkanatsios)Brigade release v0.18.0 e139cfad72fd1a92e8d1679fe3e55bced4f7ffa3 (vdice)
brig run as a go library (#623) 5cab72993ed1fa97ecd27c31586d0692ddc52229 (KUOKA Yusuke)This is a bugfix release (with a feature that we accidentally snuck in there).
This is a bugfix release (with a feature that we accidentally snuck in there).
Once we hit our release 1.0.0-alpha.1, we will cease making compatibility-breaking changes until Brigade 2.0. Until we hit the alpha release, though,…
We are working our way toward a 1.0.0 release. This is a transitional release that has some backward compatibility changes. The next few releases will be similar as we take our last opportunity to change the APIs before we freeze them.
As always, we welcome you to join the conversation in the Kubernetes Slack
The major features in this release are:
project create|delete commandsbrig builds list can now take a project namebrig dashboard has been added as a convenience for accessing Kashti (brig proxy was removed)Brigade adheres to SemVer2.
As we move toward 1.0.0, our plan is to make a few "invasive" changes which may cause breakages. Once we hit our release 1.0.0-alpha.1, we will cease making compatibility-breaking changes until Brigade 2.0. Until we hit the alpha release, though, we reserve the right to break compatibility. We do this because we want to make sure that the entire 1.0 lifecycle is stable, consistent, and usable.
That said, we do our best to avoid breaking changes.
brig proxy was removedbrigade-project chart is deprecated, but not removed yet. It will be removed before 1.0.0-alpha.1 (in favor of brig project create).Our cross-compile of brig is failing for macOS and Windows currently. We are repairing it and will post binaries when we can.
UPDATE: Binaries for brig are now available.
Job docs (#537) 4e52c4a69efa3055c248d1df51027b619a560bc2 (Mike Bannister)brig dashboard c6e35fe4eb277b16a88ca827bb55280174f471b4 (Matthew Fisher)As always, we welcome you to join the conversation in the Kubernetes Slack
As always, we welcome you to join the conversation in the Kubernetes Slack
pull_request fires closed event (#464) 1e14ec9a3711d41628db269dc9c701bd230d9787 (Harrison Harnisch)As always, we welcome you to join the conversation in the Kubernetes Slack
As always, we welcome you to join the conversation in the Kubernetes Slack
Binary releases of brig are attached to this release. We now provide an official containerized brig client
The 0.13 release was built with a version of helm package that had a bug. This release is just a rebuild of the chart (and other artifacts, for consis
The 0.13 release was built with a version of helm package that had a bug. This release is just a rebuild of the chart (and other artifacts, for consistency).
There is no need to upgrade from 0.13.0 if that release is already installed, but we recommend that new releases are done using this version.
What better day to release our lucky 13th release than on Friday the 13th? If you're highly superstitious, you might want to skip this release. For al
What better day to release our lucky 13th release than on Friday the 13th? If you're highly superstitious, you might want to skip this release. For all others, we recommend upgrading.
As always, we welcome you to join the conversation in the Kubernetes Slack
Binary releases of brig are attached to this release. We now provide an official containerized brig client
This release includes new features for Brig and for the Job JS object.
brig run --level warn)Pending, Running lines repeatedlybrig build logs command to fetch logs from builds. Try out brig build logs --last --jobs to check out the feature.Fro Job, we added these new features:
Job object now was a logs() method for fetching the STDOUT from the job after the job is complete.Job object now has an args: []string property that will allow specifying arguments that are passed directly to the container.secretKeyRef and configMapKeyRef parametersrun() in the error event (which previously did not run jobs to completion)In addition to these new features, several small ones were added. See the changelog below.
brig run to use the progress bar by default, we have changed the output. To use the old formatting in scripts, use brig run --no-progress.The next Brigade feature release will be v0.14.0.
In this release, we have a number of important fixes.
In this release, we have a number of important fixes.
As always, we welcome you to join the conversation in the Kubernetes Slack #brigade room.
In this release, we have a number of important fixes.
In this release, we have a number of important fixes.
As always, we welcome you to join the conversation in the Kubernetes Slack #brigade room.
This is a major release of Brigade, with many new features and a few compatibility breaking changes. Notably, we changed the API for sending commit in…
This is a major release of Brigade, with many new features and a few compatibility breaking changes. Notably, we changed the API for sending commit information from a gateway. We advise all users to upgrade, but also to be careful as they do so.
Big changes and fixes:
As always, we welcome you to join the conversation in the Kubernetes Slack #brigade room.
brigade-gateway has been renamed brigade-github-gateway to better reflect what it doesWe are continuing to focus on configurability and flexibility of Brigade. We are also refactoring some of the naming to standardize on ULID instead of using timestamps or other formulas to generate unique tokens.
During our pre-1.0 cycle, we will continue to fix bugs and add new features. While we try to keep compatibility breaking changes to a minimum, we know…
In this release, we have a number of important fixes, and we highly recommend all 0.8 users upgrade.
Notable bug fixes:
As always, we welcome you to join the conversation in the Kubernetes Slack #brigade room.
The Container Registry (aka Dockerhub) gateway no longer requires a GitHub auth token. There is now no auth against GitHub for DockerHub operations (which is as it should be). This won't break existing deployments, but might be surprising for those who used the gateway when we required GitHub auth for this.
During our pre-1.0 cycle, we will continue to fix bugs and add new features. While we try to keep compatibility breaking changes to a minimum, we know that our next release will have a few naming changes as we work on improving consistency.
Thank you sincerely for your thoughtful input in the issue queue and in slack! We are excited that here in this pre-1.0 cycle we can still make big changes to help the community take on big challenges.
During our pre-1.0 cycle, we will continue to fix bugs and add new features. While we try to keep compatibility breaking changes to a minimum, we know…
The Brigade community is working hard, and this release shows it! A dozen individuals contributed over 40 changes to this release. Thank you!
We encourage users to migrate to this version, especially if using the GitHub gateway.
As always, we welcome you to join the conversation in the Kubernetes Slack #brigade room.
after event when no other event is triggered. after will only fire if the worker first executes some other event.During our pre-1.0 cycle, we will continue to fix bugs and add new features. While we try to keep compatibility breaking changes to a minimum, we know that our next release will have a few naming changes as we work on improving consistency.
Thank you sincerely for your thoughtful input in the issue queue and in slack! We are excited that here in this pre-1.0 cycle we can still make big changes to help the community take on big challenges.
brigadier in examples. 5198db0cd214d0264933b4096dae7d1ab9137ccb (JD Huntington)brig c62a5ed411d865e345b89dc56d4aa9dba62473ca (Mitchel Humpherys)run command to brig scripting 50a0ceccaf28ea34dbc7afbc2f0f8c8f02e40479 (Ben Limmer)We try to be careful with our breaking changes. But prior to the 1.0 release of Brigade, we also occasionally make changes that are inconvenient but (…
We're excited to bring you Brigade 0.7.0, with features and bugfixes. We made some big changes that may impact existing users.
Join the discussion in the Kubernetes slack #brigade room!
The big feature of this release is the much-improved handling of GitHub pull_request events. For security reasons, Brigade now blocks pull requests on forked repos from triggering pull_request events. To disable this behavior, you can set the BRIGADE_BUILD_FORKED_PULL_REQUESTS environment variable on the Gateway's deployment.
We try to be careful with our breaking changes. But prior to the 1.0 release of Brigade, we also occasionally make changes that are inconvenient but (we believe) in the overall best interest of the project.
Summary of breaking changes:
imagePull event was renamed image_pull to match other events.The gateway has been split in two. The existing gateway (which will likely be renamed to "github-gateway" in the future) now only handles GitHub's push and pull_request hooks.
A new gateway, the Container Registry Gateway (cr-gateway) now handles container registry webhooks (event image_push) from Dockerhub and ACR. Because that webhook API does not have authentication, we have turned this gateway off by default. To enable it with Helm, use --set cr.enabled=true.
In the future, we will be moving toward gateway microservices instead of configuring one gateway to listen to lots of different external services.
This release includes an array of bug fixes and feature additions.
This release includes an array of bug fixes and feature additions.
This release of Brigade contains a number of improvements and fixes, and we recommend that all users upgrade.
This release of Brigade contains a number of improvements and fixes, and we recommend that all users upgrade.
From 0.5, we now require that a Build ID (in the form of a ULID) and a Build Name (arbitrary, but unique, string) be set on the Event secret by the gateway. If a build ID is not supplied, the controller will no process the request.
For developers: The Makefile got a major upgrade. You may need to re-run make bootstrap. Some make targets changed, too. For example, to build the client you can now make brig.
These reflect changes since 0.3.0, since we forgot to do 0.4.0 release notes.
Nothing published for this version
This release fixes several small bugs, and now works on Kubernetes 1.8
This release fixes several small bugs, and now works on Kubernetes 1.8
Kubernetes 1.8 dropped support for the initContainer annotation, which we were using to support older Kubernetes versions. This release switches to spec.initContainer for the init container definition.
glide to dep for package management, so building from source has a new requirement.master, not from this tag.This is the second Brigade pre-release, and contains major changes.
This is the second Brigade pre-release, and contains major changes.
Possibly breaking changes:
j.storage.enabled = truebrigade.js file. If no brigade file is sent, one is loaded from the project's VCS.Active development on Brigade will continue. The next planned release is pre-release 0.3.0.
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
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
One column per quarter.