Merge pull request #604 from microsoftgraph/feature/release-please

feature/release please

.github/release-please.yml

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

.github/workflows/publish.yml

@@ -21,10 +21,10 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
-      - name: Set up Python 3.11
+      - name: Set up Python 3.12
         uses: actions/setup-python@v5
         with:
-          python-version: 3.11
+          python-version: 3.12
       - name: Install dependencies
         run: |
           python -m pip install --upgrade pip
@@ -51,5 +51,3 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: gh release create --notes '${{ steps.extract-release-notes.outputs.release_notes }}' --title ${{ github.ref_name }} ${{ github.ref_name }}
-
-

.release-please-manifest.json

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

CHANGELOG.md

@@ -2,29 +2,28 @@
 
 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).
-
 ## [1.0.1] - 2024-04-22
 
 ### Added
 
 ### Changed
- -Enabled Large File Upload and Page iterator support
 
+ -Enabled Large File Upload and Page iterator support
 
 ## [1.0.0] - 2023-10-31
 
 ### Added
 
 ### Changed
+
 - GA release.
 
 ## [1.0.0a6] - 2023-10-12
 
 ### Added
 
 ### Changed
+
 - Replaced default transport with graph transport when using custom client with proxy.
 
 ## [1.0.0a5] - 2023-06-20

CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing to the Microsoft Graph Core SDK for Python
+
+The Microsoft Graph SDK for python 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 __main__ branch.  The main 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.
+