Skip to content

Commit fda4239

Browse files
author
Adam Sasine
authored
Merge pull request #24 from asasine/release/0.2.0
Updated versions to v0.2.0 and updated release guide
2 parents f0740dd + 35ad5d1 commit fda4239

File tree

4 files changed

+12
-17
lines changed

4 files changed

+12
-17
lines changed

README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Installing with NPM enables easier updates through the Unity Package Manager and
2828
1. Open the [Unity Package Manager](https://docs.unity3d.com/Manual/upm-ui.html) window
2929
1. In the top bar, change the packages to `Packages: In Project`
3030
1. Select `BehaviorTree.NET`
31-
1. In the bottom bar, click `Update to v0.1.1`
31+
1. In the bottom bar, click `Update to v0.2.0`
3232

3333
### Install from Git URL
3434
Installing from a Git URL allows you to fully customize which version of the package you use. If you are forking the package repository and not releasing on NPM, or are developing smaller features and bug fixes, you may find this approach useful.
@@ -38,7 +38,7 @@ Installing from a Git URL allows you to fully customize which version of the pac
3838
1. In the dropdown, select `Add package from git URL` from the add menu
3939
1. In the text box, enter the GitHub URL of this package: `https://github.com/asasine/BehaviorTree.NET.git`
4040
- You may also specify releases using tags
41-
- For example, targeting v0.1.1 would use the URL `https://github.com/asasine/BehaviorTree.NET.git#v0.1.1`
41+
- For example, targeting v0.2.0 would use the URL `https://github.com/asasine/BehaviorTree.NET.git#v0.2.0`
4242
- You can find all releases listed [here](https://github.com/asasine/BehaviorTree.NET/releases)
4343
- More information on specifying git references is available in the [Unity Manual](https://docs.unity3d.com/Manual/upm-git.html#revision)
4444
1. In the text box, click `Add`
@@ -52,4 +52,3 @@ Installing from disk lets you use a clone of the repo. This is useful if you are
5252
1. In the file explorer, navigate to the cloned repository and open the `package.json` file
5353

5454
Install the package into Unity as a local or git package by following the steps at https://docs.unity3d.com/Manual/upm-concepts.html#Sources.
55-

Runtime/BehaviorTree.NET.csproj

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
<PropertyGroup>
44
<PackageId>BehaviorTree.NET</PackageId>
5-
<Version>0.1.1</Version>
5+
<Version>0.2.0</Version>
66
<Authors>asasine</Authors>
77
<Company>asasine</Company>
88
<PackageLicenseExpression>MIT</PackageLicenseExpression>

docs/release.md

Lines changed: 8 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -13,20 +13,16 @@
1313
1. [Create a new release](https://github.com/asasine/BehaviorTree.NET/releases/new)
1414
- Tag version: `vMAJOR.MINOR.PATCH` targeting `main` (whatever version was decided above, with `v` prefix)
1515
- Title: `vMAJOR.MINOR.PATCH`
16-
- Description:
17-
- Should have a single H1: `vMAJOR.MINOR.PATCH (YYYY-MM-DD)`
18-
- Can have a small paragraph after the H1 (e.g., a summary, link to a blog post)
19-
- Should have various H2 (omit an H2 if it would be empty):
16+
- Description: use the `Auto-generate release notes` button.
17+
- Add a single H1: `vMAJOR.MINOR.PATCH (YYYY-MM-DD)`
18+
- Can have a small paragraph after the H1 (e.g., a summary, link to a blog post, etc.)
19+
- Can have categorized H2 (omit an H2 if it would be empty), or a general `What's Changed` H2. Examples of categories:
2020
- New Features
2121
- Bug Fixes
2222
- Internal
2323
- Use an unordered list under each H2
24-
- Each list item should have the format `#PR/#Issue Past tense description (@user)`
25-
- `#PR/#Issue` uses the PR or Issue number from the change.
26-
- `Past tense description` should begin with one of:
27-
- Added
28-
- Changed
29-
- Fixed
30-
- Removed
31-
- `@user` is the GitHub username of the person who made the change.
24+
- Each list item should have the format `{PR or Issue title} by @{user} {link}`
25+
- `{PR or Issue title}` is the title from the PR or Issue that was merged or closed.
26+
- `{user}` is the GitHub username of the person who made the change.
27+
- `{link}` is the URL of the PR or Issue.
3228
- Check `This is a pre-release` if `version < 1.0.0` or there's a pre-release suffix on the version (e.g., `0.1.1` or `1.4.2-alpha`)

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "com.asasine.behaviortree",
3-
"version": "0.1.1",
3+
"version": "0.2.0",
44
"displayName": "BehaviorTree.NET",
55
"description": "Behavior Trees for .NET and Unity",
66
"keywords": [

0 commit comments

Comments
 (0)