@massif/lancer-data 3.1.1 → 3.1.3

package/.github/workflows/deploy-npm.yml

@@ -0,0 +1,14 @@
+# This workflow will call org-level reusable workflows for deploying an NPM package to npmjs.com.
+
+name: Deploy NPM
+
+on:
+  workflow_dispatch:
+  release:
+    types: [created]
+
+jobs:
+  call-npm-publish:
+    uses: massif-press/.github/.github/workflows/npm-publish.yml@master
+    secrets:
+      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package/.github/workflows/lcp-version-bump.yml

@@ -0,0 +1,22 @@
+# This workflow calls an org-level reusable workflow for incrementing LCP and NPM package versions.
+
+name: LCP Version Bump
+
+on:
+  workflow_dispatch:
+    inputs:
+      version_level:
+        description: 'Version level to bump'
+        required: true
+        default: 'patch'
+        type: choice
+        options:
+          - patch
+          - minor
+          - major
+
+jobs:
+  call-bump-version-tag:
+    uses: massif-press/.github/.github/workflows/bump-version-tag.yml@master
+    with:
+      version_level: ${{ inputs.version_level }}

package/README.md

@@ -1,6 +1,6 @@
 # !! IMPORTANT !!
 
-The `lancer-data` package is no longer the current source of COMP/CON data, and is now available under `@Massif/lancer-data`. The `lancer-data` package will no longer be updated, and will be removed in the future. Please update your dependencies accordingly.
+The `lancer-data` npm package is now available under `@massif/lancer-data`. The `lancer-data` package will no longer be updated, and will be removed in the future. Please update your dependencies accordingly. It is published from this repo, so everything else will stay the same otherwise.
 
 # About
 
@@ -1223,6 +1223,8 @@ The optional type and size parameters will restrict any weapon-related bonus to
 | `drone_tech_attack`       | Add tech attack to all deployed Drones       | integer   |
 | `drone_save`              | Add save to all deployed Drones              | integer   |
 | `drone_speed`             | Add speed to all deployed Drones             | integer   |
+| `pilot_gear_slots`        | Increase Pilot Gear capacity                 | integer   |
+| `pilot_weapon_slots`      | Increase Pilot Weapon capacity               | integer   |
 
 The `overwrite` flag will _overwrite_ any integer value bonus with the highest bonus of the same type from any source that has an `overwrite` flag. Which is to say: all applicable bonuses of that bonus ID will be collected and everything will be discarded _except for_ the bonus of the highest value _that has an `overwrite` flag_.
 Eg: a mech with items that give +4, +2, +3 (overwrite) and +2 (overwrite) AI Cap will result in a +3 AI Cap bonus.