|
2 | 2 |
|
3 | 3 | <!-- Format based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) --> |
4 | 4 |
|
| 5 | +## [3.3.2] |
| 6 | + |
| 7 | +Lockstep patch release of `pryv@3.3.2` + `@pryv/monitor@3.3.2` + |
| 8 | +`@pryv/socket.io@3.3.2` + `@pryv/cmc@1.0.2`. |
| 9 | + |
| 10 | +### `@pryv/cmc@1.0.2` |
| 11 | + |
| 12 | +#### Fixed |
| 13 | +- `readOffer(capabilityUrl)` no longer passes a `streams` filter to |
| 14 | + `events.get`. Follow-up to 1.0.1: the previous fix changed |
| 15 | + `streamIds` to `streams` (correct field name) but the value |
| 16 | + `[':_cmc:_internal:offer']` referenced a stream that doesn't |
| 17 | + exist on the user's account. Only the per-capability children |
| 18 | + `:_cmc:_internal:offer:<capId>` are auto-provisioned, and the |
| 19 | + accepter doesn't know `<capId>` from the `capabilityUrl` alone. The |
| 20 | + api-server rejected the call with `unknown-referenced-resource`. |
| 21 | + The fix mirrors the plugin's own `readOfferViaCapability` |
| 22 | + (`open-pryv.io/components/cmc/src/acceptOrchestration.ts`): |
| 23 | + omit the `streams` filter entirely and rely on the capability |
| 24 | + access's permissions to narrow the response to the single offer |
| 25 | + event the token can read. The `types: ['consent/request-cmc']` |
| 26 | + filter is kept as defense in case the offer stream ever holds more |
| 27 | + than one event in future revisions. |
| 28 | + |
| 29 | +#### Test |
| 30 | +- `[CMCL1OA]` updated to assert `events.get` is called WITHOUT a |
| 31 | + `streams` field AND with a `types: ['consent/request-cmc']` filter. |
| 32 | + |
| 33 | +### `pryv@3.3.2`, `@pryv/monitor@3.3.2`, `@pryv/socket.io@3.3.2` |
| 34 | + |
| 35 | +- No code changes. Versions bumped in lockstep with `@pryv/cmc@1.0.2`. |
| 36 | + |
5 | 37 | ## [3.3.1] |
6 | 38 |
|
7 | 39 | Lockstep patch release of `pryv@3.3.1` + `@pryv/monitor@3.3.1` + |
|
0 commit comments