push: v0.1.0

.github/workflows/release-android.yml

@@ -2,9 +2,7 @@ on:
   push:
     tags:
       - v*
-    branches: 
-      - master
-name: Android Build and Release
+name: Build-Release[Android]
 
 jobs:
   release:
@@ -59,6 +57,7 @@ jobs:
             const latestRelease = releases[0];
             console.log(JSON.stringify(latestRelease, null, 2));
             core.setOutput('upload_url', latestRelease.upload_url);
+            core.setOutput('tag_name', latestRelease.tag_name);
       # 发布到 Release
       - name: Upload Release Android
         id: upload-release-android 
@@ -68,5 +67,5 @@ jobs:
         with:
           upload_url: ${{ steps.get_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps 
           asset_path: ./build/app/outputs/flutter-apk/app-release.apk
-          asset_name: app-release.apk
+          asset_name: oasx_${{ steps.get_release.outputs.tag_name }}_android.apk
           asset_content_type: application/vnd.android.package-archive

.github/workflows/release-create.yml

@@ -3,10 +3,8 @@ on:
       # Sequence of patterns matched against refs/tags
       tags: 
         - 'v*' # Push events to matching v*, i.e. v1.0, v20.15.10
-      branches: 
-        - master
 
-name: Create Release Android
+name: Release[tag]
 
 jobs:
   create-release:

.github/workflows/release-windows.yml

@@ -1,10 +1,10 @@
 on:
   push:
-    # tags: 
-    #     - 'v*'
-    branches: 
-      - master
-name: Windows Build and Release
+    tags: 
+        - 'v*'
+    # branches: 
+    #   - master
+name: Build-Release[Windows]
 
 
 jobs:
@@ -51,9 +51,10 @@ jobs:
         - name: Compress file
           uses: a7ul/tar-action@v1.1.0
           with:
+            cwd: ./build/windows/runner
             command: c
-            files: build/windows/runner/Release    
-            outPath: build/windows/runner/windows.tar.gz
+            files: ./Release    
+            outPath: ./windows.tar.gz
         # 最新的发布url
         - name: Get latest release
           id: get_release
@@ -70,7 +71,7 @@ jobs:
               core.setOutput('upload_url', latestRelease.upload_url);
               core.setOutput('tag_name', latestRelease.tag_name);
         # 发布到 Release
-        - name: Upload Release Android
+        - name: Upload Release Windows
           uses: actions/upload-release-asset@v1
           env:
             GITHUB_TOKEN: ${{ secrets.RELEASE_TOKEN }}

pubspec.yaml

@@ -1,8 +1,10 @@
 name: oasx
-description: the gui of OAS
+description: The GUI of OAS
 # The following line prevents the package from being accidentally published to
 # pub.dev using `flutter pub publish`. This is preferred for private packages.
 publish_to: 'none' # Remove this line if you wish to publish to pub.dev
+version: 0.1.0+1
+
 
 # The following defines the version and build number for your application.
 # A version number is three numbers separated by dots, like 1.2.43
@@ -16,7 +18,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev
 # https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
 # In Windows, build-name is used as the major, minor, and patch parts
 # of the product and file versions while build-number is used as the build suffix.
-version: 0.0.1+1
+
 
 environment:
   sdk: '>=3.1.0 <4.0.0'