indraq_cli 2.6.0 → 2.7.0

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.
Files changed (51) hide show
  1. package/README.md +55 -3
  2. package/cloud-api/dist/index.js +30 -2
  3. package/cloud-api/package.json +1 -1
  4. package/cloud-api/src/index.ts +12 -1
  5. package/dist/cli/help-content.js +2 -2
  6. package/dist/modules/cloud/commands/cloud.command.d.ts.map +1 -1
  7. package/dist/modules/cloud/commands/cloud.command.js +40 -3
  8. package/dist/modules/cloud/commands/cloud.command.js.map +1 -1
  9. package/dist/modules/cloud/services/cloud-aws.service.d.ts +1 -1
  10. package/dist/modules/cloud/services/cloud-aws.service.d.ts.map +1 -1
  11. package/dist/modules/cloud/services/cloud-aws.service.js +2 -2
  12. package/dist/modules/cloud/services/cloud-aws.service.js.map +1 -1
  13. package/dist/modules/cloud/services/cloud-jenkins.service.d.ts +1 -1
  14. package/dist/modules/cloud/services/cloud-jenkins.service.d.ts.map +1 -1
  15. package/dist/modules/cloud/services/cloud-jenkins.service.js +2 -2
  16. package/dist/modules/cloud/services/cloud-jenkins.service.js.map +1 -1
  17. package/dist/modules/cloud/services/cloud-npm.service.d.ts +1 -1
  18. package/dist/modules/cloud/services/cloud-npm.service.d.ts.map +1 -1
  19. package/dist/modules/cloud/services/cloud-npm.service.js +2 -2
  20. package/dist/modules/cloud/services/cloud-npm.service.js.map +1 -1
  21. package/dist/modules/cloud/services/github-packages.service.d.ts +5 -0
  22. package/dist/modules/cloud/services/github-packages.service.d.ts.map +1 -0
  23. package/dist/modules/cloud/services/github-packages.service.js +38 -0
  24. package/dist/modules/cloud/services/github-packages.service.js.map +1 -0
  25. package/dist/modules/cloud/services/project-cleanup.service.d.ts +1 -1
  26. package/dist/modules/cloud/services/project-cleanup.service.d.ts.map +1 -1
  27. package/dist/modules/cloud/services/project-cleanup.service.js +18 -16
  28. package/dist/modules/cloud/services/project-cleanup.service.js.map +1 -1
  29. package/dist/modules/cloud/services/user-provider.service.d.ts +1 -1
  30. package/dist/modules/cloud/services/user-provider.service.d.ts.map +1 -1
  31. package/dist/modules/cloud/services/user-provider.service.js +2 -2
  32. package/dist/modules/cloud/services/user-provider.service.js.map +1 -1
  33. package/dist/modules/mobile/services/mobile-project-directory.d.ts +5 -0
  34. package/dist/modules/mobile/services/mobile-project-directory.d.ts.map +1 -1
  35. package/dist/modules/mobile/services/mobile-project-directory.js +16 -1
  36. package/dist/modules/mobile/services/mobile-project-directory.js.map +1 -1
  37. package/dist/modules/prebuild/commands/prebuild.command.d.ts.map +1 -1
  38. package/dist/modules/prebuild/commands/prebuild.command.js +74 -13
  39. package/dist/modules/prebuild/commands/prebuild.command.js.map +1 -1
  40. package/dist/modules/scaffold/commands/init.command.d.ts.map +1 -1
  41. package/dist/modules/scaffold/commands/init.command.js +3 -3
  42. package/dist/modules/scaffold/commands/init.command.js.map +1 -1
  43. package/dist/modules/setup/commands/setup.command.d.ts.map +1 -1
  44. package/dist/modules/setup/commands/setup.command.js +3 -2
  45. package/dist/modules/setup/commands/setup.command.js.map +1 -1
  46. package/package.json +8 -4
  47. package/CHANGELOG_v2.5.0.md +0 -67
  48. package/CHANGELOG_v2.6.0.md +0 -9
  49. package/RELEASE_CHECKS_v2.5.0.md +0 -93
  50. package/TEST_RESULTS_v2.5.0.txt +0 -46
  51. package/TEST_RESULTS_v2.6.0.txt +0 -16
@@ -1,67 +0,0 @@
1
- # IndraQ CLI v2.5.0
2
-
3
- ## Setup and project creation
4
-
5
- - Project creation now shows one setup checklist instead of repeatedly asking `Would you like to configure it now?`.
6
- - The checklist contains:
7
- - Dockerfile(s)
8
- - GitHub Packages
9
- - Jenkins
10
- - AWS Route53
11
- - Nginx Proxy Manager
12
- - Only selected items run. Route53/NPM no longer silently add Jenkins or GitHub Packages.
13
- - `indraq setup` uses the same one-list workflow.
14
- - `indraq prebuild` uses one checklist and reuses that plan for all components.
15
- - Project creation no longer silently runs only GitHub Packages + Jenkins while ignoring Route53/NPM.
16
-
17
- ## Dockerfile reliability
18
-
19
- - Project creation can generate missing Dockerfiles for every selected web component.
20
- - `indraq setup` can generate missing Dockerfiles.
21
- - `indraq deploy` checks all selected components before build and offers one repair prompt for all missing Dockerfiles.
22
- - Existing Dockerfiles are preserved.
23
-
24
- ## Jenkins reliability
25
-
26
- - Before triggering a build, IndraQ snapshots Jenkins `nextBuildNumber` and `lastBuild`.
27
- - The Jenkins build POST is submitted only once.
28
- - If the reverse proxy returns a timeout/502/503/504 after Jenkins may have accepted the request, IndraQ does not automatically submit a second build.
29
- - IndraQ resolves the expected build number and reconnects to the same build/log stream when it can do so safely.
30
- - If IndraQ cannot safely identify the accepted build, it stops with an explicit uncertain-result message and tells the user to check Jenkins before retrying.
31
- - Queue/build-state/log reads now use bounded retry handling for transient reverse-proxy failures.
32
-
33
- ## Nginx Proxy Manager user authentication
34
-
35
- - Cloud credential resolution now uses the stored NPM email first, with username fallback for older rows.
36
- - Newly provisioned NPM users are immediately login-tested with the exact email/password IndraQ stores.
37
- - Login verification retries briefly for NPM propagation delay.
38
- - If verification fails, the newly created NPM account is removed instead of reporting a false success.
39
- - If NPM creation succeeds but Cloud credential mapping fails, the NPM identity is rolled back.
40
-
41
- ## GitHub Packages naming
42
-
43
- - User-facing `GHCR` wording is replaced by `GitHub Packages`.
44
- - `indraq scope create github-packages` is supported as the friendly CLI name.
45
- - The internal provider key remains `ghcr` and Jenkins variables such as `GHCR_IMAGE` remain unchanged for backward compatibility.
46
-
47
- ## Audit reasons
48
-
49
- - Normal creation/setup actions use safe automatic audit reasons.
50
- - Creation/setup no longer asks developers for repeated audit reasons.
51
- - Modification/deletion actions continue to ask for a reason, including user updates/deletes and project archive/restore flows.
52
-
53
- ## README and help
54
-
55
- - README rewritten in short, simple English.
56
- - Developer quick start is first.
57
- - Admin commands are separated from normal developer commands.
58
- - Dockerfile, Jenkins, NPM 401, multi-server, mobile and OTA troubleshooting are included.
59
- - Help text updated for v2.5.0 and GitHub Packages naming.
60
-
61
- ## Compatibility
62
-
63
- - Existing `ghcr` provider rows remain valid.
64
- - Existing Jenkins parameter names and pipeline variables are unchanged.
65
- - Existing v2.3 multi-environment and v2.4 mobile/OTA behavior is retained.
66
- - No new database migration is required for v2.5.0.
67
- - Cloud API version is 1.1.0 because NPM credential resolution behavior changed server-side.
@@ -1,9 +0,0 @@
1
- # IndraQ CLI v2.6.0
2
-
3
- - Fixed Windows OTA codesigning generation with argument-preserving `npx` invocation; temporary key material is always cleaned up.
4
- - Added project kind `backend-mobile` for existing and newly scaffolded projects, with backend Docker/Jenkins/GitHub Packages and mobile Jenkins/OTA setup in one Cloud project.
5
- - Added `indraq project delete` selective external cleanup: Route53 A records, GitHub Packages container packages, Jenkins project deployment jobs, and Nginx Proxy Manager proxy hosts. Every option defaults to KEEP. Shared and global Jenkins jobs are protected; failed provider operations stop Cloud-project deletion.
6
- - Added Cloud endpoint `GET /projects/:id/cleanup-inventory` for authorized project managers/admins, with cross-project resource reference checks.
7
- - No schema migration is needed. The Cloud API must be deployed before using v2.6.0's new cleanup feature.
8
-
9
- Validation: source syntax checks and local regression tests. Dependency-backed build and integration tests must run in a network-enabled environment.
@@ -1,93 +0,0 @@
1
- # IndraQ CLI v2.5.0 Release Checks
2
-
3
- ## Functional regression suite
4
-
5
- `npm test` passed from the v2.5.0 working tree.
6
-
7
- Coverage retained from earlier releases includes:
8
-
9
- - Cloud endpoint and persistent sessions
10
- - user lifecycle and provider-scope security
11
- - AWS/Route53
12
- - Nginx Proxy Manager
13
- - Jenkins crumbs/ports/live logs/parameters
14
- - Docker build context
15
- - project lifecycle/access
16
- - public/internal environment addressing
17
- - multi-component projects
18
- - multi-environment build-once deployment
19
- - mobile environments/builds
20
- - OTA registration, targeting, promotion, rollback and metrics
21
-
22
- v2.5-specific tests cover:
23
-
24
- - one setup checklist
25
- - literal selection (Route53/NPM do not silently add Jenkins/GitHub Packages)
26
- - automatic Dockerfile generation paths
27
- - GitHub Packages screen name and `github-packages` alias
28
- - creation vs mutation audit-reason behavior
29
- - NPM email-first credentials and provisioning rollback
30
- - Jenkins lost-response recovery without duplicate POST
31
- - simplified README/help
32
-
33
- ## Jenkins runtime recovery test
34
-
35
- A dedicated runtime regression simulates:
36
-
37
- 1. Jenkins pre-trigger snapshot reports next build 42.
38
- 2. The build POST reaches the simulated Jenkins/proxy path but returns HTTP 502.
39
- 3. IndraQ does not submit a second POST.
40
- 4. Build 42 appears and IndraQ attaches to it.
41
- 5. Jenkins console/build state completes successfully.
42
-
43
- A second case verifies that when no safe pre-trigger snapshot exists, IndraQ refuses to attach to an arbitrary old build and does not submit another POST.
44
-
45
- ## TypeScript validation
46
-
47
- Both projects passed strict TypeScript compilation in the sandbox:
48
-
49
- - root CLI: `strict`, `noUncheckedIndexedAccess`, `exactOptionalPropertyTypes`, `NodeNext`
50
- - Cloud API: strict TypeScript compilation
51
-
52
- The npm registry was unavailable from the sandbox (`EAI_AGAIN`/timeout), so unavailable third-party package typings were represented by temporary compile-only declarations. Those declarations are NOT included in the release package.
53
-
54
- Because of that network limitation, the final dependency-backed build gate must still be run on the publishing machine:
55
-
56
- ```powershell
57
- npm install
58
- npm run build
59
- npm test
60
- npm publish --dry-run
61
- ```
62
-
63
- Cloud API separately:
64
-
65
- ```powershell
66
- cd cloud-api
67
- npm install
68
- npm run build
69
- ```
70
-
71
- ## Package safety
72
-
73
- Before packaging, temporary validation `node_modules` and shim files are removed.
74
-
75
- The final package audit checks for:
76
-
77
- - no `node_modules`
78
- - no real `.env`
79
- - no `.npmrc`
80
- - no private `.pem`, `.key`, `.p12`, `.pfx`
81
- - no validation shim files
82
-
83
- ## Clean npm payload audit
84
-
85
- `npm pack --dry-run --ignore-scripts --json` on the clean release tree:
86
-
87
- - package: `indraq_cli@2.5.0`
88
- - files: 410
89
- - tarball size: 541,317 bytes
90
- - unpacked size: 2,254,425 bytes
91
- - forbidden files found: 0
92
- - README/changelog/release checks/test results included
93
- - `cloud-api/.env.example` included
@@ -1,46 +0,0 @@
1
- IndraQ CLI v2.5.0 test summary
2
- ================================
3
-
4
- FULL REGRESSION SUITE: PASS
5
-
6
- PASS built-in IndraQ Cloud endpoint regression
7
- PASS user-scoped cloud credential + shared environment regression
8
- PASS infrastructure init/DNS/proxy/GitHub Packages hardening regression
9
- PASS platform role/AWS/GHCR/DNS/NPM/init hardening regression
10
- PASS project membership + resource access regression
11
- PASS non-destructive existing-folder project create regression
12
- PASS Jenkins crumb + session-cookie regression
13
- PASS Jenkins aggressive port-check regression
14
- PASS prebuild cloud reconciliation regression
15
- PASS full Docker build-context + baked environment-file regression
16
- PASS identity/password/list-select/AWS-key-rotation regression
17
- PASS hard-delete / role-sync / generic-Jenkins-pipeline regression
18
- PASS v2 durable lifecycle + Jenkins compatibility regression
19
- PASS v2.2 retained scope architecture regression
20
- PASS v2.2 scope security + deploy lifecycle regression
21
- PASS v2.2.1 environment/scope-selection regression
22
- PASS v2.2.2 persistent-session regression
23
- PASS v2.2.2 persistent-session runtime regression
24
- PASS v2.2.3 logical fixes regression
25
- PASS v2.2.3 normal-user Route53 least-privilege regression
26
- PASS v2.2.3 Jenkins build/runtime diagnostics regression
27
- PASS v2.2.4 Jenkins parameter semantics + live console regression
28
- PASS v2.2.5 public/internal environment addressing regression
29
- PASS v2.3.0 compatible help/version fast-path regression
30
- PASS v2.3.0 component/multi-environment/performance/setup regression
31
- PASS v2.3.0 build-once multi-environment deploy runtime regression
32
- PASS v2.4 mobile + OTA regression
33
- PASS v2.5.0 setup/reliability/NPM/Docker/UX regression
34
- PASS v2.5.0 Jenkins lost-response recovery runtime regression
35
-
36
- STRICT TYPESCRIPT VALIDATION: PASS
37
- - Root CLI strict TypeScript: PASS
38
- - Cloud API strict TypeScript: PASS
39
-
40
- Version fast path:
41
- - node dist/index.js -V -> 2.5.0
42
-
43
- Sandbox limitation:
44
- The npm registry was unavailable, so a fresh real dependency install could not be completed in the sandbox.
45
- Temporary compile-only declarations were used only to validate the project source under strict TypeScript and were removed before packaging.
46
- Run the real dependency-backed build/publish dry-run on the publishing Windows machine before npm publish.
@@ -1,16 +0,0 @@
1
- IndraQ CLI v2.6.0 — local validation (November 19, 2026)
2
-
3
- PASS — npm test (all scripted regression suites, including v2.6.0)
4
- PASS — v2.6.0 selective cleanup mock-provider tests (DNS, NPM, Jenkins, GHCR)
5
- PASS — shared resource and shared Jenkins pipeline protection tests
6
- PASS — Windows npx argument-preservation regression (mocked Windows child process)
7
- PASS — 98 TypeScript source files parsed without syntax errors
8
- PASS — 98 TypeScript JavaScript output files generated using global TypeScript transpileModule
9
- PASS — node --check for all generated CLI and Cloud API JavaScript files
10
-
11
- NOT RUN — dependency-backed tsc build; npm registry unavailable in build environment.
12
- NOT RUN — live Windows Expo codesigning, live AWS/GitHub/Jenkins/NPM deletions, Cloud API/PostgreSQL integration.
13
-
14
- Before production: install dependencies and run npm run build && npm test
15
- in the CLI root; npm install && npm run build in cloud-api; deploy Cloud API
16
- v1.2.0 before CLI v2.6.0 and test against disposable provider resources.