officecom/oc-sentinel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 21 Wiki Activity

Add stable manifest URL for NinjaOne deployments
Some checks failed
OfficeCom Sentinel Client / build-client (push) Has been cancelled
Details

Browse Source
This commit is contained in:
OfficeCom Codex
2026-07-17 01:05:56 +02:00
parent e8b7a2831d
commit 38a99f2706
2 changed files with 14 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/ocsentinel-deployment.md
View File

@@ -36,7 +36,7 @@ Initial install/update:
```powershell ```powershell
& "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" ` & "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" `
-ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json" ` -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/raw/main/release/stable/version.json" `
-Force -Force
``` ```
@@ -44,7 +44,7 @@ Routine update:
```powershell ```powershell
& "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" ` & "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" `
-ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json" -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/raw/main/release/stable/version.json"
``` ```
Runtime: Runtime:
@@ -72,7 +72,9 @@ As of July 16, 2026, the first manual release is already published:
- tag: `v1.2.3` - tag: `v1.2.3`
- release URL: `https://gitea.officecom.cloud/officecom/oc-sentinel/releases/tag/v1.2.3` - release URL: `https://gitea.officecom.cloud/officecom/oc-sentinel/releases/tag/v1.2.3`
- manifest URL: `https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json` - stable manifest URL: `https://gitea.officecom.cloud/officecom/oc-sentinel/raw/main/release/stable/version.json`
The manifest is intentionally version-independent for NinjaOne. Only the JSON content changes per release; the NinjaOne task URL stays the same.
This means NinjaOne rollout can start immediately without waiting for a Gitea runner. This means NinjaOne rollout can start immediately without waiting for a Gitea runner.
@@ -83,3 +85,4 @@ When a Gitea runner is added later, the usual next step is:
1. connect to the runner host through SSH or RDP, depending on the server type 1. connect to the runner host through SSH or RDP, depending on the server type
2. install and register the Gitea runner 2. install and register the Gitea runner
3. let `.gitea/workflows/client-build.yml` publish future release artifacts automatically 3. let `.gitea/workflows/client-build.yml` publish future release artifacts automatically
4. update `release/stable/version.json` automatically as part of the release flow

8
release/stable/version.json Normal file
View File

@@ -0,0 +1,8 @@
{
"channel": "stable",
"version": "1.2.3",
"publishedAtUtc": "2026-07-16T22:58:05.1732183Z",
"artifactUrl": "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/OCSentinelClient-win-x64.zip",
"sha256": "50c7da8ff9cb96852493d4d89ad32bfd004a99fcf94b6acc70f8070ceaf737f2",
"minUpdaterVersion": "1.0.0"
}