@camphoric/camphoric-event-lark 1.0.0 → 1.0.1

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/CHANGELOG.md CHANGED
@@ -1,5 +1,12 @@
1
1
  # Changelog
2
2
 
3
+ ## [1.0.1](https://github.com/camphoric/camphoric-event-lark/compare/v1.0.0...v1.0.1) (2026-10-20)
4
+
5
+
6
+ ### Bug Fixes
7
+
8
+ * **build:** publish to and install from npm ([125149a](https://github.com/camphoric/camphoric-event-lark/commit/125149a798c48e225129da636133673c776e0ce5))
9
+
3
10
  ## 1.0.0 (2026-10-17)
4
11
 
5
12
 
package/README.md CHANGED
@@ -7,29 +7,13 @@ imported event.
7
7
 
8
8
  It satisfies the contract in
9
9
  [`@camphoric/camphoric-event-import-spec`](https://github.com/camphoric/camphoric/tree/main/data/packages/event-import-spec),
10
- and Camphoric's importer (`data/` in the Camphoric repository) installs it from GitHub Packages
11
- and imports it.
12
-
13
- ## Installing from GitHub Packages
14
-
15
- The `@camphoric` packages are on GitHub Packages, which needs a token to install **even public
16
- packages**. This repository's `.npmrc` points the `@camphoric` scope there; give npm a token with
17
- the `read:packages` scope, never in a committed file:
18
-
19
- ```bash
20
- gh auth refresh -s read:packages
21
- ```
22
-
23
- ```bash
24
- npm config set //npm.pkg.github.com/:_authToken "$(gh auth token)"
25
- ```
26
-
27
- In GitHub Actions, the workflows use the job's own `GITHUB_TOKEN` (with `packages: read`).
10
+ and Camphoric's importer (`data/` in the Camphoric repository) installs it from npm and
11
+ imports it.
28
12
 
29
13
  ## Developing
30
14
 
31
15
  ```bash
32
- npm ci # install (needs the token above)
16
+ npm ci # install
33
17
  npm test # unit tests, including the spec's conformance checks
34
18
  npm run typecheck
35
19
  npm run lint # type-check, then ESLint
@@ -86,14 +70,16 @@ Commits follow [Conventional Commits](https://www.conventionalcommits.org/) (`fe
86
70
  release; `feat!:` is a major). On each push to `main`,
87
71
  [release-please](https://github.com/googleapis/release-please) keeps a release PR up to date
88
72
  with the version bump and `CHANGELOG.md`. Merging it tags `vX.Y.Z`, creates the GitHub Release,
89
- and publishes the package to GitHub Packages. To publish a released tag again, if that failed:
73
+ and publishes the package to npm. To publish a released tag again, if that failed:
90
74
 
91
75
  ```bash
92
76
  gh workflow run release-please.yml -f tag=v1.0.0
93
77
  ```
94
78
 
95
- The repository publishes the package, so in the package's settings, under "Manage Actions
96
- access", this repository must keep the **Write** (or Admin) role.
79
+ The package's settings on npmjs.com list this repository and `release-please.yml` as its GitHub
80
+ Actions trusted publisher, allowed to `npm publish`. npm drops a trusted publisher that hasn't
81
+ published within 2 days of being added; without a matching one, the publish fails with npm's 404
82
+ or `ENEEDAUTH`.
97
83
 
98
84
  ## History
99
85
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camphoric/camphoric-event-lark",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "description": "Lark Traditional Arts' Lark Camp Camphoric event: its import object, organization, reports and bulk registrations.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -21,8 +21,8 @@
21
21
  "./package.json": "./package.json"
22
22
  },
23
23
  "publishConfig": {
24
- "registry": "https://registry.npmjs.org/",
25
- "access": "public"
24
+ "access": "public",
25
+ "registry": "https://registry.npmjs.org/"
26
26
  },
27
27
  "scripts": {
28
28
  "test": "NODE_OPTIONS=--experimental-vm-modules jest",