Update NPM token action and yarn install options

[Dargon789]

Updated NPM token action version and modified yarn install command.

Summary by Sourcery

Update the build workflow to use the latest NPM token action and adjust dependency installation flags.

Build:

• Bump the use-npm-token GitHub Action from v1 to v3 in the build workflow.
• Change the yarn install step in the build workflow to use --no-frozen-lockfile instead of --frozen-lockfile when cache is missed.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the CI build workflow to use a newer version of the NPM token GitHub Action and relaxes yarn install behavior by disabling the frozen lockfile constraint when cache is missed.

Flow diagram for updated dependency installation logic in CI workflow

flowchart TD
  A[Start CI job] --> B[Run yarn --prefer-offline]
  B --> C[Check yarn cache result]
  C -->|cache-hit == true| D[Skip yarn install]
  C -->|cache-hit != true| E[Run yarn install --no-frozen-lockfile]
  D --> F[Continue build steps]
  E --> F[Continue build steps]

Loading

File-Level Changes

Change	Details	Files
Upgrade the NPM token GitHub Action used in the build workflow.	Bump use-npm-token-action from version v1 to v3 for the step that configures the NPM token with organization read access	.github/workflows/build.yml
Adjust yarn install options when dependency cache is cold.	Change the dependency installation command from yarn install --frozen-lockfile to yarn install --no-frozen-lockfile for non-cached installs in the build workflow	.github/workflows/build.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Hey - I've left some high level feedback:

• Switching from --frozen-lockfile to --no-frozen-lockfile can allow the lockfile to drift from what’s committed; if this is intentional, consider adding a brief comment in the workflow explaining why this behavior is desired to avoid future confusion.
• After bumping heisenberg-2077/use-npm-token-action to v3, double-check the action’s changelog for any new required inputs or behavioral changes and reflect those in the workflow if needed, rather than assuming v1-compatible defaults.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Switching from `--frozen-lockfile` to `--no-frozen-lockfile` can allow the lockfile to drift from what’s committed; if this is intentional, consider adding a brief comment in the workflow explaining why this behavior is desired to avoid future confusion.
- After bumping `heisenberg-2077/use-npm-token-action` to v3, double-check the action’s changelog for any new required inputs or behavioral changes and reflect those in the workflow if needed, rather than assuming v1-compatible defaults.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}