- Fixed: Actually a working upload to Octopus Deploy
- New: Allow naming of containers by creating a
bake.yaml
file besides theDockerfile
- New: Push Helm charts to Octopus Deploy raw package feed
- Fixed: .NET test reports now have unique names to ensure that reports are not overwritten if a projects targets multiple frameworks
- Fixed: Not limits description of NuGet packages to 4.000 characters
- New: Use content of
README.md
files as DLL and NuGet descriptions - New: .NET test reports are now saved as
.trx
files allow artifact uploads to pick these up after build completion - Fixed: Bake is now better at picking release notes with versions that
are similar to the build version if no exact match can be found. As
an example
1.0-alpha
is picked among1.1
,1.0-alpha
and0.9
when the build version is1.0.42
- Fixed: Project DLLs are now actually added to NuGet packages
- New: If there is no
.dockerignore
file found when building aDockerfile
, create one with some sensible defaults - New: By default, Docker builds will compress build context before sending it to the Docker daemon
- Fixed: Required
RepositoryUrl
parameter for NuGet packages is now the correct URL for the repository... for real this time
- New: Now understands Python Flask applications and bundles these into containers
- Fixed: Required
RepositoryUrl
parameter for NuGet packages is now the correct URL for the repository
- New: Produce ASP.NET Core containers that are able to run in read-only
file systems, run as non-root as well as drop all capabilities. Here is
an example security configuration
securityContext: runAsUser: 1000 runAsGroup: 2000 allowPrivilegeEscalation: false privileged: false readOnlyRootFilesystem: true capabilities: drop: - all
- New: Now possible to change Bake internal defaults via environment variables. More of these will be exposed in upcomming releases
- Fixed: Docker Hub push URL should just be the username
- New: Containers and their tags are now listed on GitHub releases
- New: Helm charts are now linted and packaged
- New: Now possible to set target platforms via --target-platform argument, which has the default win/x64, linux/x64 and osx/x64
- New: Bake now builds MkDocs built projects into ZIP files and releases them as part of the release process
- Fixed: Windows tool ZIP files now excludes the ".exe" in the filename
- Fixed: GitHub Enterprise usage should be detected in most cases now
- Fixed: Made sure that composers are do in an order that statisfies their needs
- New: Run .NET in an Alpine Linux image instead of a full blow Ubuntu
- New: Provide descriptions of what each sub-command actually does
- Fixed: Not specifying a version should merely default to 1.0 instead of throwing an exception
- Fixed: Release files containing Bake should be named
bake
instead ofBake
- Fixed: Now correctly naming the ZIP filename of the release artifacts on GitHub releases
- New: ZIP release artifacts before uploading them to GitHub releases
- Fixed: Release artifacts to GitHub releases are now correctly named after their release artifacts
- Fixed: .NET released DLLs/EXEs are now correctly stamped with version
- Fixed: Bake now correctly prints the help message if no sub-command is given instead of merely doing nothing
- New: Build, test and create containers for either .NET or Go
- New: Supported destinations for artifacts
- Docker Hub
- GitHub Packages (NuGet and container)
- GitHub Releases (tools)
- Basic functionality