Merge pull request #81 from fossas/fix/non-custom-fetchers

Fix .fossa.yaml to not use implicit managed builds

.fossa.yaml

@@ -1,38 +1,12 @@
+# Generated by FOSSA CLI (https://github.com/fossas/fossa-cli)
+# Visit https://fossa.io to learn more
 version: 1
-
 cli:
-  # # Defaults to https://app.fossa.io
-  # server: https://fossa.on-prem
-  # api_key: some-key-here
-  # # If you're uploading to an existing git project, or a custom project in FOSSA
-  # fetcher: custom
-  # # If `project` is unset infer from VCS.
-  # project: fossa-proj
-
+  server: https://app.fossa.io
+  project: git@github.com:fossas/fossa-cli.git
+  fetcher: git
 analyze:
-  # ignores:
-  #   - path: github.com/kubernetes/kubernetes
-  #     type: dependency
-  #   - path: ./vendor/gopkg.in/yaml.v2
-  #     type: folder
   modules:
-    - name: fossa-cli
-      path: ./cmd/fossa
-      type: gopackage
-    # - name: vendored-jquery
-    #   path: vendor/jquery-stuff/bower.json
-    #   type: bowerpackage
-
-# These take a lot of inspiration from CircleCI
-# build:
-#   working_directory: /fossa
-#   docker:
-#     - image: some-image-host/image-name
-#       auth:
-#         username: foo
-#         password: $BAR
-#   environment:
-#     key: value
-#   steps: |
-#     echo "test"
-#     ls
+  - name: fossa-cli
+    path: ./cmd/fossa
+    type: gopackage

CHANGELOG

@@ -0,0 +1,23 @@
+# Changelog
+
+## Versioning policy
+
+This versioning policy only applies for versions below 1.0.0. We will develop a separate versioning policy after the 1.0.0 release.
+
+We generally follow semantic versioning, but semantic versioning does not specify pre-1.0.0 behavior. Here is how `fossa` pre-1.0.0 releases will work:
+
+- Any update that creates a breaking change (i.e. a change that causes a previously working configuration to fail) will bump the minor version.
+- All other updates will bump the patch version.
+- Preview, beta, and other special releases will have a pre-release identifer in the semantic version, and will be marked as pre-release on GitHub Releases.
+
+## Version history
+
+Major breaking changes and new features will be recorded here. For a much more detailed automated changelog, see the changelogs accompanying each GitHub Release.
+
+### 0.4.1
+
+#### New features
+- Managed Builds are now supported: you no longer need to have a corresponding Git project within FOSSA to upload build results.
+
+#### Breaking changes
+- By default, new projects will use Managed Builds (i.e. their fetcher will be `custom`). This is different from the original default, which set the fetcher to be `git`. This will break your configuration if you do not explicitly set the project's fetcher.