pi-deepseek-tariff 0.3.0 → 0.3.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.
Files changed (2) hide show
  1. package/README.md +12 -6
  2. package/package.json +3 -2
package/README.md CHANGED
@@ -3,6 +3,7 @@
3
3
  [![npm](https://img.shields.io/npm/v/pi-deepseek-tariff?color=blue)](https://www.npmjs.com/package/pi-deepseek-tariff)
4
4
  [![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)
5
5
  [![pi-package](https://img.shields.io/badge/pi-package-8a2be2)](https://pi.dev/packages)
6
+ [![changelog](https://img.shields.io/badge/changelog-Keep%20a%20Changelog-orange)](CHANGELOG.md)
6
7
 
7
8
  A [pi](https://pi.dev) extension that shows the current **DeepSeek API tariff window** — peak or off-peak — with a countdown, and a panel with live prices parsed from the official DeepSeek pricing page.
8
9
 
@@ -132,12 +133,12 @@ Git tags and npm versions are kept in lockstep: the tag `vX.Y.Z` always points a
132
133
  the commit whose `package.json` says `X.Y.Z`, and npm publishes that same version.
133
134
 
134
135
  ```bash
135
- # 1. bump package.json + README, commit
136
- npm version 0.3.1 --no-git-tag-version # or edit by hand
137
- git commit -am "chore: release 0.3.1"
136
+ # 1. bump package.json, add a CHANGELOG entry, commit
137
+ npm version 0.3.2 --no-git-tag-version # or edit by hand
138
+ git commit -am "chore: release 0.3.2"
138
139
 
139
140
  # 2. tag the release commit and push
140
- git tag -a v0.3.1 -m v0.3.1
141
+ git tag -a v0.3.2 -m v0.3.2
141
142
  git push origin main --tags
142
143
 
143
144
  # 3. publish the tag to npm (2FA prompt, or --otp=123456)
@@ -148,7 +149,7 @@ npm publish --access public
148
149
  Check the result:
149
150
 
150
151
  ```bash
151
- npm view pi-deepseek-tariff dist-tags # { latest: '0.3.1' }
152
+ npm view pi-deepseek-tariff dist-tags # { latest: '0.3.2' }
152
153
  npm view pi-deepseek-tariff versions
153
154
  ```
154
155
 
@@ -156,9 +157,14 @@ npm view pi-deepseek-tariff versions
156
157
  `NPM_TOKEN` secret is configured; with trusted publishing enabled on npmjs.com the
157
158
  token is not needed at all and the build is signed with provenance.
158
159
 
159
- Tags are pinnable with `pi install git:…@v0.3.1`. Published versions show up in the
160
+ Tags are pinnable with `pi install git:…@v0.3.2`. Published versions show up in the
160
161
  [pi package gallery](https://pi.dev/packages) through the `pi-package` keyword.
161
162
 
163
+ ## Changelog
164
+
165
+ See [CHANGELOG.md](CHANGELOG.md). Git tags and npm versions are kept in lockstep, so
166
+ `vX.Y.Z` always matches the published `X.Y.Z`.
167
+
162
168
  ## License
163
169
 
164
170
  MIT
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-deepseek-tariff",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "DeepSeek peak/off-peak tariff panel for pi: local clock, next window, live per-model prices and Search & Fetch rates",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -30,7 +30,8 @@
30
30
  "pi": {
31
31
  "extensions": [
32
32
  "./extensions/deepseek-peak.ts"
33
- ]
33
+ ],
34
+ "image": "https://raw.githubusercontent.com/valderan/pi-deepseek-tariff/main/assets/banner.png"
34
35
  },
35
36
  "peerDependencies": {
36
37
  "@earendil-works/pi-coding-agent": "*",