Update ocmcli to v0.7.0

[hilmarf]

bump versions:

• ocm v0.7.0
• cobra v1.8.0
• exp v0.0.0-20231006

Description

fixes: #183

Once it's merged the github action `` should work again and when triggered, creates a new PR to update the OCM-commandline-interface docs.

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

• Fixes Action for generation of linked docs from OCM CLI fails #183

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help
• Separate ticket for tests # (issue/pr)

Added to documentation?

• 📜 README.md
• 🙅 no documentation needed

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[morri-son]

lgtm

[morri-son]

Hi @hilmarf, I'm not able to run the webpage locally anymore. This should work using

npm run start

Trying this now I get

❯ npm run start

> [email protected] prestart
> npm run clean


> [email protected] clean
> shx rm -rf public resources


> [email protected] start
> exec-bin node_modules/.bin/hugo/hugo server --bind=0.0.0.0 --disableFastRender

node:events:497
      throw er; // Unhandled 'error' event
      ^

Error: spawn node_modules/.bin/hugo/hugo ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn node_modules/.bin/hugo/hugo',
  path: 'node_modules/.bin/hugo/hugo',
  spawnargs: [ 'server', '--bind=0.0.0.0', '--disableFastRender' ]
}

Node.js v21.7.0

Can you please try this out on your laptop? I just installed a new node.js version and also she, so the issue may be related to this, too.

[hilmarf]

Hi @hilmarf, I'm not able to run the webpage locally anymore. This should work using

npm run start

Trying this now I get

❯ npm run start

> [email protected] prestart
> npm run clean


> [email protected] clean
> shx rm -rf public resources


> [email protected] start
> exec-bin node_modules/.bin/hugo/hugo server --bind=0.0.0.0 --disableFastRender

node:events:497
      throw er; // Unhandled 'error' event
      ^

Error: spawn node_modules/.bin/hugo/hugo ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn node_modules/.bin/hugo/hugo',
  path: 'node_modules/.bin/hugo/hugo',
  spawnargs: [ 'server', '--bind=0.0.0.0', '--disableFastRender' ]
}

Node.js v21.7.0

Can you please try this out on your laptop? I just installed a new node.js version and also she, so the issue may be related to this, too.

@morri-son
Please give it a try with the latest LTS version of node v20.11.1

I believe I was running the site yesterday successfully with that version

[morri-son]

yup, that was the issue! Thanks, works now!