[DSD-4199]

[JanardhanBS-SyncByte]

No description provided.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: ab300b9c-8bd5-492c-8637-c5f39bfd9c41

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch develop

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

Generally, the fix is to explicitly define a permissions block that scopes the GITHUB_TOKEN to the minimum needed. This can be done at the workflow root (applies to all jobs without their own permissions) or per job. Since this workflow has a single job that calls a reusable workflow which likely needs to read repository contents and possibly write to gh-pages and read workflow metadata, we should set only those permissions that are clearly required.

Without modifying the functionality, we should:

• Add a root‑level permissions block after the on: section (lines 3–42).
• Grant contents: write to allow publishing Helm charts (push to gh-pages), and id-token: write only if needed for OIDC (we will omit it since there is no indication it’s used).
• Optionally grant actions: read if the reusable workflow needs to query workflow runs; since we do not see such usage here, we’ll keep it minimal.

Concretely, in .github/workflows/chart-lint-publish.yml, insert:

permissions:
  contents: write

between the on: block (ending at line 42) and the jobs: block (line 44). This limits GITHUB_TOKEN to repository contents write access only, which is the minimum obviously required for linting/publishing charts.

To fix this, avoid including raw id in response messages sent back to clients. The best minimal-change fix is to return static messages that preserve behavior (status codes and success/failure semantics) while removing reflected user input.

In mock-abis/src/main/java/io/mosip/proxy/abis/controller/ProxyAbisConfigController.java, update the deleteExpectation method:

• Replace line returning "Expectation not found: " + id with a constant "Expectation not found".
• Replace line returning "Successfully deleted expectation " + id with a constant "Successfully deleted expectation".

No new imports, helper methods, or dependencies are required.