Skip to content

Release/1.1.0#21

Draft
gkostkowski wants to merge 535 commits into
mainfrom
release/1.1.0
Draft

Release/1.1.0#21
gkostkowski wants to merge 535 commits into
mainfrom
release/1.1.0

Conversation

@gkostkowski

Copy link
Copy Markdown
Contributor

This PR introduces the stable 1.1.0 release. A comprehensive description of the changes is available in the CHANGELOG.

twicechild and others added 30 commits April 15, 2026 02:45
fix: close whitespace-only gap in GET /lookup, remove duplicate constant
…n seed script

1. factories.py: add `_organisation_payload()` and `_procedure_payload()` with
   faker-synthesised fields matching the RDF mapping config field names, plus
   `_payload_for(entity_type)` dispatcher and `build_for_entity_type()` on
   `ResolutionRequestRecordFactory` so callers can generate type-correct content
   and parsed_representation in one call.

2. seed_db.py: use `build_for_entity_type()` when seeding mentions so each
   record carries content matching its entity type; partition cluster references
   by entity type so ORGANISATION and PROCEDURE mentions are never mixed in
   the same cluster, and thread type-scoped cluster IDs through to candidate
   selection.
- factories.py: content() now delegates to _payload() instead of
  hardcoding _organisation_payload(), keeping content consistent
  with parsed_representation for subclasses
- factories.py: build_for_entity_type() derives content_hash as the
  SHA-256 of the generated payload, matching the ResolutionRequestRecord
  contract
- seed_db.py: _build_cluster_references() returns empty maps early when
  called with an empty mentions list, avoiding ZeroDivisionError
Moves the RDF mention mapping config from er-ops into config/ at the
repo root. Updates the default config path, mounts the file in the dev
compose setup, and documents the env var in .env.example.
chore: add rdf_mention_config.yaml to repo and wire it up
Co-authored-by: Meaningfy <hi@meaningfy.ws>
…d-data-gen

feat: generate distinct entities for procedure type, fix cluster membership issue
…-fixes

fix(scripts): operational script tests, docs, stale-entry repair, batch-size clarification
TEDSWS-524-1: reject exclusions (TEDSWS-530), cluster-size delete-on-zero, review-state read-port
…nt and cluster_sizes

Add BDD feature and step definitions covering the full reviewed_since_placement
lifecycle (fresh placement, curator action, ERE re-placement). Fix scenario isolation
by including cluster_sizes in the MongoDB cleanup list. Align injected decision
documents with the two new materialised fields. Correct the bulk-reevaluation
decision fixture to exclude current_placement from candidates per domain invariant.
…ince-placement

fix(scripts): backfill also sets reviewed_since_placement
Aligns reject_decision with the intended invariant: when a curator
rejects a decision, ERE should re-evaluate excluding both the current
placement and all candidate clusters. Updates the unit and e2e test
assertions accordingly.

Resolves merge conflict in test_user_reevaluation.py (all_refs fixture
variable name), restoring the corrected _make_decision helper.
test(e2e): extend e2e contract tests for curation PRs 120/121/122
… scenarios

Extends resolution_and_curation.http with two new full-cycle scenarios:
S6 covers the accept curation action with confirming ERE re-placement; S7
covers the reviewed_since_placement filter lifecycle (set on action, reset
on re-placement). All new cases marked as passing in the testing report.

Also rewords the notification subscriber worker debug log to accurately
describe both the cross-instance case and unsolicited re-evaluation outcomes.
test(manual): add S6 accept and S7 reviewed_since_placement lifecycle scenarios
- Add --no-cache rebuild tips (make rebuild-clean / make infra-rebuild-clean)
  in the ERS Getting Started section and INSTALL.md steps for ERS and ERE
- Document that entity schema changes require clearing the database volume
  (make down-volumes) to avoid schema mismatch errors on restart
- Fix API_BACKEND_URL default: curation-api:8000 (no http:// prefix);
  Nginx prepends the protocol internally — the http:// prefix caused API errors
- Add host-machine override note for REDIS_HOST in src/infra/.env.example:
  export REDIS_HOST=localhost before running black-box test targets
- Update CHANGELOG.md version tag to 1.1.0-rc.2
docs: practical notes on setup and configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants