From e8b7a2831d7f07a621c7595d15492884764c8eb3 Mon Sep 17 00:00:00 2001 From: OfficeCom Codex Date: Fri, 17 Jul 2026 01:00:34 +0200 Subject: [PATCH] Document manual NinjaOne rollout for v1.2.3 --- docs/ocsentinel-deployment.md | 24 +++++++++++++++++++++--- 1 file changed, 21 insertions(+), 3 deletions(-) diff --git a/docs/ocsentinel-deployment.md b/docs/ocsentinel-deployment.md index 283e7d2..e3bdb91 100644 --- a/docs/ocsentinel-deployment.md +++ b/docs/ocsentinel-deployment.md @@ -17,7 +17,7 @@ Build these locally with: ```powershell powershell -ExecutionPolicy Bypass -File .\build\build-client-package.ps1 powershell -ExecutionPolicy Bypass -File .\build\build-release-manifest.ps1 ` - -ArtifactUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v2.0.0/OCSentinelClient-win-x64.zip" + -ArtifactUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/OCSentinelClient-win-x64.zip" ``` ## Installed Layout @@ -36,7 +36,7 @@ Initial install/update: ```powershell & "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" ` - -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v2.0.0/version.json" ` + -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json" ` -Force ``` @@ -44,7 +44,7 @@ Routine update: ```powershell & "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" ` - -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v2.0.0/version.json" + -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json" ``` Runtime: @@ -65,3 +65,21 @@ Runtime: This writes: - `C:\ProgramData\OCSentinel\secrets\ocsentinel-upload-secret.dat` + +## Current Manual Release State + +As of July 16, 2026, the first manual release is already published: + +- 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` + +This means NinjaOne rollout can start immediately without waiting for a Gitea runner. + +## Later Automation + +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 +2. install and register the Gitea runner +3. let `.gitea/workflows/client-build.yml` publish future release artifacts automatically