0.31.0

BREAKING CHANGE - The Kilnfile must be updated to work with this release. Instead of release_sources[].regex, the key is now release_sources[].path_template. See the README for details.

• kiln fetch no longer checks the stemcell version of compiled releases in the releases directory. Instead, it relies on the fact that the sha1 field will change when we switch the release to be compiled against a different stemcell. If the sha1 field from the Kilnfile.lock doesn't match the SHA1 of the release tarball, then we'll delete it and redownload the one compiled against the correct stemcell.

0.30.0

kiln upload-release will fail if the release would overwrite an existing release

0.29.0

• kiln upload-release now calculates the remote path instead of taking it as an argument
• kiln update-release accepts --allow-only-publishable-releases to ensure that we only update to "publishable" (i.e. compiled) releases
• Improve the output of kiln upload-release

0.28.0

Breaking Change - The Kilnfile.lock has new required fields: remote_source and remote_path. kiln fetch will fail if these are missing. You should no longer update the Kilnfile.lock by hand. Use kiln update-release instead.

Adds a few new commands:

• kiln update-release - Finds the "best" source for the specified release and version, and then updates the Kilnfile.lock so that kiln fetch will download that release tarball from now on.
• kiln upload-release - Uploads a local release tarball to a release source, so that it can be found by kiln update-release and downloaded by kiln fetch

Renames kiln update to kiln update-stemcell

Makes kiln fetch stable, so that is will always fetch the same assets given the same Kilnfile.lock. Previously it would always do a new search for the "best match" release. This lead to issues like the SHA1 being incorrect unpredictably.

0.27.0

• kiln fetch no longer errors when local releases are compiled for the wrong stemcell. It now deletes the incorrect releases and downloads the correctly-compiled version.
• kiln publish waits longer for PivNet responses and retries a few times to fetch the list of user groups. Previously it would error after timing out once, leaving your release in an inconsistent state that required manual fixing.
• Bump to go-pivnet v2.0.11 to resolve an issue with a breaking change made in that package

0.26.0

kiln fetch now has the --allow-only-publishable-releases flag. When this flag is set, it will only fetch from release sources marked as publishable: true in Kilnfile. You should use this flag when you're building a tile for public release.

0.25.0

kiln publish now updates user groups based on release type and kilnfile.

For pre-ga releases, it adds user groups based on pre_ga_user_groups key in kilnfile. If that key is omitted publish won't add any user groups.

GA releases will be made available to all users.

We also added some logging about the changes kiln publish makes.

0.24.0

BREAKING CHANGE

Change all kiln commands to use a Kilnfile and Kilnfile.lock instead of a mixture of assets.yml, assets.lock, Kilnfile and Kilnfile.lock. This required changing a flag name for each command (e.g. --assets-file became --kilnfile), which is where the breaking change comes in. The default value for these flags has also changed to Kilnfile where appropriate.

0.23.0

BREAKING CHANGE

Allow for more than one source of uncompiled releases for kiln fetch, as well as any combination and order of release sources. This changes the format of the assets.yml file. See the changes to the README.md for details.

0.22.0

• kiln fetch can now also fetch uncompiled releases from bosh.io and from a configurable s3 bucket. This enables us to build tiles that include bosh releases which have not previously gone through the RelEng CI.
• Add kiln update, which can update the version of the stemcell included in the tile. In the future it may be able to update release versions as well.
• Add kiln publish. This automates the previously-manual steps of the publishing process the RelEng team followed. It is currently missing one feature: setting the release to "All Users" (or a wider set of users if appropriate). That will come in a future release