revel-backend

v1.62.0 Feature

This release adds 1 notable feature for engineering teams evaluating rollout.

Published 1mo Productivity & Wikis

✓ No known CVEs patched

✓ No known CVEs patched in this version

Summary

AI summary

Fixes the event‑cancelled notification and adds persistence of an optional cancellation reason.

Type	Severity	Summary	CVE
Feature	Medium	Adds optional cancellation reason persistence for events. Adds optional cancellation reason persistence for events. Source: llm_adapter@2026-06-02 Confidence: high	—
Bugfix	Medium	Repairs event-cancelled notification and gates cancellation reason to attendees. Repairs event-cancelled notification and gates cancellation reason to attendees. Source: llm_adapter@2026-06-02 Confidence: high	—

Full changelog

chore(locale): update German translations, standardize colon gendering, and harmonize terminology in django.po by @florimond-collette in https://github.com/letsrevel/revel-backend/pull/469
feat(events): persist optional cancellation reason on event (closes #470) by @biagiodistefano in https://github.com/letsrevel/revel-backend/pull/471
fix(events): repair event-cancelled notification + gate cancellation reason to attendees by @biagiodistefano in https://github.com/letsrevel/revel-backend/pull/472

@florimond-collette made their first contribution in https://github.com/letsrevel/revel-backend/pull/469

Full Changelog: https://github.com/letsrevel/revel-backend/compare/v1.61.0...v1.62.0

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track revel-backend

Get notified when new releases ship.

About revel-backend

The Django backend of the Revel event platform project

v1.72.1 Makes payment base fields (`amount`, `currency`, `platform_fee`) read-only
v1.72.1 Restricts organization ownership transfer to superusers only
v1.71.0 Checkout flow now uses a two-step reserve then session creation process.
v1.68.0 check-in endpoint path renamed to use ticket code (UUID or series:<uuid>) instead of ticket ID.