Merge pull request #151 from microsoft/ci/release-please

ci: adds release please configuration

.github/release-please.yml

@@ -0,0 +1,3 @@
+manifest: true
+primaryBranch: main
+handleGHRelease: true

.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+    ".": "1.0.8"
+}

CHANGELOG.md

@@ -2,11 +2,6 @@
 
 All notable changes to this project will be documented in this file.
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [Unreleased]
-
 ## [1.0.8] - 2024-08-13
 
 ### Changed

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing to the Kiota JSON serialization for Go
+
+The Kiota JSON serialization for Go is available for all manner of contribution. There are a couple of different recommended paths to get contributions into the released version of this SDK.
+
+__NOTE__ A signed a contribution license agreement is required for all contributions, and is checked automatically on new pull requests. Please read and sign [the agreement](https://cla.microsoft.com/) before starting any work for this repository.
+
+## File issues
+
+The best way to get started with a contribution is to start a dialog with the owners of this repository. Sometimes features will be under development or out of scope for this SDK and it's best to check before starting work on contribution.
+
+## Submit pull requests for trivial changes
+
+If you are making a change that does not affect the interface components and does not affect other downstream callers, feel free to make a pull request against the __dev__ branch.  The dev branch will be updated frequently.
+
+Revisions of this nature will result in a 0.0.X change of the version number.
+
+## Submit pull requests for features
+
+If major functionality is being added, or there will need to be gestation time for a change, it should be submitted against the __feature__ branch.
+
+Revisions of this nature will result in a 0.X.X change of the version number.
+
+## Commit message format
+
+To support our automated release process, pull requests are required to follow the [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/)
+format.
+
+Each commit message consists of a __header__, an optional __body__ and an optional __footer__. The header is the first line of the commit and
+MUST have a __type__ (see below for a list of types) and a __description__. An optional __scope__ can be added to the header to give extra context.
+
+```
+<type>[optional scope]: <short description>
+<BLANK LINE>
+<optional body>
+<BLANK LINE>
+<optional footer(s)>
+```
+
+The recommended commit types used are:
+
+- __feat__ for feature updates (increments the _minor_ version)
+- __fix__ for bug fixes (increments the _patch_ version)
+- __perf__ for performance related changes e.g. optimizing an algorithm
+- __refactor__ for code refactoring changes
+- __test__ for test suite updates e.g. adding a test or fixing a test
+- __style__ for changes that don't affect the meaning of code. e.g. formatting changes
+- __docs__ for documentation updates e.g. ReadMe update or code documentation updates
+- __build__ for build system changes (gradle updates, external dependency updates)
+- __ci__ for CI configuration file changes e.g. updating a pipeline
+- __chore__ for miscallaneous non-sdk changesin the repo e.g. removing an unused file
+
+Adding a footer with the prefix __BREAKING CHANGE:__ will cause an increment of the _major_ version.

release-please-config.json

@@ -0,0 +1,14 @@
+{
+  "release-type": "go",
+  "bump-minor-pre-major": true,
+  "bump-patch-for-minor-pre-major": true,
+  "include-component-in-tag": false,
+  "include-v-in-tag": true,
+  "packages": {
+    ".": {
+      "package-name": "github.com/microsoft/kiota-serialization-json-go",
+      "changelog-path": "CHANGELOG.md"
+    }
+  },
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
+}