You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"pull-request-header": ":rotating_light: There are changes ready for release :rocket:\n\nℹ Merge this PR once the team confirms the release is ready.\n",
We use [`release-please-action`][release-please-action-link] to automate versioning and changelog generation, along with a GitHub workflow that automatically publish the templates to [brickhub.dev][brickhub_link].
4
+
5
+
### How it works:
6
+
7
+
- 📌 **On Every Commit to main:**
8
+
- Commits are analyzed using [Conventional Commits][conventional_commits_link].
9
+
- If a version bump is needed, a **release PR** is automatically created or updated by [`release-please-action`][release-please-action-link].
10
+
- The **release PR** includes:
11
+
- An updated `CHANGELOG.md`
12
+
- A version bump in `brick.yaml`
13
+
14
+
##### 💡 Notes
15
+
16
+
- Release PR's are created **per template**.
17
+
- The GitHub Action workflow that automates the release process is configured in `.github/workflows/release_please.yaml`
18
+
- release-please settings are defined in `.release-please-config.json` and `.release-please-manifest.json`
19
+
- The release PR can be manually edited before merging.
20
+
- The release PR should be merged **ONLY** when a new release is needed.
21
+
22
+
<br />
23
+
24
+
- ✅ **When the Release PR Is Merged:**
25
+
- A new Git tag is created.
26
+
- A GitHub Release is published with the changelog.
27
+
- A new version of the brick is automatically published in [brickhub.dev][brickhub_link].
28
+
29
+
#### 💡 Notes
30
+
31
+
- GitHub Releases are created **per template**.
32
+
- The publishing process is automatically triggered when a version tag is created.
33
+
- The automated publishing workflows to [brickhub.dev][brickhub_link] are defined in `.github/workflows/publish_<template-name>.yaml`
34
+
35
+
<br />
36
+
37
+
This document provides a good summary of how it works and how we use it, but we recommend that you also read the official documentation of [Conventional Commits][conventional_commits_link], [Semantic Versioning][sem_ver_link], [Publishing a Brick][brickhub_publishing_link] and [`release-please-action`][release-please-action-link].
refactor(very_good_core)!: remove root-level project_name folder from brick structure.
4
5
5
-
## Migration details
6
+
###Migration details
6
7
7
8
The `very_good_core` brick no longer includes a top-level project name folder.
8
9
This allows generating the project directly into the current or a custom directory.
@@ -17,14 +18,14 @@ mason make very_good_core
17
18
mason make very_good_core -o ./output_folder
18
19
```
19
20
20
-
# 0.11.1
21
+
##0.11.1
21
22
22
23
- docs: update test command in very good core README ([#287](https://github.com/VeryGoodOpenSource/very_good_templates/pull/287))
23
24
- chore(very_good_core): deprecated script-based application of the flutter gradle plugin ([#249](https://github.com/VeryGoodOpenSource/very_good_templates/pull/249))
24
25
- chore(very_good_core): update format on MainActivity.kt ([#290](https://github.com/VeryGoodOpenSource/very_good_templates/pull/290))
25
26
- fix(android): correct source sets to ensure plugin compatibility ([#292](https://github.com/VeryGoodOpenSource/very_good_templates/pull/292))
26
27
27
-
# 0.11.0
28
+
##0.11.0
28
29
29
30
- chore(deps): bump very_good_analysis from 6.0.0 to 7.0.0 in /very_good_core/hooks [#233](https://github.com/VeryGoodOpenSource/very_good_templates/pull/233)
@@ -36,63 +37,63 @@ mason make very_good_core -o ./output_folder
36
37
- fix(very_good_core): Update concurrency group name template [#255](https://github.com/VeryGoodOpenSource/very_good_templates/pull/255)
37
38
- chore: bump very_good_analysis to 9.0.0 [#261](https://github.com/VeryGoodOpenSource/very_good_templates/pull/261)
38
39
39
-
# 0.10.0
40
+
##0.10.0
40
41
41
42
- feat: update pull request templates to add `test` type option ([#214](https://github.com/VeryGoodOpenSource/very_good_templates/pull/214))
42
43
- chore: update to Flutter 3.27 and Dart 3.6 ([#223](https://github.com/VeryGoodOpenSource/very_good_templates/pull/223))
43
44
44
-
# 0.9.0
45
+
##0.9.0
45
46
46
47
- chore: update copyright year in Windows Runner.rc ([#188](https://github.com/VeryGoodOpenSource/very_good_templates/pull/188))
47
48
- refactor: move current_year out from configuration ([#193](https://github.com/VeryGoodOpenSource/very_good_templates/pull/193))
- feat: use application id on macOS project ([#159](https://github.com/VeryGoodOpenSource/very_good_templates/pull/159))
58
59
- fix: default id when application id is empty ([#165](https://github.com/VeryGoodOpenSource/very_good_templates/pull/165))
59
60
60
-
# 0.7.1
61
+
##0.7.1
61
62
62
63
- style: Adding extra space to the application opening tag ([#126](https://github.com/VeryGoodOpenSource/very_good_templates/pull/126))
63
64
- chore: update Java versions on Very Good Core ([#128](https://github.com/VeryGoodOpenSource/very_good_templates/pull/128))
64
65
- chore: update to Very Good Analysis 6.0.0 ([#135](https://github.com/VeryGoodOpenSource/very_good_templates/pull/135))
0 commit comments