chore: update standard dependency to version 17.1.2

[originalix]

Summary by CodeRabbit

• Chores
  • Pinned the development linting dependency to an exact version to improve tooling stability, reproducible installs, and CI consistency. This does not affect application behavior, performance, or the user interface. No functional changes, migrations, or configuration updates are required for end users. Developers may see more consistent linting results and fewer unexpected diffs across machines.

[coderabbitai]

Walkthrough

Pin devDependency "standard" in package.json to version 17.1.2, replacing the previous range ^14.3.4.

Changes

Cohort / File(s)	Summary
Dev tooling: dependency pin package.json	Update devDependency "standard" from ^14.3.4 to 17.1.2 and pin exact version (no caret).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "chore: update standard dependency to version 17.1.2" clearly and accurately summarizes the primary change—upgrading the devDependency "standard" to 17.1.2. It is concise, specific, and readable for teammates scanning the commit history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-tmp

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 90b6fdb and 9d43445.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

52-52: Major linter bump + pin: check CI Node and rule namespace changes

• package.json pins "standard": "17.1.2" — fine for reproducibility; consider "~17.1.2" for automatic patch updates.
• Repo scan found no deprecated eslint-disable patterns using "node/".
• No .github/workflows with setup-node/node-version detected; package.json has no "engines.node". Confirm where CI runs and ensure CI uses Node ≥12.22 (prefer Node 18+ LTS) so ESLint 8 passes.
• Recommend adding a CI matrix that runs "npm run standard" on Node 18 and 20.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[revan-zhang]

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

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	standard@​14.3.4 ⏵ 17.1.2	+1		+1	-1

View full report