From 37462903a6460fc33cf881c23e44b954dd2b40a3 Mon Sep 17 00:00:00 2001
From: Jason Garber <jason@sixtwothree.org>
Date: Sun, 11 Feb 2024 23:20:25 -0500
Subject: [PATCH] Manually update versions in lockfile to `1.19.0` (#99)

I ran `npm install` locally and noticed changes to `package-lock.json`. Turns out it was for these two lines that identify the package's current version.

(Note that there's no negative effective on any version of the package on npm since the lockfile doesn't get published.)
---
 package-lock.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package-lock.json b/package-lock.json
index c30e135..c668cfe 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "eslint-plugin-sort-class-members",
-  "version": "1.18.0",
+  "version": "1.19.0",
   "lockfileVersion": 2,
   "requires": true,
   "packages": {
     "": {
       "name": "eslint-plugin-sort-class-members",
-      "version": "1.18.0",
+      "version": "1.19.0",
       "license": "MIT",
       "devDependencies": {
         "@babel/cli": "^7.8.4",