Track internal Postgres target in release process
Some checks failed
OfficeCom Sentinel Client / build-client (push) Has been cancelled
Some checks failed
OfficeCom Sentinel Client / build-client (push) Has been cancelled
This commit is contained in:
25
docs/release-checklist.md
Normal file
25
docs/release-checklist.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Release Checklist
|
||||
|
||||
## Goal
|
||||
|
||||
Use this checklist before publishing every OfficeCom Sentinel release.
|
||||
|
||||
## Infrastructure Check
|
||||
|
||||
1. Confirm the internal PostgreSQL target is still correct in `infra/postgres-target.example.json` or its private production counterpart.
|
||||
2. Confirm the n8n internal base URL is still correct.
|
||||
3. Confirm the public client ingest URL still forwards to the intended internal service.
|
||||
4. Confirm no internal PostgreSQL host or IP is embedded in client configuration, installer output, or public release artifacts.
|
||||
|
||||
## Build Check
|
||||
|
||||
1. Build `OCSentinelClient-win-x64.zip`.
|
||||
2. Build `OCSentinelSetup.exe`.
|
||||
3. Generate `version.json`.
|
||||
4. Verify SHA-256 output matches the released ZIP.
|
||||
|
||||
## Publish Check
|
||||
|
||||
1. Upload the ZIP, SHA256 file, and setup EXE to the release.
|
||||
2. Update `release/stable/version.json` so NinjaOne keeps a version-independent manifest URL.
|
||||
3. If infrastructure changed, update the internal Postgres target record in the repo at the same time.
|
||||
Reference in New Issue
Block a user