fortrip 0.2.0 → 0.2.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/README.md +19 -0
- package/package.json +5 -1
package/README.md
CHANGED
|
@@ -81,3 +81,22 @@ pnpm build # dist/cli.js
|
|
|
81
81
|
```
|
|
82
82
|
|
|
83
83
|
Point at a local Fortrip app with `FORTRIP_API_URL=http://localhost:3000`.
|
|
84
|
+
|
|
85
|
+
## Releasing
|
|
86
|
+
|
|
87
|
+
Pushing a `v*` tag publishes to npm through
|
|
88
|
+
[`.github/workflows/publish.yml`](.github/workflows/publish.yml), which signs
|
|
89
|
+
in with npm trusted publishing (no npm token in GitHub).
|
|
90
|
+
|
|
91
|
+
1. Bump the version in a PR and merge it into `main`:
|
|
92
|
+
`npm version minor --no-git-tag-version` (or `patch`).
|
|
93
|
+
2. Tag the merged commit on `main` and push the tag:
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
git checkout main && git pull
|
|
97
|
+
git tag v0.2.0 && git push origin v0.2.0
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
The workflow refuses a tag that doesn't match `package.json` or isn't on
|
|
101
|
+
`main`, then runs typecheck, tests and the build before publishing. Every
|
|
102
|
+
installed skill picks up the new guide on its next `npx fortrip@latest skill`.
|
package/package.json
CHANGED
|
@@ -1,8 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "fortrip",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.1",
|
|
4
4
|
"description": "Search, price and book Fortrip hotels from the terminal or an AI agent.",
|
|
5
5
|
"type": "module",
|
|
6
|
+
"repository": {
|
|
7
|
+
"type": "git",
|
|
8
|
+
"url": "git+https://github.com/FortripEngineering/fortrip-cli.git"
|
|
9
|
+
},
|
|
6
10
|
"bin": {
|
|
7
11
|
"fortrip": "dist/cli.js"
|
|
8
12
|
},
|