github.com/joey-fossa/fossa-cli@v0.7.34-0.20190708193710-569f1e8679f0/CHANGELOG.md (about) 1 # Changelog 2 3 ## Versioning policy 4 5 This versioning policy only applies for versions below 1.0.0. We will develop a 6 separate versioning policy after the 1.0.0 release. 7 8 We generally follow semantic versioning, but semantic versioning does not 9 specify pre-1.0.0 behavior. Here is how `fossa` pre-1.0.0 releases will work: 10 11 - Any update that creates a breaking change (i.e. a change that causes a 12 previously working configuration to fail) will bump the minor version. 13 - All other updates will bump the patch version. 14 - Preview, beta, and other special releases will have a pre-release identifer in 15 the semantic version, and will be marked as pre-release on GitHub Releases. 16 17 ## Version history 18 19 Major breaking changes and new features will be recorded here. For a much more 20 detailed automated changelog, see the changelogs accompanying each GitHub 21 Release. 22 23 ### 0.7.0-beta 24 25 - Analyzers can now take options. The exact options depend on the analyzer. 26 - **Breaking:** Modules now have "targets", distinct from their name and path. 27 Targets help specify things like Maven projects, Maven configurations, etc. 28 29 ### 0.4.5 30 - `fossa` is now licensed under MPL-2.0 instead of AGPLv3 31 - Non-fatal missing binaries no longer cause builds to fail (this should help a 32 lot for Go) 33 34 ### 0.4.1 35 - Managed Builds are now supported: you no longer need to have a corresponding 36 Git project within FOSSA to upload build results. 37 - **Breaking:** By default, new projects will use Managed Builds (i.e. their 38 fetcher will be `custom`). This is different from the original default, which 39 set the fetcher to be `git`. This will break your configuration if you do not 40 explicitly set the project's fetcher.