Skip to content

Bump eslint-plugin-local-rules from 2.0.1 to 3.0.2#1959

Merged
rugpanov merged 1 commit into
mainfrom
deps/eslint-plugin-local-rules-v3
Jul 3, 2026
Merged

Bump eslint-plugin-local-rules from 2.0.1 to 3.0.2#1959
rugpanov merged 1 commit into
mainfrom
deps/eslint-plugin-local-rules-v3

Conversation

@rugpanov

@rugpanov rugpanov commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Why

Replaces Dependabot's #1938, which bumped package.json without regenerating the lockfile (the usual Yarn Berry YN0028 failure). eslint-plugin-local-rules just wires the repo's custom local-rules/* rules into ESLint; v3 has no engine/peer constraints affecting us.

What

  • Bump eslint-plugin-local-rules^3.0.2 via yarn up; regenerated yarn.lock (resolves 3.0.2).

Verification

  • yarn install --immutable passes.
  • eslint src --ext ts passes (0 errors).
  • Confirmed the custom rule is still active under v3 — eslint --print-config reports local-rules/mutex-synchronised-decorator: ['error'] (not silently dropped).

Backward compatibility: dev/lint tooling only; no runtime, API, persisted-state, or config-format change.

Closes #1938.

This pull request and its description were written by Isaac.

*Why*
Dependabot's #1938 bumped only package.json without regenerating the lockfile
(the usual Yarn Berry YN0028 failure). This recreates the bump with a consistent
lockfile. eslint-plugin-local-rules just wires the repo's custom
`local-rules/*` rules into ESLint; v3 has no engine/peer constraints affecting us.

*What*
- Bump `eslint-plugin-local-rules` to `^3.0.2` (databricks-vscode package) via
  `yarn up`, regenerating yarn.lock (resolves 3.0.2).

*Verification*
- `yarn install --immutable` passes.
- `eslint src --ext ts` passes (0 errors).
- Confirmed the custom rule is still active under v3: `eslint --print-config`
  reports `local-rules/mutex-synchronised-decorator: ['error']` (not silently
  dropped) — so the plugin upgrade preserves rule enforcement.

Backward compatibility: dev/lint tooling only; no runtime, API, persisted state,
or config-format change.

Closes #1938.

Co-authored-by: Isaac
@rugpanov rugpanov temporarily deployed to test-trigger-is July 3, 2026 12:31 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/vscode

Inputs:

  • PR number: 1959
  • Commit SHA: 7c24e9bb60af861dea0496d0a34b2dc2b4a6bfdf

Checks will be approved automatically on success.

@rugpanov

rugpanov commented Jul 3, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Integration tests ❌ 8 of 35 test jobs failed for 7c24e9bb (27 passed).
View run

@rugpanov

rugpanov commented Jul 3, 2026

Copy link
Copy Markdown
Contributor Author

Integration tests: https://github.com/databricks-eng/eng-dev-ecosystem/actions/runs/28660941986

TLDR: no regressions — 24 passing / 8 failing, within the current e2e baseline. Zero Can't find view control "CONFIGURATION" (activation) failures. This is a lockfile-only devDependency bump (lint plugin), so it can't affect extension runtime; all 8 reds are the known pre-existing environmental flakes (terraform-registry network, UC Item "access" not found, Login didn't finish, element click intercepted, ENOENT) that fail identically on main.

@rugpanov rugpanov enabled auto-merge (squash) July 3, 2026 13:03
@rugpanov rugpanov merged commit bab1c41 into main Jul 3, 2026
6 of 8 checks passed
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