Releases · game-ci/unity-builder

16 Aug 19:53

webbertakken

v1.2

3e0842d

Scaling out to kubernetes 🎉

Marketplace

Functional changes:

#115 Add Android Build Settings and macOS buildNumber
#118 Remove androidVersionCode from workflow
#119 Log git diff during build
#122 Move docs to unity-ci.com
#123 and #124 Kubernetes Feature

Fixes:

#126 Bump lodash from 4.17.15 to 4.17.19 dependencies
#129 Fix boolean logic
#137 Rename custom -version flag to -buildVersion (internal change only)

Thanks

Special thanks for this release go out to:

@frostebite for doing all the hard work on the initial k8s implementation
@davidmfinol and @benoitdion for their continued efforts on support for mobile builds
@jspahrsummers for fixing an issue in unity >= 2019.4
@dogboydog for making debugging easier

Assets 2

02 Jul 15:25

webbertakken

v1.1

3523c6a

Android support 🎉

Marketplace

Functional changes:

#112 Document additional action inputs
#111 Cleanup workflow
#106 Add support for android builds
#102 Update to 2019.3
#101 Set android versionCode
#99 Make StandaloneOSX app runnable

Fixes:

#105 Fix fork PR builds
#94 Snyk badge really almost never works, bye

Thanks

Special thanks for this release go out to:

@benoitdion for contributing a significant improvement to the versioning code and adding android support!
@nathanleiby for adding improvements for OSX builds

Assets 2

22 May 22:53

webbertakken

v1.0

bfe6be7

First stable release 🎉

Marketplace

Functional changes:

#93 Update readme for v1.0 🎉
#92 Use commit-ish for git description when acquiring version
#91 Add flag for allowing dirty branch, needed for specific use cases building for different platforms

Fixes:

#90 Run versioning commands in projectPath instead of github workspace root

Thanks!

Special thanks for this first major release go out to:

@GabLeRoux for helping with design choices and continued support in the community.
@davidmfinol for help with versioning specifics in #92 and their efforts into streamlining android support in unity-actions#54, #60 and more.
@ivan-omnidrone for help with some versioning specifics in #90 and #91
Everyone who has contributed to unity-actions and provided their feedback

Assets 2

02 May 15:13

webbertakken

v0.15

44bde7f

Fix in versioning for PR events

Marketplace

Fixes:

#86 Base number of commits off of the branch

Assets 2

01 May 19:11

webbertakken

v0.14

34e4b86

Hotfix for repositories without tags

Marketplace

Fixes:

#85 Fix case where no tags does not trigger false

Known issues:

When no tag has ever been made the amount of commits will be used (as expected), however the amount of commits may be 1 higher than expected in pipelines that are triggered by PRs, because the ref to the pr commit is different than that of the branch (as far as i understand).

This means that when building from a PR, the version may be 1 higher than expected.

Assets 2

01 May 16:11

webbertakken

v0.13

e9514b4

Build versioning

Marketplace

Functional changes:

#80 Adds versioning strategies that make versioning work out of the box (does not apply for custom build scripts).
#80 Add strategy None to give the option to opt out. (version will be unchanged)
#80 Add strategy Semantic which will be based on tags and the number of commits on top. (0.1.2)
#80 Add strategy Tag which will only be based on the tag (tag must start with v#, where # is a digit for this to work)
#80 Add strategy Custom to simply pass in a specific version of your own choosing.
#80 Add documentation for all strategies in the readme of this repository.
#81 Cover versioning logic with 100% coverage
#83 Fix versioning for push event

Security updates:

#76 Bump acorn from 6.4.0 to 6.4.1
#84 Security updates

Other:

#84 Updated prettier and unicorn linters to the latest version and refactored code to match latest code styles.
#84 Set code coverage for patches to no longer block PRs, unless they affect the project too much.

More about versioning:

The custom option would be useful for pipelines that already generate their versions based on a different script. The implementation for that would look like this (supplying version in addition to versioning:

  versioning: Custom
  version: "0.4.12"

The default strategy will be set to Semantic, because it allows for easy out of the box versioning, which helps the newer developers under us (but also pro's) succeed faster. 🎉

To enable automatic versioning, all you need to do is update to the latest version of builder. This means that versioning is effectively an opt-out feature, rather than opt-in. 😉

To opt-out, simply set versioning strategy to none, like so;