Skip to content

Commit

Permalink
Private Datasets: process acceptance testing feedback: Vol. 1 (#1054)
Browse files Browse the repository at this point in the history
* TransformInput: after validation, use alias only for error messages

* OsoDatasetAuthorizer: be prepared to work with duplicates

* Release (patch): 0.221.1
  • Loading branch information
s373r authored Jan 31, 2025
1 parent eb07ada commit e8880cf
Show file tree
Hide file tree
Showing 12 changed files with 241 additions and 238 deletions.
19 changes: 13 additions & 6 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,16 +11,23 @@ Recommendation: for ease of reading, use the following order:
- Fixed
-->

### [0.221.1] - 2025-01-31
### Fixed
- Private Datasets:
- Validation `SetTransform` event (input datasets): IDs are used for accessibility checks.
Aliases are used only to generate an error message.
- `OsoDatasetAuthorizer`: readiness to handle duplicates when filtering

## [0.221.0] - 2025-01-29
### Added
- GQL suport to query and update email on the currently logged account
- GQL support to query and update email on the currently logged account
- Account registration sends `AccountLifecycleEvent` to `Outbox`
### Changed
- Emails are mandatory for Kamu accounts now:
- predefined users need to specify an email in config
- predefined users are auto-synced at startup in case they existed before
- GitHub users are queried for primary verified email, even if it is not public
- migration code for the database existing users
- predefined users need to specify an email in config
- predefined users are auto-synced at startup in case they existed before
- GitHub users are queried for primary verified email, even if it is not public
- migration code for the database existing users

## [0.220.0] - 2025-01-27
### Changed
Expand Down Expand Up @@ -380,7 +387,7 @@ Introduced `DatasetRegistry` abstraction, encapsulating listing and resolution o
### Changed
- Outbox main loop was revised to minimize the number of transactions:
- split outbox into planner and consumption jobs components
- planner analyzes current state and loads bunch of unprocessed messages within a 1 transaction only
- planner analyzes current state and loads a bunch of unprocessed messages within a 1 transaction only
- consumption jobs invoke consumers and detect their failures
- Detecting concurrent modifications in flow and task event stores
- Improved and cleaned handling of flow abortions at different stages of processing
Expand Down
Loading

0 comments on commit e8880cf

Please sign in to comment.