chore: update knope

[pcfreak30]

Add Knope configuration for the @lumeweb/portal-plugin-onboarding package

This PR registers the @lumeweb/portal-plugin-onboarding package in knope.toml, enabling automated versioning and changelog generation for it. The configuration follows the same pattern as existing portal plugin packages, pointing to the package's package.json for version tracking and its CHANGELOG.md for changelog output.

[kody-ai]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​

[kody-ai]

Non-existent changelog path libs/portal-plugin-onboarding/CHANGELOG.md in knope.toml causes release failures when Knope attempts to update package metadata. Create this file to match repository conventions and ensure successful execution.

[packages."@lumeweb/portal-plugin-onboarding"]
versioned_files = ["libs/portal-plugin-onboarding/package.json"]
changelog = "libs/portal-plugin-onboarding/CHANGELOG.md"

# Also create libs/portal-plugin-onboarding/CHANGELOG.md (empty or with initial header)

Prompt for LLM

File knope.toml:

Line 76 to 78:

WHAT: The changelog path `libs/portal-plugin-onboarding/CHANGELOG.md` is referenced in knope.toml but the file does not exist in the repository. WHY: Every other package in knope.toml has its corresponding CHANGELOG.md file present; Knope will likely fail when attempting to read or append to this non-existent file during a release. HOW: Create `libs/portal-plugin-onboarding/CHANGELOG.md` before merging (e.g., with an initial entry or as an empty file, matching the convention of other packages).

Suggested Code:

[packages."@lumeweb/portal-plugin-onboarding"]
versioned_files = ["libs/portal-plugin-onboarding/package.json"]
changelog = "libs/portal-plugin-onboarding/CHANGELOG.md"

# Also create libs/portal-plugin-onboarding/CHANGELOG.md (empty or with initial header)

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​