instar 0.26.0 → 0.26.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/package.json +1 -1
- package/src/data/builtin-manifest.json +2 -2
- package/upgrades/0.26.1.md +22 -0
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "./builtin-manifest.schema.json",
|
|
3
3
|
"schemaVersion": 1,
|
|
4
|
-
"generatedAt": "2026-04-
|
|
5
|
-
"instarVersion": "0.26.
|
|
4
|
+
"generatedAt": "2026-04-01T18:33:40.868Z",
|
|
5
|
+
"instarVersion": "0.26.1",
|
|
6
6
|
"entryCount": 180,
|
|
7
7
|
"entries": {
|
|
8
8
|
"hook:session-start": {
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
# Upgrade Guide — v0.26.1
|
|
2
|
+
|
|
3
|
+
<!-- bump: patch -->
|
|
4
|
+
|
|
5
|
+
## What Changed
|
|
6
|
+
|
|
7
|
+
**Slack standalone file support** — Previously, files drag-and-dropped into Slack without accompanying text were silently ignored. These arrive as `file_shared` events containing only a `file_id` (no download URL), so the handler logged them but never processed them. Now `_handleFileShared()` calls the Slack `files.info` API to fetch the full file metadata (`url_private`, mimetype, name), downloads with authenticated `FileHandler`, and routes through the standard message pipeline.
|
|
8
|
+
|
|
9
|
+
**Scope dependency**: This feature uses `files.info` which requires the `files:read` bot scope. This scope was always listed as required but was never exercised at runtime until now. Slack apps created using the instar setup flow should already have it. If the scope is missing, the handler logs an actionable error message ("add files:read in your Slack app's OAuth settings") and fails gracefully — existing functionality is not affected.
|
|
10
|
+
|
|
11
|
+
**Graceful degradation**: If `files.info` fails for any reason (missing scope, rate limit, network error), the file is simply not processed. No crash, no broken messages. Message-embedded files (sent with text) continue to work exactly as before via the existing inline handler.
|
|
12
|
+
|
|
13
|
+
## What to Tell Your User
|
|
14
|
+
|
|
15
|
+
- **Slack file support**: "Files shared in Slack without a message — like drag-and-dropping a PDF or image — are now picked up and processed automatically. Previously these were silently ignored. If your Slack app was set up with the standard permissions, this just works. If not, I can help you add the required permission."
|
|
16
|
+
|
|
17
|
+
## Summary of New Capabilities
|
|
18
|
+
|
|
19
|
+
| Capability | How to Use |
|
|
20
|
+
|-----------|-----------|
|
|
21
|
+
| Standalone Slack file processing | Automatic — drag-and-drop files into Slack channels |
|
|
22
|
+
| Missing scope detection | Automatic — actionable error logged if `files:read` scope is missing |
|