brave-real-launcher 1.2.31 → 1.2.33

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "brave-real-launcher",
3
- "version": "1.2.31",
3
+ "version": "1.2.33",
4
4
  "description": "Launch Brave Browser with ease from node. Based on chrome-launcher with Brave-specific support.",
5
5
  "main": "./dist/index.js",
6
6
  "module": "./dist/index.mjs",
File without changes
@@ -1,44 +0,0 @@
1
- # GitHub Workflow Local Test Report
2
-
3
- **Generated:** 2025-09-19T16:27:51.568Z
4
-
5
- ## Test Results
6
-
7
- - ✅ Basic workflow syntax validation passed
8
- - ✅ Auto-increment version logic working
9
- - ✅ Always-proceed logic implemented
10
- - ✅ Chrome-launcher sync script validation passed
11
- - ✅ Build process validation passed
12
-
13
- ## Summary
14
-
15
- - **Total Tests:** 5
16
- - **Passed:** 5
17
- - **Warnings:** 0
18
- - **Failed:** 0
19
-
20
- ## Next Steps
21
-
22
- 1. ✅ Workflow syntax is valid
23
- 2. ✅ Core logic is working
24
- 3. ✅ Build process is functional
25
- 4. 🚀 **Ready to push to GitHub**
26
-
27
- ## GitHub Secrets Required
28
-
29
- Make sure these secrets are configured in your GitHub repository:
30
-
31
- - `GH_TOKEN` - GitHub Personal Access Token with repo permissions
32
- - `NPM_TOKEN` - NPM authentication token for publishing
33
-
34
- ## Manual Testing Commands
35
-
36
- To test the workflow manually on GitHub:
37
-
38
- ```bash
39
- # Manual trigger with default settings
40
- gh workflow run chrome-launcher-sync.yml
41
-
42
- # Manual trigger with specific version
43
- gh workflow run chrome-launcher-sync.yml -f chrome_launcher_version=1.0.0 -f force_publish=true
44
- ```