2.5 KiB
2.5 KiB
Internal Extension Distribution
Fixed Extension ID
- Manifest key is fixed in the project.
- The unpacked extension ID is
pkjopdibdnomhogjheclhnknmejccffg. - Update Logto with:
https://pkjopdibdnomhogjheclhnknmejccffg.chromiumapp.org/callbackhttps://pkjopdibdnomhogjheclhnknmejccffg.chromiumapp.org/chrome-extension://pkjopdibdnomhogjheclhnknmejccffg
Internal Package
- Run
npm test. - Run
npm run package:internal. - Run
npm run write:latest. - Send
release/star-chart-search-enhancer-internal.zipto coworkers.
COS Update Manifest
The popup checks src/shared/update-config.ts for the update manifest URL.
Before publishing the COS-based update flow:
- Upload these files to COS:
star-chart-search-enhancer/latest.jsonstar-chart-search-enhancer/releases/<version>/star-chart-search-enhancer-internal.zipstar-chart-search-enhancer/releases/<version>/星图增强插件-超简单安装使用指南.pdf
- Make the COS path publicly readable.
- Replace the placeholder
UPDATE_MANIFEST_URLinsrc/shared/update-config.tsif your COS bucket changes. - Rebuild and package the extension.
The release manifest can be generated with a real public base URL:
UPDATE_PUBLIC_BASE_URL="https://wksgx-1343191620.cos.ap-nanjing.myqcloud.com/star-chart-search-enhancer/releases/<version>" npm run write:latest
Quick access check:
curl -I https://wksgx-1343191620.cos.ap-nanjing.myqcloud.com/star-chart-search-enhancer/latest.json
Drone Release Flow
Tag the repo to trigger the release pipeline:
git tag 0.0525.1
git push origin 0.0525.1
The Drone job will:
- Run
npm ci. - Run
npm test. - Run
npm run release:tag. - Build the release bundle.
- Write
release/latest.json. - Upload
latest.json, the ZIP, and the PDF to COS.
Drone secrets required:
cos_secret_idcos_secret_key
The pipeline uses the tag as the release version. Recommended format: 0.MMDD.N.
Coworker Install Steps
- Unzip
star-chart-search-enhancer-internal.zip. - Open
chrome://extensions. - Enable developer mode.
- Click
Load unpacked. - Select the unzipped
dist/folder. - Confirm the extension ID is
pkjopdibdnomhogjheclhnknmejccffg.
Notes
- Keep
.local/extension-key.pemprivate and backed up internally. - Do not commit or share the private key with people who only need to install the extension.
- If the batch submit backend changes away from
192.168.31.21:8083, updatescripts/manifest.mjsbefore packaging.