Skip to content

CCM-16068 - Added support for setting up pnpm tooling#102

Open
rhyscoxnhs wants to merge 4 commits intomainfrom
feature/CCM-16068
Open

CCM-16068 - Added support for setting up pnpm tooling#102
rhyscoxnhs wants to merge 4 commits intomainfrom
feature/CCM-16068

Conversation

@rhyscoxnhs
Copy link
Copy Markdown
Contributor

Description

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@rhyscoxnhs rhyscoxnhs marked this pull request as ready for review April 2, 2026 11:27
@rhyscoxnhs rhyscoxnhs requested review from a team as code owners April 2, 2026 11:27
- name: pnpm install
working-directory: ./docs
run: npm ci --min-release-age 3
run: pnpm install --frozen-lockfile
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should default to true in CI environments. I can't see GitHub mentioned but probably falls under env.CI with GitLab:
https://pnpm.io/cli/install#--frozen-lockfile

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually the bash scripts do want it explicitly set as we might run it locally. So we could just stick with it being explicitly set everywhere.

return sub;
}),
subscriptions: config.subscriptions.map(
// eslint-disable-next-line sonarjs/function-return-type -- false positive: complex conditional spread returns are all SubscriptionConfiguration subtypes
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we have a load of lint fixes on this branch? Was the linter not picking these up?

- "tools/*"

engineStrict: true
minimumReleaseAge: 720
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is 12 hours enough? Gone from 0 -> 3 days -> 12 hours.
I think 1 day at least would give us enough time to be alerted to a supply chain attack but 2 would be safer.

ts-node: "^10.9.2"
tsx: "^4.21.0"
typescript: "^5.9.3"
zod: "^4.3.6"
Copy link
Copy Markdown
Contributor

@mjewildnhs mjewildnhs Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is zod not app rather than tools?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants