@eveshipfit/sde 14.3665151.0 → 14.3678022.0-singularity.92

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -29,7 +29,7 @@ go run ./cmd/sde-patched serve # edit the patches in a browser
29
29
  ```
30
30
 
31
31
  `build` downloads the SDE when there is none yet, and uses the one on disk otherwise.
32
- Use `--build <number>` to pin a version, and `--major <number>` to stamp the major version of the release into `sde.dat`.
32
+ Use `--build <number>` to pin a version, `--server singularity` to use the SDE of the test server, and `--major <number>` to stamp the major version of the release into `sde.dat`.
33
33
 
34
34
  ## Editing
35
35
 
@@ -79,6 +79,9 @@ Every day at 12:00 UTC, `main` is built against the latest SDE.
79
79
  When the result differs from the latest release, the SDE build number and release date aside, a new release is made and published on npm and PyPI.
80
80
  A change to the patches is released this way too.
81
81
 
82
+ To preview the SDE of Singularity, run the Release workflow by hand with `server` set to `singularity`.
83
+ It is published on npm only, under the `singularity` tag.
84
+
82
85
  ## Patches
83
86
 
84
87
  The SDE describes what the EVE client needs, not what a fitting tool needs.
package/dist/names.dat CHANGED
Binary file
package/dist/sde.dat CHANGED
Binary file
package/dist/texts.dat CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@eveshipfit/sde",
3
- "version": "14.3665151.0",
3
+ "version": "14.3678022.0-singularity.92",
4
4
  "description": "A patched EVE Online SDE, as flatbuffers, for EVEShipFit's dogma-engine",
5
5
  "repository": {
6
6
  "type": "git",