Skip to content

Releases: buildkite/go-pipeline

v0.5.1

03 Apr 23:15
eae5ee4
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.5.0...v0.5.1

v0.5.0

01 Apr 23:46
4edda58
Compare
Choose a tag to compare

🗒️ Some input pipelines will now parse with a non-nil error, that didn't before. Code that calls Parse should check for the new error type provided by the warning package before aborting, since the parsed pipeline could still be accepted by Buildkite.

What's Changed

Full Changelog: v0.4.1...v0.5.0

v0.4.1

19 Feb 03:59
36fe486
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.4.0...v0.4.1

v0.4.0

08 Feb 23:01
v0.4.0
4cd6280
Compare
Choose a tag to compare

v0.4.0 (2024-02-09)

Full Changelog

⚠️ This release has some breaking changes.

Firstly, the type that is required to be passed into pipeline.(*Pipeline).Interpolate has changed from a map[string]string to an interface, pipeline.InterpolationEnv.

type InterpolationEnv interface {
	Get(string) (string, bool)
	Set(string, string)
}

This allows some equivalence between environment variable names to be established by the user, for example, on Windows, the environment variable names may be case-insensitive. If the implementation supports this, the pipeline interpolation will also support this. For example, this pipeline:

steps:
- command: echo $Foo $FOO

with an InterpolationEnv that whose Get method returns "bar" for "foo" regardless of the case, will be interpolated to

steps:
- command: echo bar bar

Previously, it was not possible to do this without adding the case-variants to the map[string]string.

Another breaking change is that previously, when interpolating the pipeline level environment block, a pipeline level environment variable could take precedence over environment variables in the argument to pipeline.(*Pipeline).Interpolate (aka the runtime env in the context of a job running on an agent) depending on the ordering. This may have contravened Buildkite's documentation that suggests the Job runtime environment takes precedence over that defined by combining environment variables defined in a pipeline. This led to results like this:

Suppose the runtime env consisted of FOO=runtime_foo. The following pipeline

env:
  BAR: $FOO
  FOO: pipeline_foo
steps:
- command: echo hello world

would be interpolated to become:

env:
  BAR: runtime_foo
  FOO: pipeline_foo
steps:
- command: echo hello world

On the other hand, the pipeline

env:
  FOO: pipeline_foo
  BAR: $FOO
steps:
- command: echo hello world

would be interpolated to become

env:
  FOO: pipeline_foo
  BAR: pipeline_foo
steps:
- command: echo hello world

We think this is inconsistent with runtime env taking precedence, and if users would like to interpolate $FOO as the value of the pipeline level definition of FOO, they should ensure the runtime env does not contain FOO=runtime_foo.

Fixed

  • Environment variable interpolation was not capable of being case-insensitive on Windows #20 (@triarius)
  • Precedence of Runtime Variables over Pipeline and Step Environment variables, even after they collide after interpolation #20 (@triarius)

Dependencies

  • Bump github.com/lestrrat-go/jwx/v2 from 2.0.18 to 2.0.19 #19 (@dependabot[bot])

v0.3.2

14 Dec 02:05
v0.3.2
943d581
Compare
Choose a tag to compare

v0.3.2 (2023-12-14)

Full Changelog

Fixed

v0.3.1

05 Dec 11:12
6df52d1
Compare
Choose a tag to compare

v0.3.1 (2023-12-05)

Full Changelog

Fixed

  • Fix interpolation of env variables into command step labels #17 (@triarius)

Dependencies

  • Bump github.com/lestrrat-go/jwx/v2 from 2.0.17 to 2.0.18 #16 (@dependabot[bot])

v0.3.0

29 Nov 02:52
d06cd5e
Compare
Choose a tag to compare

v0.3.0 (2023-11-29)

Full Changelog

Added

  • Add support for key and label fields on Command and Group steps #11 (@DrJosh9000)

Removed

  • [Breaking] Remove support for signing jobs with HMAC-SHA algorithms #13 (@moskyb)
  • [Breaking] Only allow 512-bit signature algorithms (remove support for *256 and *384 signing algorithms) #12 (@moskyb)

Changed

v0.2.1

13 Nov 02:03
4defc9c
Compare
Choose a tag to compare

v0.2.1 (2023-11-13)

Full Changelog

Fixed

  • Fix marshalling of plugins without config #7 (@triarius)
  • Update doc comments for plugin Marshal{JSON,YAML} #8 (@DrJosh9000)

Internal

v0.2.0

09 Nov 02:17
52ae055
Compare
Choose a tag to compare

v0.2.0 (2023-11-09)

Full Changelog

Changed

[Retracted] v1.0.1

08 Nov 04:09
f9a6620
Compare
Choose a tag to compare

This release exists to retract the accidentally-released v1.0.0, and to retract itself. The latest current version is v0.1.0.