Skip to content

Commit b413818

Browse files
authored
Merge pull request #14 from zy84338719/update
chore: release v1.9.8
2 parents a71bdc6 + bd4e58c commit b413818

File tree

29 files changed

+1677
-354
lines changed

29 files changed

+1677
-354
lines changed

.github/workflows/build.yml

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

33
on:
44
push:
5-
# Only trigger the heavy multi-platform build on version tag pushes (e.g. v1.9.1)
5+
# Only trigger the heavy multi-platform build on version tag pushes (e.g. v1.9.8)
66
tags:
77
- 'v*'
88
# Allow manual dispatch for ad-hoc builds from the UI

CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ This document explains how our GitHub Actions are gated and how to trigger heavi
44

55
### CI design principles
66
- Lightweight checks (unit tests, linters) run on `push` / `pull_request` for `main` and `develop` branches.
7-
- Heavy tasks (cross-platform builds, Docker image builds & push, release packaging) only run on tag pushes (e.g. `v1.9.1`) or when explicitly requested.
7+
- Heavy tasks (cross-platform builds, Docker image builds & push, release packaging) only run on tag pushes (e.g. `v1.9.8`) or when explicitly requested.
88

99
This reduces wasted CI minutes and avoids building/publishing artifacts for every code merge.
1010

@@ -13,8 +13,8 @@ There are multiple intentional ways to trigger full/heavy workflows:
1313

1414
- Push a semantic version tag (recommended for releases):
1515
```bash
16-
git tag v1.9.1
17-
git push origin v1.9.1
16+
git tag v1.9.8
17+
git push origin v1.9.8
1818
```
1919
Tag pushes trigger the `build.yml` / `release.yml` flows which do cross-platform builds and create the Release.
2020

0 commit comments

Comments
 (0)