capibara 1.3.71 → 1.3.73
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/.claude/skills/capibara-publish/SKILL.md +38 -0
- package/dist/index.js +291 -279
- package/package.json +1 -1
- package/src/lib/capibara.js +14 -1
- package/src/scss/components/_input_nav.scss +99 -0
- package/src/scss/layout/_nav.scss +30 -0
- package/src/scss/layout/_plotContainer.scss +4 -0
- package/src/util/tableElements.js +122 -11
- package/src/version.js +5 -0
- package/vite.config.js +4 -0
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: capibara-publish
|
|
3
|
+
description: Prepare, merge, and publish a new Capibara npm release when the user explicitly requests a version release or publication. Use only for the capibara package, not ordinary builds or unrelated npm packages.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Capibara Publish
|
|
7
|
+
|
|
8
|
+
Publish Capibara safely from `/home/projas/dev/irricrops/capibara`. The repository's primary branch is `master`; do not assume a branch named `main` exists.
|
|
9
|
+
|
|
10
|
+
## Scope and authorization
|
|
11
|
+
|
|
12
|
+
- Preparing a version is local work. Pushing a branch, creating a remote tag, and `npm publish` change external state. Require the user's explicit request to do those actions in the current task.
|
|
13
|
+
- Preserve unrelated work in the repository. Before committing or staging, inspect `git status --short` and limit the release commit to Capibara's relevant source, tests, docs, and version files.
|
|
14
|
+
- Do not publish a version that is already registered. Never retry `npm publish` merely because the npm website has not refreshed yet.
|
|
15
|
+
|
|
16
|
+
## Release procedure
|
|
17
|
+
|
|
18
|
+
1. Inspect the active branch, `master`, remotes, staged changes, current `package.json` version, and npm identity with `npm whoami`.
|
|
19
|
+
2. Fetch `origin`. If the release is on a feature branch, confirm whether it can fast-forward onto `master`. Do not merge a divergent history without asking the user.
|
|
20
|
+
3. Validate before changing release state:
|
|
21
|
+
- run `npm test` when the repository provides it;
|
|
22
|
+
- run `npm run build`;
|
|
23
|
+
- run `npm publish --dry-run` and verify the tarball includes `dist/index.js` and has the intended version.
|
|
24
|
+
4. Create the requested semantic version with `npm version <patch|minor|major> --no-git-tag-version`, unless the user explicitly supplied an exact version. Check `npm view capibara@<version> version`; an existing result is a stop condition.
|
|
25
|
+
5. Commit only the release files, normally `package.json` and `package-lock.json`, with a clear release message. Include implementation files only if they have not already been committed as part of the requested release.
|
|
26
|
+
6. Merge the release branch into `master` using `git merge --ff-only`, then push `master` to `origin`.
|
|
27
|
+
7. Run `npm publish`. After a successful command, create and push the annotated tag `v<version>`.
|
|
28
|
+
8. Verify publication from the registry, not only from the command output:
|
|
29
|
+
- query `npm view capibara@<version> version`;
|
|
30
|
+
- query `npm dist-tag ls capibara` and confirm `latest` when that tag was intended.
|
|
31
|
+
|
|
32
|
+
## Delayed registry visibility
|
|
33
|
+
|
|
34
|
+
The npm registry can report that a package is being processed before `npm view` or npmjs.com displays the new version. Poll the registry for a short, bounded period before reporting success. If it remains unavailable, report the pending state and do not republish the same version: npm publication is immutable and a duplicate retry can fail or create confusion.
|
|
35
|
+
|
|
36
|
+
## Completion report
|
|
37
|
+
|
|
38
|
+
State the exact version, target branch, commit, tag, and whether npm registry verification succeeded. Distinguish a completed publication from a successful upload still awaiting registry visibility.
|