@jtl-software/eslint-plugin-posthog 0.1.0 → 0.1.1

package/.github/dependabot.yml

@@ -0,0 +1,19 @@
+version: 2
+updates:
+  # Enable version updates for npm dependencies
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    groups:
+      dependencies:
+        patterns:
+          - "*"
+
+  # Enable version updates for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5

package/README.md

@@ -115,20 +115,6 @@ To test the plugin in your project before publishing:
 
 3. Add the plugin to your ESLint config as shown above
 
-### CI/CD
-
-This project uses GitHub Actions for continuous integration and deployment:
-
-- **Tests** run automatically on every push and pull request
-- **Publishing to npm** happens automatically when pushing to the `main` branch
-
-To set up automatic publishing, add an `NPM_TOKEN` secret to your GitHub repository:
-
-1. Generate an npm access token at https://www.npmjs.com/settings/tokens
-2. Go to your repository settings on GitHub
-3. Navigate to Settings → Secrets and variables → Actions
-4. Add a new repository secret named `NPM_TOKEN` with your npm token
-
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jtl-software/eslint-plugin-posthog",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "ESLint rules for PostHog event tracking best practices",
   "main": "src/index.js",
   "type": "module",
@@ -13,6 +13,10 @@
   ],
   "author": "JTL Platform Team",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/jtl-software/eslint-plugin-posthog.git"
+  },
   "peerDependencies": {
     "eslint": "^9.0.0"
   },