[c19yamamoto]

Summary

• Add version-manager resolve <versionTags...> to print the highest matching version.
• Skip generator bootstrap and downloads for the resolver command.
• Keep configuration reads side-effect-free so openapitools.json is not created or modified.

Testing

• yarn lint
• yarn test
• yarn build
• Manual check: version-manager resolve latest prints 7.26.0 without creating a config file or JAR.

Fixes #1289

---

Summary by cubic

Adds a side-effect-free resolve subcommand to version-manager that prints the highest matching version, fixing #1289. Resolution now fails with a non-zero exit code when no version matches the given tags.

• version-manager resolve <versionTags...> prints the first matching version and skips generator bootstrap, downloads, and config writes; unmatched tags print an error to stderr and exit non-zero.
• The command is detected positionally, so opening flags like --openapitools are skipped and it is not confused with pass-through arguments.
• ConfigService no longer creates or modifies openapitools.json when reading configuration—the file is only touched on writes.

^{Written for commit 305bb54. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 7 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/generator-cli/src/app/services/config.service.spec.ts">

<violation number="1" location="apps/generator-cli/src/app/services/config.service.spec.ts:72">
P2: This regression test does not cover the absent-config case: its setup always returns an existing configuration object. Add a case with `fs.readJSONSync.mockReturnValue(undefined)` and assert that `ensureFileSync` and the write methods remain unused, so a missing `openapitools.json` cannot regress to being created.</violation>
</file>

<sub>Reply to a comment to ask cubic a question or push back. It learns from your replies.

View guided diff | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: This regression test does not cover the absent-config case: its setup always returns an existing configuration object. Add a case with fs.readJSONSync.mockReturnValue(undefined) and assert that ensureFileSync and the write methods remain unused, so a missing openapitools.json cannot regress to being created.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At apps/generator-cli/src/app/services/config.service.spec.ts, line 72:

<comment>This regression test does not cover the absent-config case: its setup always returns an existing configuration object. Add a case with `fs.readJSONSync.mockReturnValue(undefined)` and assert that `ensureFileSync` and the write methods remain unused, so a missing `openapitools.json` cannot regress to being created.</comment>

<file context>
@@ -69,12 +69,10 @@ describe('ConfigService', () => {
         });
 
-        it('ensures the config file', () => {
+        it('does not create or modify the config file', () => {
           fixture.get('some-path');
-          expect(fs.ensureFileSync).toHaveBeenNthCalledWith(
</file context>

[c19yamamoto]

Fixed in d7f0e8f. The tests now cover an absent configuration (readJSONSync returns undefined) and verify that no file creation or write occurs.

[cubic-dev-ai]

1 issue found across 6 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/generator-cli/src/app/controllers/version-manager.controller.ts">

<violation number="1" location="apps/generator-cli/src/app/controllers/version-manager.controller.ts:111">
P2: This edit lands in `set`, not `resolve`. `set`'s no-match message now goes to stderr, a behavior change nobody asked for, and the `set` spec still expects `log`, so it will fail. Revert this line to `this.logger.log(`; `resolve` already uses `logger.error`.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: This edit lands in set, not resolve. set's no-match message now goes to stderr, a behavior change nobody asked for, and the set spec still expects log, so it will fail. Revert this line to this.logger.log(; resolve already uses logger.error.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At apps/generator-cli/src/app/controllers/version-manager.controller.ts, line 111:

<comment>This edit lands in `set`, not `resolve`. `set`'s no-match message now goes to stderr, a behavior change nobody asked for, and the `set` spec still expects `log`, so it will fail. Revert this line to `this.logger.log(`; `resolve` already uses `logger.error`.</comment>

<file context>
@@ -108,7 +108,7 @@ export class VersionManagerController {
     }
 
-    this.logger.log(
+    this.logger.error(
       chalk.red(
         `Unable to find version matching criteria "${versionTags.join(' ')}"`,
</file context>

Suggested change

	this.logger.error(
	this.logger.log(

[c19yamamoto]

This appears to be stale or misattributed. In the current code, set still uses logger.log, while only resolve uses logger.error, so no further change is needed.

[wing328]

thanks for the PR

let's give it a try

[github-actions]

🎉 This PR is included in version 2.42.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀